Privacy Policy
Last updated May 22, 2026.
1. What this covers
This policy covers how Revint (“we”, “us”) handles information when you visit https://revint.dev or use the Revint product. It covers the marketing site, the authenticated app, and the data we ingest from third-party integrations you choose to connect.
2. What we collect — site visitors
We collect three categories of data from site visitors:
- Page-level traffic. URL, referrer, browser user agent, anonymised IP, screen size, and country. Recorded by our first-party analytics tracker (no third-party cookies are set).
- Submitted information. Email address, full name, company name, and anything else you type into a contact, demo, or pilot signup form.
- Inferred information. Industry vertical and company size derived from the company domain you provide. Used to route demo requests to the right vertical pack.
3. What we collect — customers
Once you sign in, Revint ingests data you authorise via OAuth: HubSpot company and contact records (plus the deal stages you select for closed-loop ingestion), Pipedrive or Close records (if connected), and SDR-level usage data inside the Revint dashboard.
Customer-content data is stored encrypted at rest with AWS KMS and in transit with TLS 1.3, isolated per workspace at the database row level.
4. How we use it
- To run the product — enrich your accounts, write fields into your CRM, sharpen your ICP from closed-won and closed-lost outcomes.
- To service your account — billing, support, security, and onboarding emails. We use Resend for transactional email delivery.
- To improve Revint — aggregated, non-identifying usage data informs product decisions. Customer CRM data is never used to train models.
- To meet legal obligations — tax records, audit logs, and lawful requests we are obligated to comply with.
5. What we never do
- We do not train our pattern-matching models on customer CRM data. Cross-workspace inference is impossible by construction.
- We do not sell your data. We do not rent your data. We do not enrich third-party datasets with your contacts.
- We do not set third-party advertising cookies on the marketing site.
6. Sub-processors
Revint runs on AWS (us-east-1, with EU/UK residency on Enterprise). We rely on the following sub-processors for specific functions: Supabase (auth), Stripe (billing), Resend (transactional email), Google Gemini (signal extraction). The full sub-processor list is maintained in our DPA.
7. Your rights
EU, UK, and California residents have rights of access, correction, deletion, portability, and objection. To exercise any of them, write to hello@revint.dev. We respond within 30 days.
If you cancel your subscription, you have 30 days to export your data through the Revint dashboard. After 30 days, the data is deleted per the retention policy.
8. Contact
Privacy questions: hello@revint.dev.
For the full Data Processing Agreement, request a copy via the demo form — we email the latest version on request.
