Troy runs the same business we built it for, so security isn't a checkbox — it's how we protect our own operation and yours. Here's how your data is kept safe.
Last updated: June 15, 2026
Troy is a multi-tenant platform: every customer has its own isolated workspace ("org"). Isolation is enforced at the database layer, not just in application code. Each table that holds customer records is protected by row-level security policies that restrict access to the rows belonging to the signed-in user's organization. A request that tries to read another workspace's data returns nothing — the rule is applied by the database on every query.
This means a sales rep at one company cannot see another company's leads, invoices, or messages, even in the unlikely event of a flaw in the front-end code, because the boundary lives below the application.
Sign-in is handled by a dedicated authentication service. Within a workspace, the account owner controls roles and permissions, so each person sees only the parts of the business they should — sales sees the pipeline, the warehouse sees fulfillment, and managers see the whole picture. Administrative access to production systems on our side is limited to personnel who need it and is protected accordingly.
Billing is processed by Stripe, a PCI DSS Level 1 certified payment provider. Card details are entered directly with Stripe's secure checkout and are never stored on Troy's servers. We retain only the billing metadata needed to manage your subscription (such as plan, status, and a Stripe customer reference).
When you use the in-app AI assistant, your prompt is sent through a server-side function to our AI provider (Anthropic) to generate a response. The API key that authorizes those calls is held server-side only and is never exposed in the browser. We do not use your Customer Data to train AI models.
We build on established, security-focused providers rather than running our own data centers:
| Provider | Role |
|---|---|
| Supabase (on AWS) | Database, authentication, file storage — with row-level security enforcing tenant isolation |
| Netlify | Application & site hosting and serverless functions, served over HTTPS |
| Stripe | PCI-compliant subscription billing and payments |
| Anthropic | Powers the AI assistant; receives only the prompts you submit |
| Resend | Transactional and notification email delivery |
A current list of sub-processors and the data each handles is in our Privacy Policy.
Customer data is stored on managed infrastructure with provider-level redundancy and automated backups. We aim for high availability and monitor the Service, while recognizing that no online service can guarantee uninterrupted operation.
API keys, signing secrets, and service credentials are stored as protected environment variables in our hosting platform and are never committed to source code or exposed to the browser. Webhook payloads sent on your behalf can be signed so receivers can verify authenticity.
You can export your data at any time while your account is active, and you can delete it. We do not sell your data, and we do not use Customer Data for advertising or model training. See the Privacy Policy for retention and deletion detail.
We welcome reports from security researchers. If you believe you've found a vulnerability, please email [email protected] with details and steps to reproduce. Please give us a reasonable chance to investigate and fix the issue before any public disclosure, and avoid accessing or modifying other users' data while testing. We will not pursue good-faith research that follows this guideline.
If we become aware of a security incident affecting your data, we will investigate promptly, take steps to contain and remediate it, and notify affected customers as required by law and our agreements.
This page describes Troy's security practices in good faith and in plain language. It reflects how the platform is built today and may evolve as the product does.