Account Deletion Policy
You can delete your VERA account yourself, at any time, without contacting support. The account ends the moment you confirm: your subscription is cancelled, you are signed out everywhere, your sign-in stops working, your email address is released, and anything scheduled to publish is cancelled. Your records are then held, unreachable, for 30 days so that a deletion made by mistake can be undone, and are permanently erased when that window closes. Read this page before you do it.
- Version
- 1.2
- Effective
- August 17, 2026
- Last updated
- August 17, 2026
- Revisions
- 3
On this page (8 sections)
1. How to delete your account
Open Settings, go to the Account tab, and use Delete account in the danger zone. You will be asked to type your account email address exactly to confirm; the server checks it again before proceeding.
When you confirm, VERA cancels any active Stripe subscription, ends the account, and signs you out. You do not need to cancel your subscription separately first.
If you deleted the account by mistake, email support@myvera.io from the address that owned it, within 30 days, and ask us to restore it. After 30 days the records are gone and nobody can bring them back, including us.
2. Before you delete
Export your data. Settings has a data export that produces a JSON file of your account, business profile, customer records, estimates, invoices, and content. Once the account is deleted we cannot produce it for you.
Save anything you need from outside the export, such as generated images you want to keep or documents you have not downloaded.
Disconnecting integrations is not required, since deletion removes the stored credentials, but revoking VERA's access from the provider's own settings page is good hygiene and is the only way to be certain on the provider's side.
3. The 30-day recovery window
Deletion happens in two steps, and we would rather describe both than let the first one imply the second has already happened.
The first step runs the instant you confirm, and it is not reversible by us: your Stripe subscription is cancelled, every session is signed out, any linked Google or magic-link sign-in is disconnected, posts and automations waiting to run are cancelled, your membership in anyone else's VERA business is closed, and your email address is released so you (or anyone) can open a new account with it straight away. From that moment you cannot sign in, and there is no version of your account still running.
The second step is the permanent erasure of the records themselves, and it runs 30 days later. During those 30 days the data is not in use, not visible to you, and not visible in the product to anyone. It is reachable only by VERA staff, for one purpose: restoring the account if you tell us the deletion was a mistake.
We hold it because accounts do get deleted by accident, and an erasure we cannot undo turns a misclick into the loss of a business's records. If you would rather not wait, ask us to erase it immediately and we will (see "Deletion requests we handle by hand").
Restoring brings the records back. It does not undo the first step: a cancelled subscription stays cancelled, cancelled posts stay cancelled, and a closed membership in someone else's business stays closed, because those belong to Stripe, to a real audience, and to another business owner. If somebody has claimed your released email address in the meantime, we cannot restore the account to it, and we will not take the address off their account.
4. What is deleted
Deletion removes your records from the live database rather than flagging them as hidden. It covers the tables that hold your business data, which is all of them except the small, named set in the next section. We describe it that way rather than claiming every row everywhere is destroyed, because that claim would not be true and a policy should not make a promise the software cannot keep.
Specifically it removes:
- Your account and identity. The user record, password hash, linked Google or magic-link identities, sessions, and any outstanding verification or password reset tokens for your email address.
- Business and brand. Business profile, brand kit, onboarding session and its messages, profile suggestions, and Industry Radar context.
- Customer and operational records. Leads, contacts, companies, deals, jobs, technicians, appointments and booking configuration, support tickets, chatbot configuration and captured chat leads, workflows and their runs, agent definitions, saved ideas, tasks, and automation rules.
- Documents. Estimates with their sections, line items, revisions and activity, estimate settings, catalog items, invoices, imported documents including the stored copy of the original file, and learned import mappings.
- Content and files. Content drafts and items, proposals, agent runs, before-and-after projects and their variations, and every uploaded or generated asset, including the image data itself.
- Connected platform data. Integration connections and their encrypted credentials, sync logs, email provider connections, and every record synced from a platform: orders, customers, products, ad campaigns, email campaigns, social posts, calendar events, and daily metrics.
- Mileage and vehicles. Every trip, including submitted and reimbursed ones, the vehicles, odometer entries, rates, rules, settings, the mileage audit trail, and every proof image. Raw location readings are removed first and unconditionally, before anything else in the transaction, because they are the most sensitive thing the account holds and must not survive a partial failure further down.
- Expenses and receipts. The expense ledger, the imported document rows that hold the extraction, and the stored original of every receipt and uploaded file.
- Text messages. Conversations, message bodies, MMS media, messaging numbers, automation settings, and consent and opt-out records. Nothing about your texting survives the account, so export first if you need the consent record for your own compliance file.
- Social publishing. Composed and scheduled posts, their per-platform targets, the publishing queue, and cached uploads held with the publishing provider. Deleting the queue is what stops anything still scheduled from being published after you are gone. Posts already published to a platform remain on that platform.
- Assistant and canvas. Conversations with VERA and their messages, assistant tasks, Content Studio project sessions and every card on their boards, and generated content images.
- Team. Your team members, their invitations, your custom roles, and the attributed activity trail, within your own business.
- Payments you take from your customers. Payment requests, schedules, milestones, payments, attempts, refunds, payouts, disputes and their evidence, fraud reviews, saved payment method summaries, and the payments audit log. Your connected Stripe account itself is yours, not ours, and is not closed by this.
- Billing and usage. Credit account and ledger, trial records and metering, reports, notifications, radar insights and articles, support requests you filed, commission rules and entries, estimate templates and custom fields, cost-source selections, any half-finished integration authorization, and the cancellation feedback you left, which is treated as your own words rather than as operator analytics.
- Your audit trail. The per-account audit events and security events recorded against your account.
5. What remains, and why
A small amount of information is not removed by account deletion. We would rather name it than imply a completeness we cannot deliver. This list is maintained against the database schema by an automated check, so a new kind of record cannot quietly join it.
- Your employment in someone else's business. If you were a team member or employee in another VERA business, that membership is closed rather than erased: it stops being live, and the account it named no longer exists, so it authorizes nothing. The row survives so that business's expense and mileage history keeps naming who filed each record. Those submissions are the business's records, not yours to withdraw, and anonymizing a year of a business's receipts is not what deleting your account should mean to them. Your own business, and everything in it, is deleted in full.
- Geocoding and routing cache. Addresses and routes looked up for mileage are cached under a hash of the normalized request, never the raw address, and never against an account. There is nothing in it to match to you, which is also why deletion does not sweep it. Entries expire on their own within 30 days.
- Stripe billing records. Your Stripe customer record, invoices, and payment history stay with Stripe under its own retention and under financial and tax record-keeping obligations. VERA cancels the subscription but does not erase Stripe's records.
- Platform admin audit log. If a VERA operator took an administrative action affecting your account (granting credits, extending a trial, suspending it), that operator accountability record is deliberately retained after the account is removed. It identifies the action and the target, not your business content.
- Rate-limit counters and webhook ids. Anti-abuse counters and webhook replay-protection records are keyed by address, IP, or provider event id rather than by account, and are not swept by deletion. They hold no business content and are overwritten or superseded in the ordinary course.
- Server logs. Operational logs held by the hosting provider rotate on that provider's schedule and are not individually purged.
- Provider-held backups. Managed database snapshots taken before deletion age out on the provider's cycle. Deleted data is gone from the live database immediately.
- Correspondence. Support email you sent us remains in our mailbox unless you ask us to delete it.
6. Consequences of deletion
Your subscription is cancelled. Deletion mid-term does not automatically generate a refund; see the Refund Policy.
Public estimate links stop working. If you have sent an estimate to a customer who has not yet accepted it, that link will 404 after deletion.
Scheduled posts, automations, and workflows stop. Anything queued but not yet executed will not run.
Unused credits, including purchased packs, are forfeited. They have no cash value and are not refundable on deletion.
Your email address becomes available for a new account immediately, not after 30 days. Signing up again creates a fresh, empty account; it does not restore anything, and it means the deleted account can no longer be restored to that address.
7. Alternatives to deleting
If you want to stop paying but keep your records, cancel your subscription instead. The account moves to a limited state at the end of the paid period and your data stays.
If you want to pause, cancelling and returning later is the current route. VERA does not offer an account freeze.
8. Deletion requests we handle by hand
If you cannot sign in, email support@myvera.io from the address on the account with the subject line "Delete my account". We verify the request against that address before acting.
If your personal data is in VERA because one of our customers put it there, contact that business. VERA cannot delete a record inside a customer's account on a third party's instruction; we will refer the request to the account holder and assist them, as the Data Processing Addendum requires.
Meta operates its own data deletion callback. If you request deletion of your data through Facebook or Instagram, VERA receives that request, revokes and purges the Meta connections on your account, and returns a confirmation code you can use to check the status.
Change history
Every revision of this document, newest first. Material changes are notified to account holders before they take effect where practicable.
- v1.2August 17, 2026
Corrected the claim that there is no grace period and no way to restore an account. Deletion now has a stated 30-day recovery window before permanent erasure, described in its own section, and the policy separates the effects that happen immediately (subscription, sessions, sign-in identities, scheduled posts, email release) from the erasure that follows.
- v1.1August 12, 2026
Removed the claim that deletion is a hard delete across every table. Added the mileage, expense, messaging, social, assistant, canvas, team and customer-payment categories now removed, and named the employment record in another business and the hashed geocoding cache among the records that remain.
- v1.0July 28, 2026
Initial Account Deletion Policy published.
Questions about this document?
Legal and contracts: support@myvera.io. Privacy and data rights: support@myvera.io. Security reports: support@myvera.io.
Related
- Privacy Policy
- Cookie Policy
- SMS Opt-In Policy
- GDPR Rights
- California Notice
- DPA
- Subprocessors
- Data Retention
This document is a carefully drafted policy written against how VERA actually works. It is not legal advice, and it should be reviewed by a licensed attorney in your jurisdiction before you rely on it.
