Privacy Policy
Conduit33 reads your email for a living, so this policy is specific rather than reassuring: exactly what is stored, exactly who else can see it, and exactly how to get it back.
Effective August 6, 2026
1. The short version
- We store the email you give us, and what we extract from it.
- We do not sell it, use it for advertising, or train machine-learning models on it.
- Every customer’s data is separated at the database level, not just in application code.
- Four third parties can technically see data because they run our infrastructure. They are named in section 5.
2. What we collect
Because you gave it to us
- Account details — email address, display name, the organisation you belong to and your role in it.
- Message content — the full text, headers and attachments of email you forward to a Conduit33 address, import, or authorise us to read from a connected mailbox.
- Workspace content — everything extracted from those messages (tasks, dates, amounts, people, references, commitments) plus anything you type: edits, comments, assignments and templates.
- Mailbox credentials — if you connect a Microsoft mailbox, the access and refresh tokens for it. These are encrypted at rest and are used only to fetch the mail you authorised.
Because the service generated it
- An audit log of significant actions in your organisation — who changed what, and when. This exists so you can answer that question, and it is visible to your organisation.
- Activity and read state — what changed since you last looked, so the daily digest can exclude your own actions.
- Basic usage events on public pages — the path, an event name and a label. No cross-site tracking, no advertising identifiers, and no third-party analytics service.
3. Why we hold it
To operate the service you asked for: parsing your mail, showing you the result, keeping it available across sessions, letting your colleagues see the same thing, sending the digest you enabled, and keeping the product secure and debuggable. We do not process your content for any purpose you would not expect from that description.
Where the GDPR applies, our lawful bases are performance of a contract (running the service), legitimate interests (security, abuse prevention, fixing faults) and consent where you have given it — for example by connecting a mailbox or enabling AI enrichment.
4. Who can see it
- You and your organisation. Members see workspaces according to their role.
- Anyone holding a share link. Share links are unguessable and read-only, but they need no account — treat one as public until you revoke it.
- Us, rarely and reluctantly. The operator can technically reach the database. We access customer content only to fix a fault you have reported or to meet a legal obligation, not to browse.
Separation between customers is enforced by PostgreSQL row-level security on every table holding customer data, with the policy forced so that even the table owner is subject to it. That is a database-level guarantee, so an application bug alone is not enough to leak another organisation’s data.
5. Third parties
These providers can technically access data because they run our infrastructure:
| Provider | Why | What they can see |
|---|---|---|
| Supabase | Database and authentication | All account and workspace data, including message content you import |
| Vercel | Application hosting, DNS and the domain registration | Request logs and anything transmitted while using the service |
| ImprovMX | Forwarding mail sent to our published contact addresses | Only messages you send to an @conduit33.network address |
| Microsoft | Optional mailbox connection, if you choose to connect one | Mail you authorise us to read via Microsoft Graph |
These are configured in the code but not currently enabled, so they receive nothing today. They are listed because they would begin receiving data the moment the feature is switched on, and finding that out later is unpleasant:
- Resend — outbound email delivery. Would receive: recipient address and message body of any mail we send you.
- Anthropic — optional ai enrichment of extracted fields. Would receive: message text submitted for enrichment.
We do not sell personal information, and we do not share it for cross-context behavioural advertising. We may disclose data if legally compelled, and will tell you unless we are prohibited from doing so.
6. Where it lives, and for how long
Data is stored in the United States. We keep it for as long as your account is active. Deleting a workspace deletes its messages, extracted items and comments.
Being straight about a gap:there is no self-service “delete my account” button yet. Email hello@conduit33.network and we will delete your organisation and its contents within 30 days. Building the button is on the roadmap; until it exists, saying so is better than implying otherwise.
Backups may retain deleted content for a short period before they rotate out. Audit log entries may be retained after related content is deleted, because a security record that can be erased by the person being audited is not a security record.
7. Your rights
Depending on where you live you may have the right to access, correct, export, delete or restrict processing of your personal data, and to object to it. Exercise any of these by emailing hello@conduit33.network. We will respond within 30 days and will not charge you or degrade your service for asking.
Most of your content is already exportable from within the product. If you need it in a form the product does not offer, ask and we will produce it.
8. Security
- Encrypted in transit (HTTPS) and at rest.
- Mailbox tokens encrypted with a separate application key.
- Row-level security enforced and forced on every customer-data table.
- Tenant isolation covered by an automated test suite run before deploys.
No system is perfectly secure. If you find a vulnerability, please report it to security@conduit33.network rather than disclosing it publicly first. If a breach affects your data we will notify you without undue delay.
9. Children
Conduit33 is a business tool and is not directed at anyone under 16. We do not knowingly collect their data; if we learn we have, we delete it.
10. Changes
If we change this policy in a way that materially affects how your data is handled, we will notify account holders before it takes effect. The effective date at the top of the page always reflects the current version.
11. Contact
Privacy questions and rights requests: hello@conduit33.network.
Security reports: security@conduit33.network.