2 different relationships run side by side here, and they decide who answers a question about a piece of data.
Your own account records, your name, your email address and your billing history, are ours to look after as the controller. The reviews and reviewer details collected from your connected sources are yours: you are the controller and ReviewComet handles them on your instructions.
What is stored
Account and location records. Your name, email address, password hash, the locations you create, the people you invite and the role each was given. 2FA secrets and recovery codes where you enabled them.
Connected source credentials. For each source, the access token the site issued, the identifiers of the Page or listing it covers, the permissions you granted and the expiry. Tokens are encrypted at rest, on top of the encryption everything else gets, and are never shown back to you or to anyone in your location. Your Facebook password, or the password for any review site, is never received or stored at any point.
Reviews and reviewer details. For each connected source, the reviews left about your business. Each one carries its text, title and star rating where the site has them, when it was posted, its language, and the public identity the site attaches: display name, site user id, and a profile picture where the site gives one. Private feedback a customer sent you is stored the same way and never published. On top of that sits the reply record: the reply that went out or was copied, who or what wrote it, who approved it, and which rule acted on the review.
Nothing is collected about people who never reviewed your business.
Usage and technical records. Request logs for the app and the API, including IP address, browser user agent, action and time. Error reports. The aggregate counts behind your usage figures.
Payment records. Your plan, billing cycle, invoices, and the brand and last four digits of the card. Full card numbers go straight to the payment processor and never touch our servers.
How long each of them stays
The retention section of the privacy policy, listing each kind of data and how long it is kept.
- Reviews and replies: 1 year from the date the review arrived, then automatic deletion. An account owner or admin can set a different window per location, from 30 days up to 24 months, under Settings > Danger zone > Data retention.
- Action history: 24 months, on its own clock. Which rule fired, who acted on a review and when, is kept whatever window the location sets, so the record of what was done outlives the reviews it was done to.
- Access tokens: until you disconnect the source, the token is revoked, or the account closes, whichever comes first.
- Account and location records: for as long as the account is open, then 30 days.
- Invoices and payment records: 7 years, because tax law requires it.
- Request and security logs: 90 days.
- Email delivery records: 12 months.
- Backups: encrypted, rolling, and overwritten within 35 days. A deletion reaches the backups as they roll.
A new source starts with what the site lets us read when you connect it, which for a Facebook Page is its recent recommendations, and fills from that moment on.
Who else touches it
A small set of sub-processors, each under a written contract and each used for one purpose:
The sub-processor table listing each company, what it does and where it operates.
- Cloudflare runs the hosting, the application, the database and the storage, plus DNS and protection against attacks.
- Stripe handles cards, subscriptions, invoices and tax.
- Resend sends transactional email: alerts, digests, invitations and receipts.
- The AI sub-processors run the AI agents, translation and the drafted replies, and only for the features you switched on. They are named in full on the privacy policy, which is where that choice is recorded when it changes.
Our database and file storage are hosted in western Europe. Some processing happens elsewhere: AI requests may be served from the United States, which is why every AI feature can be switched off on its own, and reviews pass through Cloudflare's global network on their way in. Beyond that list, data is shared only where the law requires it.
The current list always lives on the privacy policy, and it is published there before a new sub-processor starts handling anything. If you need a copy of the data processing terms, or a question answered about a specific record, write to support@reviewcomet.com.