Why revoq
Built for the question that comes later.
Most opt-out tooling is designed for the moment a consumer clicks submit. revoq is designed for the moment, months later, when someone asks what your company actually did about it.
Principles
Four commitments that shape every screen
- Evidence over assurances
- If revoq shows a status, there is a recorded event behind it. Nothing is inferred after the fact to make a report look tidy.
- Verification before recording
- A request is only recorded as verified after a one-time code sent to that number is confirmed. Unverified submissions are rejected, not stored as if they counted.
- Precise language
- Attempted, accepted under the configured rule, inconclusive, and failed are different states with different meanings, and revoq never collapses them into one word.
- Append-only history
- Revocation records and delivery attempts are not editable. Corrections are added as new entries so the original remains visible.
Comparisons, honestly framed
What revoq replaces, and what it does not
- Instead of a plain web form: the number is verified, the disclosure version is captured, and the request is delivered rather than emailed to someone.
- Instead of a shared inbox or spreadsheet: each request has a reference number, a timeline, and a delivery history that nobody assembles by hand.
- Alongside your suppression systems: revoq does not replace them. It feeds them and records what they replied.
- Not a substitute for legal judgment: revoq does not interpret regulations or certify compliance. It documents facts your advisors can rely on.
Current stage
An early platform, described accurately
revoq is in active development. The capabilities described across this site are the ones running today; planned work is labeled as planned everywhere it appears.
- No customer logos, quotes, or performance statistics appear on this site, because none have been approved for publication.
- No certifications or audit outcomes are claimed.
- Roadmap items are stated as roadmap, including native connectors and file-based exchange.