Security at Trilly

How we protect your account and your company's workspace, and what isn't done yet.

For your security review

What Trilly never sees
Your conversations with your AI. Skills run inside your own AI app. How information moves
How skills are checked
Every version, before anyone can add it. Skills
Certifications
None yet. Certifications
More answers: for your security review
Where data is stored and processed
Mainly in the United States, with Amazon Web Services. Where your information is kept
Is our data kept apart?
Not yet. A separate Trilly-only setup is planned. How information moves
What's encrypted
Stored files, off-site backups, and connections up to Amazon. Not yet the server's disk. What's encrypted, in full
Backups and recovery
Database backups every 15 minutes, checked by a restore drill every 4 weeks. Backups, and what isn't covered yet
Sign-in and access
Two-step login, passkeys, company sign-in (SSO) and SCIM. Your account and company workspaces
Audit log
Changes to a workspace's people, seats, skills, rules and settings are recorded. Company workspaces and sending it to Splunk or Sentinel
Incidents and breaches
A written plan to stop the harm and tell the people affected. If something goes wrong

Where your information is kept

  • In the United States: Amazon Web Services in Northern Virginia, and Anthropic for the safety checks. Payments (Stripe) and our own mailboxes (Fastmail) are in Australia and the United States. We can't keep your data in Australia today.
  • Your browser and your AI app reach Trilly over HTTPS. Inside Amazon's network, the last step to Trilly's server isn't encrypted yet; that's planned. The address trilly.io works over HTTPS only, with HSTS.
Show the rest: Where your information is kept
  • Stored files and the off-site backup copies are encrypted too. The database server's own disk isn't encrypted yet. Encrypting it is planned.
  • Payments are handled by Stripe. Trilly never sees your full card number.

How information moves

Who holds what, and where.

How information moves between you, your AI app, Trilly and the companies that help us run it.

Your AI app

Claude, ChatGPT, Copilot, Gemini and others. Your conversations stay here, with your AI provider. Trilly never sees them.

Your browser

trilly.io: your account, your settings and anything you buy.

Amazon Web Services, United States (Northern Virginia)

Every request comes through Amazon's network and web firewall first. Public pages and images may be kept for a short time in Amazon's data centres around the world.

The server Trilly runs on

The website, the Trilly connector and Trilly's own database. The server is shared today; Trilly has its own database and login on it.

File storage

Skill files, photos and logos, in Amazon S3.

Off-site backups

Copies of the database, kept in Amazon S3.

Email sending

Amazon SES sends Trilly's emails, such as receipts and password resets.

Backups and recovery

  • The database is backed up in full once a day, and every 15 minutes in between. If something went badly wrong, the database would lose at most the last 15 minutes of changes.
  • Each backup is copied off the server to Amazon S3, in the same region, encrypted with a key only Trilly uses. The server can add backups there but can't read or delete them. Backups are kept for up to 400 days, then deleted on their own.
  • The newest backups also stay on the server's own disk for 3 days, so, like that disk, they aren't encrypted yet.
  • Every 4 weeks we restore the newest backups into a separate copy of the database, check it for damage and compare it with the live one. The last drill, on 18 October 2026, passed.
  • Getting the database back takes minutes from the copies on the server: each drill does it. From the off-site copies we estimate a few hours. We haven't practised that yet.
  • The sign-in keys are backed up off the server too, and on 30 October 2026 we checked the copy can be restored. The server's other settings aren't in a confirmed backup yet, so if we lost the server, setting them up again would add time. That's a gap we'll fix.
  • Trilly runs on one server. If it failed, the site would be down until it was back. Rebuilding the server from nothing would take about a day. That's our estimate: we haven't practised a full rebuild yet, and there's no copy in a second region yet.

Your account

  • Passwords are stored as slow one-way hashes (PBKDF2 with SHA-512), never as the password itself. Common and easy-to-guess passwords are refused.
  • Five wrong tries pause sign-in for 15 minutes, and we email you when that happens.
