Updated May 2026 ยท Counsel-reviewed

Privacy & data handling.

Read-only inbox access. Local cache, never on our servers. No ad trackers, ever. What Roloflow touches, where it lives, and what we deliberately don't do - in plain English. Email alan@tapcre.com if anything's unclear.

What Roloflow touches

CategoryWhatWhy
Email metadatasender, recipients, subject, date, thread idmatch threads to contacts
Email bodiesplain text body of each threadsent to Anthropic Claude for classification
Contact dataname, email, company (if you uploaded CSVs)seed contact rows
Classification outputrole, interest tags, deal stage, summary, evidence quotepopulate the XLSX
Billing stateplan id, status, customer/subscription ids, usage countersenforce quota (managed tier)

Where it lives

StoreContentsOperator
Local SQLite Threads (including body text), contacts, extractions, batch metadata, usage counters, license cache. Lives on your machine at data/roloflow.db. You
Unipile Your mailbox content under the authorization you granted. Unipile
Anthropic Each thread body + the system prompt, for the duration of a Batch call. Output stored per Anthropic's policy. Anthropic
Stripe Customer + subscription records. Stripe
Roloflow servers (managed-tier webhook) Event metadata only - id, type, livemode. Never event payloads. Never email content. Roloflow

What Roloflow does NOT do

The local cache, explicitly

The cache lives only on your device. Roloflow's servers never see it. Each thread body you ask Roloflow to classify is held locally in a SQLite file so a killed process can resume without re-fetching from Unipile.

Your rights

Third-party processors

Roloflow uses these processors. Their policies govern data we send to them:

Contact

Privacy questions: alan@tapcre.com.