Can Incogni be vibe coded?
Track manual data-removal requests and reminders without impersonating the user or bypassing identity checks
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Incogni, track manual data-removal requests and reminders without impersonating the user or bypassing identity checks. The hard boundary is broker network, legal authorization, repeated removals, support, and operational scale, plus security assurance, infrastructure, and trust.
Jump to the build brief ↓Legacy-calibrated assessment
Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Tracked separately from the pricing check
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Track manual data-removal requests and reminders locally with strong encryption, never impersonating the user or bypassing identity checks, and without claiming to replace an audited service.
- Prototype the workflow, but rely on audited libraries and established security tools.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- broker network, legal authorization, repeated removals, support, and operational scale
- independent security audits
- global relay infrastructure
- breach monitoring data
- Trust, audits, and counterparties matter more than feature parity.
- Compliance, licensing, and legal accountability are core features.
Build, switch, or keep paying
Narrower, with trade-offs
Track manual data-removal requests and reminders locally with strong encryption, never impersonating the user or bypassing identity checks, and without claiming to replace an audited service.
Use the build brief ↓3 checked options
- California DROP ↗California residents get one government request to 600-plus brokers; everyone else gets a geography lesson.
- Optery Free Basic ↗Finds the profiles and hands you the opt-out links; your unpaid labor is the business model.
- Permission Slip by DeleteMe ↗A phone app that sends individual privacy requests and tracks them; bulk broker removal is the paid part.
Recommended
People still pay for Incogni because security products are paid for because expert review, infrastructure, and accountability matter more than recreating screens. The recurring cost buys cryptography, secure updates, key recovery, threat intelligence, relay capacity, abuse response, audits, and incident handling, not just the visible interface.
Visit Incogni ↗Why people still pay
People still pay for Incogni because security products are paid for because expert review, infrastructure, and accountability matter more than recreating screens. The recurring cost buys cryptography, secure updates, key recovery, threat intelligence, relay capacity, abuse response, audits, and incident handling, not just the visible interface.
Trust, audits, and counterparties matter more than feature parity.
Compliance, licensing, and legal accountability are core features.
Reliability at the vendor's scale is an operations problem, not a prompt.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Incogni
Context
Incogni — Track manual data-removal requests and reminders without impersonating the user or bypassing identity checks. It currently costs $14.98/mo.
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Incogni, track manual data-removal requests and reminders without impersonating the user or bypassing identity checks. The hard boundary is broker network, legal authorization, repeated removals, support, and operational scale, plus security assurance, infrastructure, and trust.
This brief describes a focused, single-operator replacement for the part of Incogni that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Track manual data-removal requests and reminders locally with strong encryption, never impersonating the user or bypassing identity checks, and without claiming to replace an audited service.
Prototype the workflow, but rely on audited libraries and established security tools.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Desktop OS.
Secure backup location.
Modern cryptographic libraries.
Careful review before real-world use.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a closest honest personal substitute for Incogni in an empty repository.
Use Rust, Tauri 2, React, SQLite, Argon2id, and audited cryptographic libraries; do not offer alternative stacks.
The core loop is: track manual data-removal requests and reminders locally with strong encryption, never impersonating the user or bypassing identity checks, and without claiming to replace an audited service.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Write a plain-language threat model before implementing any sensitive feature.
Keep all vault data encrypted with a master key derived through Argon2id and a unique salt.
Use authenticated encryption from a maintained library and never invent cryptographic primitives.
Implement lock timeout, clipboard clearing, password generation, import, export, and encrypted backups.
Make recovery-key creation explicit and test restore from a fresh installation.
Display a persistent warning that the build has not received an independent security audit.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out a production VPN or anonymity network.
Deliberately leave out identity-protection monitoring and data-broker removal.
Deliberately leave out enterprise security guarantees, audits, and emergency support.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Broker network, legal authorization, repeated removals, support, and operational scale.
Independent security audits.
Global relay infrastructure.
Breach monitoring data.
Account recovery and support.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Risk
High consequence. Use this as a prototype or personal aid. Keep a qualified human and an established provider in the loop for consequential decisions.
Editorial confidence in this assessment: high. No reviewed project implementation is linked yet.
Existing alternatives
Before building, compare these checked options:
California DROP — California residents get one government request to 600-plus brokers; everyone else gets a geography lesson
Optery Free Basic — Finds the profiles and hands you the opt-out links; your unpaid labor is the business model
Permission Slip by DeleteMe — A phone app that sends individual privacy requests and tracks them; bulk broker removal is the paid part
Prior art
Working open-source software you can read, fork, or borrow from before starting:
Vaultwarden — Widely used Bitwarden-compatible self-hosted password server implementation
Generated by Can It Be Vibe Coded? · Full report: https://www.canitbevibecoded.com/incogni
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
Projects built from this idea
No reviewed implementation has been linked for Incogni yet. A submission is evidence for review, not automatic proof that the whole product was replaced.
Built a version of Incogni?Submit the project as evidence for this report.
Open-source prior art
Before you start
Can Incogni be vibe coded?
Not faithfully. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Incogni, track manual data-removal requests and reminders without impersonating the user or bypassing identity checks. The hard boundary is broker network, legal authorization, repeated removals, support, and operational scale, plus security assurance, infrastructure, and trust.
What can an AI coding agent reproduce from Incogni?
Track manual data-removal requests and reminders locally with strong encryption, never impersonating the user or bypassing identity checks, and without claiming to replace an audited service. Prototype the workflow, but rely on audited libraries and established security tools. A responsive interface with real empty, loading, success, and error states.
What will a DIY Incogni replacement still be missing?
broker network, legal authorization, repeated removals, support, and operational scale; independent security audits; global relay infrastructure; breach monitoring data; Trust, audits, and counterparties matter more than feature parity.; Compliance, licensing, and legal accountability are core features.
What do I still own after building a Incogni alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss.