Privacy Policy

Last updated: September 17, 2026

This policy explains what REVIVE ("REVIVE," "we") collects when a business ("you," "Customer") connects a data source - HubSpot, or an uploaded Excel/CSV file of your pipeline - and uses the product, why, where it lives, who can see it, how long we keep it, and exactly what an AI provider receives if you turn on voice recovery.

1. What we collect, and why

From your HubSpot account, if you connect it: contact records (name, email, phone, lifecycle stage, and the specific custom properties you map to REVIVE in Setup), deal records (amount, stage, close date), meeting records (outcome, timestamp), and the calls/notes/tasks REVIVE creates on your behalf. This is collected to run the core analysis - finding leads with slow or missing follow-up and pricing the gap. REVIVE reads only Contacts, Deals, Meetings, and Engagements - no other HubSpot object.

From an uploaded spreadsheet, if you use that instead: whatever columns you map in Setup - typically name, email, phone, lead source, dates, deal value, consent, and do-not-call status. Nothing in the file beyond the columns you explicitly map is used for analysis. The file itself is processed to extract this data and is not permanently stored as a document.

From you directly: your account email, workspace name, and the configuration choices you make in Setup (field mappings, calling hours, holdout percentage). Needed to run your account and apply your settings correctly.

Automatically: an append-only audit log of every analysis, recommendation, approval, and outreach action taken in your workspace - kept so you (and we) can always reconstruct why REVIVE did something. It is never editable, including by us. REVIVE also derives Recovery Patterns from your own workspace's completed analyses - statistical summaries (which type of lead responded to which intervention, and by how much) computed from your aggregate outcomes, not from any single lead's individual record, and never shared with or derived from any other customer's workspace.

2. Where it's stored

In Supabase's hosted Postgres database (AWS, us-east-1, United States) and served by the application running on Vercel (also US-hosted). HubSpot access tokens are encrypted at rest (AES-256-GCM) before being stored - never saved or logged in plaintext.

3. Who can access it

Your own team sees only your workspace, gated by your login and role (manager or sales employee). We don't have a support team beyond the founder at this stage - operator access is limited to whoever is operating REVIVE directly, for the sole purpose of running the service, troubleshooting a problem, or providing support you've asked for. The operator does not use workspace access to compete with you, to build a product for another customer, or for any purpose unrelated to operating REVIVE.

Operator access to a workspace is not silent: every such visit is written to that workspace's own append-only audit log (the same one described in Section 1), labeled as operator access and distinguishable from anything your own team did. Any manager on your workspace can review this at any time on the Audit log page. Nothing about this record can be edited or deleted by the operator, including retroactively.

Three infrastructure subprocessors touch data to make the product work: Supabase (database and authentication hosting), Vercel (application hosting), and, only if you configure voice recovery, ElevenLabs (see Section 5 for exactly what they receive). We don't sell data, and we don't share it with anyone else.

4. How long we keep it

During a pilot: under the Pilot Agreement, all cached CRM/spreadsheet data, normalized records, and pipeline logs are permanently deleted within thirty (30) days of the pilot ending, whether it runs its full course or is terminated early.

For an ongoing paid account: we retain synced data for as long as your workspace stays connected. Disconnecting your data source (HubSpot or a spreadsheet) stops all further syncing immediately, takes an encrypted backup of your lead and deal records at that moment, and removes them - along with any analysis, recommendations, and learned recovery patterns generated from them - from active use, so a later reconnect can restore your history, but a disconnected workspace shows no stale analysis and drives no further outreach. The audit log is retained after disconnection either way, since its whole purpose is a permanent record of actions already taken - not new source data, just a log of what REVIVE did and when.

5. What an AI provider receives (voice recovery only)

Voice recovery is optional and is off by default - a workspace only reaches an AI voice provider if you explicitly configure an agent and phone number in Setup. For your pilot specifically, voice recovery is not configured, so nothing in this section is currently active.

If and when it is turned on, here is exactly what goes to ElevenLabs (the voice provider) for each approved call, field for field: the lead's phone number (required to place the call), the lead's first name only (never last name), your company name, the lead's source (e.g. "Referral"), and the date they first inquired. Nothing else about the lead - no email, no deal value, no notes, no other HubSpot property - leaves REVIVE's systems.

REVIVE only ever calls a lead whose mapped HubSpot consent property indicates they agreed to be called; leads without that consent, marked do-not-call, or lacking a valid phone number are always routed to a human task instead - never to the AI provider.

After the call, ElevenLabs sends back a structured outcome (e.g. "appointment requested," "not interested"), an AI-generated text summary of the call, and its duration. REVIVE stores that summary and outcome - not the raw audio or a full transcript. The recording and full transcript are retained on ElevenLabs' own platform, under ElevenLabs' own data-retention terms, not ours; before enabling voice recovery for any real customer, review ElevenLabs' data processing terms directly and put a data processing agreement in place if your customer's data warrants one.

6. How to disconnect or delete your data

Click Disconnect next to HubSpot on your Setup page at any time - this immediately revokes REVIVE's stored access token and stops all syncing. To request deletion of already-synced data, email lrewti@gmail.com; pilot workspaces are deleted automatically within 30 days of the pilot ending regardless (Section 4).

7. Telemarketing and consent law

You remain responsible for ensuring your own lead-generation and consent-capture practices comply with TCPA and other applicable telemarketing law in your jurisdiction. REVIVE enforces the consent field you map to it, but cannot verify how that consent was originally obtained.

8. Your rights

You can request a copy of the data we hold for your workspace, or request its deletion, at lrewti@gmail.com. If you're in a jurisdiction with statutory data-subject rights (GDPR, CCPA, etc.), those rights apply and we'll respond within the timeframe the law requires.

9. Changes to this policy

We'll post any material changes here and update the date above. Continued use of REVIVE after a change means you accept the updated policy.

10. Contact

Lorenzo Rewti, an individual doing business as REVIVE (sole proprietorship) · 11300 NE 2nd Ave, Miami, FL 33168 · lrewti@gmail.com