This policy describes what data trustyourinbox collects, why we collect it, who we share it with, and your rights. Plain English, no legalese theater. If something here is unclear, and we'll fix it.
trustyourinbox is an email security and deliverability service built around DMARC monitoring. We do not share data with advertisers. We do not run behavioral tracking for advertising. The product is built around the principle that what you publish in DNS is yours, and what flows through DMARC reports is yours.
From customers who sign up:
- Account info: your email address and any name you provide, managed by Clerk (our authentication provider). We see what Clerk sees.
- Domain names you add to monitor.
- DMARC aggregate reports sent to your unique RUA address. These XML reports contain sending IPs, alignment results, and message counts: they do not contain message bodies, recipients, subject lines, or any private email content. They are themselves designed to be aggregate data only.
- Forwarded messages for Delivery Diagnosis: the original message, including its body, stored temporarily while we analyze it. The case retains message headers, the subject and diagnostic evidence, which can include email addresses and delivery-error details.
- Audit log entries for actions you take in the dashboard (domain added, paused, deleted, sender identified, digest preferences changed, etc.).
- Product-usage analytics, collected first-party and used only to operate and improve the product, never for advertising and never shared. For signed-in use we record which dashboard pages and features are used and by which account seat, how long a page was actually visible, the path taken between pages within one browser tab, and named interface interactions from a fixed list (for example "opened the DMARC explainer" or "copied the SPF record"). We never record what you type: no keystrokes, no free-text field contents, no search-query text, and no screen or session recording of any kind. When you search our documentation or help center we record that a search happened, how long it was and how many words, how many results came back, and which article you opened, so we can find the questions our writing does not answer. The words you searched for are never stored. Pages viewed in one visit are grouped by a random id that lives only in your browser tab and expires when you close it. We also record coarse context about the visit (device class, browser family, country, and timezone), page-speed timings, and whether a visit arrived from one of our own emails or notifications, which is marked as such. Operator staff see this data account-by-account to support you and improve the product; it is covered by our Data Processing Agreement with your organization.
- Plan + billing info (handled by Stripe).
From anonymous visitors using our public tools:
- What you enter into our free tools: a domain name, message headers, or a DMARC report, depending on the tool. Domain checks are public-DNS lookups. We use what you enter to run the check and don't store it long-term.
- IP address for rate limiting: each tool limits how many checks one IP address can run. Held only in short-lived rate-limit counters, gone within an hour.
- Aggregate page-view and tool-usage data, collected first-party on our own servers. For each page view we record the page URL, the referring site, any campaign tags in the URL, the country/region/city, timezone, and network (the autonomous-system number and operator name, which tells us datacenter traffic from human traffic) that Cloudflare derives from the request, your browser and device type, language and screen size, and how the page was used: how long it was actually visible and how far you scrolled. When you run a free tool we record which tool ran and whether it succeeded, never what you typed into it. If the address you arrived on carries an ad-platform click marker we record that the visit was an ad click, never the marker's value. We never store your IP address. Daily visitor counts use a hash that rotates every 24 hours, so it cannot identify you or follow you across days. Pages viewed in one visit are grouped by a random id that contains nothing about you and cannot connect two visits. It is held both in your browser tab and in a cookie on our own domains that expires when you close your browser, so that one visit still reads as one visit when it carries on into our app, documentation, or help center. If you sign in during that visit, we link it to your account from that moment onward, so we can tell whether the pages you read answered your question. That link is never applied backwards: anything you read before signing in stays anonymous permanently, including earlier the same day. No cross-site tracking, no advertising identifiers.
- Message bodies, recipient addresses or subject lines from DMARC aggregate reports: those reports do not contain them. Messages you choose to forward for Delivery Diagnosis are handled as described above.
- Tracking cookies for advertising. We set three kinds of first-party cookies: Clerk's session cookie (essential for authentication); a small "first page" cookie on the marketing site that remembers the first page and referring site that brought you here, so if you later sign up we know which content worked, which contains no identifier of any kind and expires after 90 days; and a random visit id that lets one visit read as one visit across our sites and expires when you close your browser. None are shared with third parties, and none are used for advertising.
- Third-party trackers (Google Analytics, Facebook Pixel, Mixpanel, etc.).
- Personally identifiable behavioral data linked to your identity for marketing.
We use a small number of trusted vendors to operate the service:
- Clerk: authentication. Stores your email + password hash + session.
- Cloudflare: hosting, DNS, R2 (raw DMARC and TLS reports, and forwarded bounces for Delivery Diagnosis), Workers, Email Routing.
- Neon: Postgres database hosting.
- Anthropic: Claude API for two features. The in-app help assistant receives the question you ask, the recent turns of that conversation, and excerpts from our own documentation. The acceptable-use check that runs when you add a domain receives the domain name and the title and opening text of its public homepage. We do not send your DMARC report data. We operate under a Zero Data Retention (ZDR) agreement with Anthropic, which means Anthropic does not log or store our API inputs and outputs.
- Resend: outbound transactional email (digest reports, alerts).
- Stripe: payment processing. They see card details; we don't.
We do not sell data. We do not share customer data with anyone outside the vendors listed above. We comply with lawful requests for data only when legally required, and will notify the affected customer unless legally prohibited.
- Account data: while your account is active. Deleting your account removes it immediately and it cannot be restored; copies in our database backups age out within 7 days.
- Support tickets: the messages and files you send our support team, kept for up to 24 months after the ticket is closed, including after you delete your account.
- Raw DMARC and TLS reports in Cloudflare R2, as mailbox providers send them: kept with no set deletion date, including after an account is deleted, so a report can be read again. They carry sending IP addresses, message counts and authentication results, never message content.
- Forwarded bounces for Delivery Diagnosis, in Cloudflare R2: the original message, including its body, is stored temporarily and deleted once analyzed, within 7 days at most. The case, including its headers, subject and diagnostic evidence, is kept for 90 days.
- Parsed DMARC reports: kept 14 months, or until you delete your workspace if that comes first.
- Archived MSP clients: archive pauses a client and keeps its data. Delete removes it. An archived client stops billing, and its data is kept, with reports for its domains still arriving and kept for the periods above, until you restore or delete it. Deleting a client removes its domains, parsed reports and settings within 7 days; raw report files are kept as described above.
- Audit log: kept while your workspace is active.
- Free tool inputs: not persisted; only the IP address is held in short-lived rate-limit counters (max 1 hour).
- Data sent to Anthropic: not retained by Anthropic. Our Zero Data Retention agreement means API inputs and outputs are not logged or stored on Anthropic's side.
You can do any of the following. For data access, export, deletion, or objection requests, :
- See and edit your account info via the dashboard, or ask us to.
- Export your data yourself, any time: CSV and JSON exports are built into the dashboard on every plan. If you need something the export buttons don't cover, ask and we'll provide it.
- Delete your account at any time. Account data is removed immediately and backup copies age out within 7 days. Removed domains are hard-purged after 7 days. Support tickets are kept for up to 24 months after they close.
- Object to specific data uses.
Residents of the EU/UK have the rights described under GDPR (access, rectification, erasure, portability, objection). California residents have rights under CCPA. We treat all customers to the higher of any applicable standard.
trustyourinbox is intended for business use. We do not knowingly collect data from anyone under 13. If you believe a child has signed up, and we'll delete the account.
If we materially change what we collect or how we use it, we'll email customers in advance and update the "Last updated" date at the top. Material changes apply only prospectively.
Questions, requests, or concerns? . We reply within 2 business days.
See also Terms of Service · Acceptable Use Policy · Security · Data Processing Agreement · Subprocessors.