Effective Date: October 10, 2026
This Privacy Policy explains how Revive Sales (“we,” “us,” or “our”), operating from 16842 NE 39th Ct, Apt C1010, Redmond, WA 98052, collects, uses, stores, shares and protects information when you use the Revive Sales platform at revivesales.app (the “Service”). It should be read with our Terms of Service, Security page and Data Processing Addendum.
In short: we collect what we need to run the Service; we use your sales pipeline data only to produce your briefings, signals and suggested messages; we do not sell your data or use it for advertising; we do not use it to train AI models; we share it only with the service providers listed below; and you can delete it by closing your account.
Customer Data is the information about your own sales pipeline that you upload or connect, such as company names, contact names, deal details, sales notes and CRM fields. For Customer Data, you are the controller (or “business”) and Revive Sales acts as your processor (or “service provider”): we process it only on your instructions to provide the Service. Our Data Processing Addendum applies to Customer Data, and a countersigned copy is available at support@revivesales.app.
Account Data is information about the people who use the Service (sign-in details, billing status, usage). For Account Data we act as the controller.
The Service is not designed for sensitive personal data (such as health, financial account, government ID or children’s data). Please do not upload it.
We do not use Customer Data for advertising, and we do not sell personal information.
If you connect HubSpot, you authorise Revive Sales through HubSpot’s standard OAuth screen. We request permission to read deals, contacts and companies, and to update deals so that outcomes you log can be written back. We also ask, as an optional permission you can decline, to read the sales emails HubSpot has logged on your deals, so Revive can notice when a prospect replies, stop follow-ups, and draft your response. We read only replies on deals you have contacted through Revive, never send email, and do not store email content beyond the reply text and summary shown to you in your workspace. We store the access and refresh tokens HubSpot issues, encrypted by us before storage, in a table that browsers cannot read. We use them only to run your syncs and write-backs.
You can disconnect at any time from the Service or from HubSpot. When you disconnect, or close your account, we delete the stored tokens and ask HubSpot to revoke our access. Connecting or syncing HubSpot may replace or update the dormant-pipeline accounts in your workspace with data from your HubSpot account.
Sending and tracking. Revive does not connect to your Gmail or Outlook account and cannot read your mailbox. When you choose to send an email Revive drafted, we open a compose window in your own Gmail or Outlook with the draft filled in, and you review it and click Send there. The compose link includes a hidden blind-copy (BCC) address at our email provider, Resend, so that Revive can see that you sent the message. We receive that blind copy, use it only to match it to the account in your workspace, record the send, and start your follow-up timer. We do not read your other email. If you remove the BCC address before sending, Revive will not know the email was sent and you can mark it sent yourself. When you log an outcome or a send, Revive adds a note to the related HubSpot deal (a short activity summary), and it may read the HubSpot contact property that shows whether a contact has replied.
If your workspace owner connects Apollo, they authorise Revive Sales through Apollo’s standard OAuth screen so that your team can verify or find a contact’s email. We store the access and refresh tokens Apollo issues, encrypted by us before storage, in a table that browsers cannot read. We use them only to run lookups that a person on your team starts by clicking. For each lookup we send Apollo the contact’s name, the company name, or the email address being verified, and Apollo returns the matching email address and its status. Lookups use credits from your own Apollo account, and Apollo’s terms and privacy policy apply to them. If you find an email for a CRM contact who had none, we save it in Revive only; we do not write it back to your CRM.
You can disconnect Apollo at any time in Settings. When you disconnect, or close your account, we delete the stored Apollo tokens. Apollo does not offer us a way to revoke access, so you can also remove Revive Sales from your Apollo account settings.
The Service uses artificial intelligence to analyse sales notes and generate signals and suggested messages. To do this we send our AI provider, Anthropic, the company names, contact names, deal details and sales notes it needs for the request. We use Anthropic through its business API on our behalf. We do not use Customer Data to train AI models.
To find live market signals, we send our search provider, Tavily, company names and short search phrases derived from your notes (not your full notes). AI-generated output is a suggestion only. It can be incomplete or wrong, and you are responsible for reviewing it before acting. We do not use AI to make decisions about individuals that produce legal or similarly significant effects.
We use these service providers (subprocessors) to run the Service. They process data on our behalf under written terms and may not use it for their own purposes.
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase | Database and authentication | Account details, pipeline data, signals, outcomes, encrypted CRM tokens |
| Vercel | Application hosting | All traffic to the Service; server logs |
| Stripe | Payments and subscriptions | Billing details and subscription status |
| Resend | Email delivery | Recipient email address, email content, link-click events, and the blind-copy of emails you send from your own email account so Revive can record them |
| Anthropic | AI analysis | Company names, contact names, deal details, sales notes |
| Tavily | Web search for market signals | Company names and short search phrases |
| HubSpot | CRM you choose to connect | Data flows only when you connect it |
| Apollo | Email lookup you choose to connect | Contact name, company name or email address, only when someone on your team clicks a lookup |
| Optional sign-in | Name and email when you choose Google sign-in |
Browser push notifications are delivered through your browser vendor’s push service. We will notify customers by email before adding a subprocessor that handles Customer Data. We may also disclose information where required by law or valid legal process, to protect rights, safety or security, or in connection with a merger, acquisition or sale of assets (we would tell you and the new owner would remain bound by this policy). We do not sell, rent or trade your data.
Each workspace’s data is separated using row-level security in the database, and server-side checks confirm the workspace behind each request. Other customers cannot access your Customer Data.
| Data | How long we keep it |
|---|---|
| Account Data | While your account is active; deleted when you close it |
| Referral source | Stored with your account while it is active; deleted when you close it |
| Customer Data and signals | Until you delete it or close your account |
| HubSpot tokens | Until you disconnect or close your account; we also ask HubSpot to revoke them |
| Apollo tokens | Until you disconnect or close your account |
| Billing records | As long as needed for tax, accounting and legal obligations (held by Stripe and by us) |
| Audit log entries | As long as needed for security and accountability; they record actions, not CRM content |
| Server and email logs | A limited period set by our hosting and email providers |
| Support messages | As long as needed to help you and keep a record of the request |
| Backups | Copies in our database provider’s backups are removed when those backups expire |
You can close your account in the Service (Briefing, Settings, Close your account). This cancels any active subscription, ends our HubSpot and Apollo access, and deletes your workspace, uploads, accounts, signals and login. You can also request deletion at support@revivesales.app. If your workspace has other team members, they must be removed first so a team’s data is not deleted by accident.
Data is encrypted in transit with TLS and at rest by our database provider. Passwords are hashed. CRM tokens are additionally encrypted by us before storage. Access to each workspace is enforced with row-level security, billing fields cannot be changed from a browser, our HubSpot sign-in flow uses signed, time-limited state, sign-in, sign-up and account-lookup endpoints are rate limited, key account actions are logged, and the site sends standard security headers. Access to production systems is limited to authorised personnel. No system is perfectly secure, and we cannot guarantee absolute security. We are not currently SOC 2 certified. More detail is on our Security page.
If we become aware of a breach of security affecting your personal data, we will notify affected customers without undue delay and share what we know to help you meet your own obligations. To report a vulnerability, email support@revivesales.app with the subject “Security”.
Depending on where you live, you may have the right to: access the personal information we hold about you; correct it; delete it; receive a portable copy; object to or restrict certain processing; withdraw consent where we rely on it; and not be discriminated against for exercising these rights. You can access and update your account information in the Service, export your Customer Data through its export features, disconnect HubSpot, and delete your account and data as described above.
To exercise a right, email support@revivesales.app. We may need to verify your identity first. We aim to respond within 30 days (or within 45 days where California law applies, and we will tell you if we need longer). If we decline a request you can ask us to reconsider by replying to our response. If your information is Customer Data that a business uploaded, we will usually refer you to that business, which is responsible for the request, and we will assist it. An authorised agent may submit a request on your behalf with proof of authority.
You may also lodge a complaint with your local data protection authority or, in the United States, your state attorney general.
In the past 12 months we have collected the categories of personal information described in section 3 (identifiers such as name and email; commercial information such as plan and subscription; internet and device activity; and professional information contained in Customer Data) for the purposes in section 4, and disclosed them to the service providers in section 7 for business purposes.
We do not sell personal information or share it for cross-context behavioural advertising, and we do not knowingly sell or share the personal information of anyone under 16. We do not use or disclose sensitive personal information for purposes that would require a right to limit.
We use essential cookies for sign-in and session management. If you arrive through a referral link, we set a first-party cookie called referred_by for up to 90 days so we can credit the referral when you sign up. We do not use analytics cookies, advertising cookies or third-party tracking cookies. Because we do not track you across other sites, we do not respond to Do Not Track signals; we do honour opt-out preference signals such as Global Privacy Control by not selling or sharing your information, which we do not do in any case.
The Service is operated from the United States. If you use it from outside the United States, your information is transferred to and processed in the United States. If you are in the European Economic Area, the United Kingdom or Switzerland, our legal bases are described in section 4, and where law requires a transfer mechanism we rely on the Standard Contractual Clauses (with the UK addendum where applicable), which we will sign on request.
The Service is a business tool and is not directed at children under 16. We do not knowingly collect personal information from children under 16. If you believe we have, contact support@revivesales.app and we will delete it promptly.
We may update this Privacy Policy from time to time. We will notify you of material changes by email and by updating the effective date above. Continued use of the Service after the effective date means you accept the updated policy.
For privacy or security questions, contact support@revivesales.app or Revive Sales, 16842 NE 39th Ct, Apt C1010, Redmond, WA 98052.