Privacy
What we hold, where it goes, and for how long
Six places your data can reach, listed in order, including the one that only exists if you switch it on.
Who is responsible for this data
- Registered business name
- Leela Aravind Karlapudi, trading as ITISYOU
- Registered address
- Lytchett House, 13 Freeland Park, Wareham Road, Poole, Dorset, BH16 6FA, United Kingdom
- Company registration number
- Not applicable (sole trader)
- VAT number
- Not VAT-registered
- Legal structure
- Sole trader
- Contact for legal notices
- support@itisyou.app
Where your data goes
-
Browser
Your browser talks to our application over HTTPS when you sign in, configure a workflow, or view results.
-
Cloudflare Workers and D1 (EU-West)
Our application runs on Cloudflare Workers, with data stored in Cloudflare D1, a SQL database, in the EU-West region. This is where your workspace configuration, source events and retained evidence live.
-
HubSpot
We read your contact records back from HubSpot, using the read access you grant us, to check them against your rules.
-
Resend
We read message status events back from your connected Resend account to check whether the acknowledgement email reached the point your rules require. Resend is also the service we use to send our own transactional emails to you: sign-in links, failure notices, deletion confirmations.
-
Stripe
Billing is handled entirely by Stripe hosted Checkout and the Stripe Billing Portal. Card details never reach our servers.
-
Optional model provider
Only if you turn on the optional AI assistant: the specific text needed to answer your request is sent to a model provider. The assistant is off by default and never decides a verification result, an access right, or a charge.
Subprocessors
| Subprocessor | Role | Data involved |
|---|---|---|
| Cloudflare | Application hosting, database (D1) and cron scheduling | All workspace configuration, source events and retained evidence |
| HubSpot | Customer-connected CRM evidence source (read access only) | The specific contact record fields your workflow rules reference |
| Resend | Customer-connected email evidence source (read access only), and our own transactional email sender | Message status events for the acknowledgement email your workflow rules reference; the transactional messages we send you (sign-in links, failure notices, deletion confirmations) |
| Stripe | Payment processing and billing management | Billing details and subscription status; we never see full card numbers |
| Optional model provider | Powers the optional AI assistant, only when a customer enables it | Only the text needed to answer the specific assistant request |
How long we keep evidence
30 days is a fixed system limit, not a per-customer setting.
Questions about your data
Do you store my customer data?
We store the specific pieces of evidence needed to check your rules, the CRM record fields and email status your workflow's assertions reference, and the source event your automation sent us, scoped to your workspace. We do not import or mirror your whole CRM. Evidence is kept for 30 days by default and then removed.
Is my data used to train anything?
No. Evidence we retrieve is used only to check your rules and show you results. If you turn on the optional AI assistant, only what is needed to answer your specific question is sent to the model provider for that request; the assistant can never decide a verification result, an access right, or a charge, and by default the assistant is switched off.
How long do you keep evidence?
30 days by default, then it is removed.
Do you use AI to decide whether a run passes or fails?
No. Verification is decided by the rules you set, evaluated against the evidence we read back; that logic never depends on a model. An optional AI assistant exists to help you with things like explaining a result or drafting a rule, but it proposes; it never decides a verification outcome, an access right, or a charge.