Show the rest: Your account
  • Two-step login with an authenticator app, plus backup codes. The secret behind your codes is encrypted.
  • Passkeys: log in with your fingerprint, face or device PIN instead of a password. Your fingerprint, face or PIN never leaves your device.
  • Sign in with Google or Microsoft if you prefer.
  • See every device you're signed in on, and log out of any of them, or everywhere, from your security settings.
  • Email links (confirming your address, resetting your password) work once and expire.

Company workspaces

  • Company sign-in (SSO). OpenID Connect or SAML 2.0. We check every sign-in is signed by your identity provider, meant for Trilly, recent, and used only once. Companies can make it required for their email domains.
  • Backup (break-glass) owners. When company sign-in is required, only owners the company marks for emergencies, with two-step login on, can still use a password.
Show the rest: Company workspaces
  • SCIM. Your identity provider adds and removes people. Tokens are shown once and stored only as fingerprints. When someone is removed, their seats free up, unless you chose to keep them for leave. For accounts on your domain, their AI apps are disconnected and every session ends.
  • Session rules. Choose how long a sign-in lasts, and sign everyone out with one button.
  • AI app controls. Choose which AI apps work accounts may link to Trilly.
  • Audit log. Changes to a workspace's people, seats, skill list, rules and settings are recorded with who, when, from where, and before and after. It can be downloaded. It can't be edited, and it's kept for at least two years. On the Enterprise plan, it's built so your security tools, like Splunk or Microsoft Sentinel, can read it with a read-only token. We haven't tried it with a customer's own Splunk or Sentinel yet. Sending it to Splunk or Sentinel.
  • Private skills. Skills private to a company are only ever served to its active members. They never appear in search, public pages or sitemaps. Who owns them, and who sees them.
  • Data processing addendum. Owners accept our DPA in the workspace, and we record the version, the time and who accepted it. Owners, admins and auditors can export their workspace's data at any time.

Skills

Every version of every skill is checked before anyone can add it. Skills about money, betting, health, the law or your accounts also get our full review, and Trilly approves each version before it goes live. Each version gets its own fingerprint, so what you add is exactly what we checked. How we check skills.

If something goes wrong

We have a written plan for security incidents and data breaches. In short:

  • Trilly's owner leads every incident and makes the calls.
  • Whoever finds a problem stops the harm straight away, with the smallest switch that works: taking a skill down everywhere at once, locking an account, changing a leaked key, rolling back a release, or taking the site offline.
Show the rest: If something goes wrong
  • We keep the evidence. Nothing that matters is deleted, and the audit log is never changed.
  • For a likely data breach, a lawyer is told on day one. We follow Australia's Notifiable Data Breaches scheme: a suspected breach is assessed within 30 days, and if serious harm is likely we tell the people affected and the Office of the Australian Information Commissioner as soon as we can.
  • If a breach puts people in the European Economic Area (the EU plus Iceland, Liechtenstein and Norway) or the UK at risk, we tell the data protection authority where they live (in the UK, the Information Commissioner's Office), within 72 hours where we can, and we tell the people affected.
  • If a breach affects a company workspace, we tell its owners without undue delay, and within 72 hours where we can (our DPA, section 5).
  • Within two weeks we look back at what let it happen, and change it.
  • We haven't run a practice exercise of this plan yet.

What has gone wrong before, and what we changed: past incidents. To hear when something's wrong, turn on status emails or follow the feed on the status page.

Found a weakness in Trilly's security? How to report a security problem.

Companies that help us run Trilly

WhoWhat they doWhere
Amazon Web ServicesServers, database, file storage, file delivery and sending the site's emailsUnited States (Northern Virginia); file delivery keeps short-lived copies worldwide
StripePayments, invoices, payouts and makers' identity checksAustralia and the United States
FastmailOur own mailboxes, when you email usAustralia, with servers in the United States
AnthropicAutomated safety reviews of skill files, a company's private skills included (never anyone's conversations)United States

The same list is in our privacy policy and our DPA. Companies get 30 days' notice before we add a new one.

Certifications

We don't hold SOC 2, ISO 27001 or similar certifications yet, and we haven't had an independent penetration test yet. If your company needs answers for a review, contact us: once a year we answer a reasonable security questionnaire for companies on Trilly.

Contents: back to the list of sections