How we protect your inbox, your consultants' data, and your clients' data.
Last updated: October 22, 2026
Project Shield connects to your agency's shared email inbox to triage requests and draft replies. We know what that means: the people who run this service can technically see what's in that inbox. Given how often data breaches make the news, we think you deserve a direct, specific answer to "how do you actually protect this," not a marketing page. This page is that answer.
Email subjects, bodies, AI-generated summaries, and draft replies are encrypted in the database (AES, via a server-side key never stored alongside the data). A stolen database backup or an exposed disk does not hand over readable email content.
IMAP app passwords and Gmail/Outlook OAuth tokens are encrypted at rest with the same mechanism, and are never written to application logs.
Every ticket, every consultant record, every teammate account belongs to exactly one company. The application enforces this on every database query — one customer's staff can never query another customer's data, by design, not just by convention.
Any staff account can require a time-based one-time code (TOTP, the same standard used by Google Authenticator and Authy) in addition to a password, plus one-time recovery codes for lost devices. We recommend enabling this for account owners.
Our support team does not need, and does not have, blanket access to your inbox content through normal use of the product. If we ever do sign in to your account to help debug an issue, that access is recorded — who, and exactly when it started and ended — and you can see that record yourself any time in Settings → Support access log. We don't send a real-time alert for every support touch (that would make ordinary troubleshooting feel alarming), but we never hide it from you after the fact.
Repeated failed password or 2FA-code attempts against an account trigger a temporary lockout, so credential stuffing and code-guessing attacks don't get unlimited tries.
All access to Project Shield, in the browser and via API, is served over HTTPS/TLS. Session cookies are marked Secure in production, so they are never sent over an unencrypted connection.
Within your company, we support two roles: owner (can manage billing, connect or disconnect the shared inbox, and add or remove teammates) and staff (can work tickets and view the talent roster, but cannot change account-level settings). Only accounts you explicitly add can sign in to your company's data — there is no shared or default account.
On our side, only a small number of named operator accounts can access the administrative tools at all, and the "view as a customer" support tool described above is the only way any of us can see inside a specific customer's account — every use of it is attributed to a named operator account and logged as described.
The production database runs on a managed PostgreSQL service with continuous point-in-time recovery; depending on plan tier, this allows restoring to any point within the last 3–7 days. We also take periodic manual exports as an additional safeguard against provider-side incidents. No backup system eliminates all risk, but your data is not resting on a single, unprotected copy.
We rely on a short, named list of subprocessors to operate the Service — we do not sell or broadly share your data:
See our Privacy Policy for the full data-handling picture, including how this applies under Japan's APPI, the EU/UK GDPR, the CCPA, and the UAE's PDPL.
Our infrastructure and AI subprocessor currently operate out of the United States. If your company is established in, or your end clients/consultants are located in, a jurisdiction with its own cross-border transfer restrictions — including the United Arab Emirates (PDPL) or the EU/UK (GDPR) — we will sign a Data Processing Agreement with appropriate transfer safeguards (such as Standard Contractual Clauses or an equivalent mechanism recognized under the relevant law) before you submit personal data to the Service. Contact us at the address below to request our DPA template.
If you believe you've found a security vulnerability in Project Shield, please tell us before disclosing it publicly, so we can investigate and fix it: projectshiedexam@gmail.com. We will acknowledge reports promptly and keep you updated as we investigate.