HTTPS in transit, AES-256-GCM for credentials
The platform is served only over HTTPS. Credentials are encrypted with AES-256-GCM and the key is held outside the database: OAuth tokens, API keys, SMTP passwords and SSO secrets are encrypted at field level before they are written.
- TLS in transit
- AES-256-GCM field encryption for credentials
- Encryption key held outside the database
Role-based access with an audit trail
Every query is checked on the server against the caller's workspace, not just in the interface, and a build-failing test counts the places that bypass those checks. Within a workspace, permissions follow the member's role. Record changes, exports and LP document views are written to an audit log with the acting user, time and, where available, IP address — and audit entries cannot be edited or deleted through the API.
- Role-based permissions
- Workspace isolation
- Append-only audit log (via the API)
- SAML or OIDC SSO on every plan
- SCIM provisioning (Enterprise)
Managed, replicated infrastructure
The platform runs on managed cloud infrastructure, served only over HTTPS. The database runs as a replicated cluster, so losing one machine loses no data. Ask us for the current backup schedule and recovery targets — we will put them in writing rather than on a banner.
- Managed hosting
- Replicated database
- HTTPS only
- DDoS protection
Export everything, whenever you like
Your data is yours. A workspace admin can export every record, the uploaded files and the audit log in one archive with a manifest and checksums, whenever they like, from Settings. Files are included up to 5 GiB in total; any past that ceiling are listed in the manifest and sent on request. After termination, email privacy@tenyq.com within 30 days and we send you an export; we then delete your data from production systems within 30 days, and backups age out on their own cycle. The fund remains responsible for its own record-keeping duties.
The database runs on a replicated cluster. Backup schedule and recovery targets are provided in writing on request, and so is the region where your data is stored.
We publish our subprocessor list, give 30 days' notice before it changes, and you have the right to object. If we confirm a security incident affecting your data, we notify you within 72 hours of confirmation.
- Full export from Settings
- Manifest and checksums in every archive
- Export on request for 30 days after termination
- Deletion from production within 30 days after that
- 30 days' notice of subprocessor changes
- Incident notice within 72 hours of confirmation
- Backup targets and data region on request
We are preparing for SOC 2
We are preparing for SOC 2. We do not hold a report today, and this page will say so when we do. Our data processing is aligned with GDPR and CCPA, and a Data Processing Agreement — GDPR Article 28, with Standard Contractual Clauses for international transfers — is available.
- Preparing for SOC 2
- GDPR- and CCPA-aligned data processing
- DPA available
Rate limits, lockouts and failed-action tracking
Sign-in, sign-up and public endpoints are rate limited. An account is locked for ten minutes after five consecutive failed sign-ins. Exports and views of sensitive records are recorded in the workspace audit log, where admins can review them, and every export carries the name of the person who made it. Automated access is not allowed under our Terms: no bots, scrapers or AI agents outside our documented APIs, and sign-up refuses temporary inboxes.
locked · 10 min
- Rate limiting + throttling
- Lockout after 5 failed sign-ins
- Failed actions in the audit log
- Admin-visible audit trail
Breach notification under the DPA
Security reports go to security@tenyq.com. Customers who sign our DPA are notified of a personal data breach affecting their data without undue delay, and within 72 hours of confirming it, with what is known about its scope and the steps taken.
- security@tenyq.com
- Breach notification within 72 hours of confirmation
- Audit log available for investigation
Our Data Processing Agreement template and the full list of vendors that process customer data, with what each receives and where it is located.
We welcome reports from security researchers. This policy says what is in scope, how to report, what we promise and what we ask of you.
Scope. tenyq.com and the Tenyq app, tested only through a workspace you own or are authorised to use. Services run by our subprocessors are out of scope; report issues in them to their owners.
How to report. Email security@tenyq.com with a description of the issue, the steps to reproduce it and the impact you believe it has.
What we promise. We acknowledge your report within 3 business days, keep you informed while we investigate and fix it, and credit you once it is fixed if you would like us to.
What we ask. While you research:
- Access no more data than you need to show the issue, and keep none of it
- No denial of service, load testing or automated scanning of production
- No social engineering, phishing or physical attacks
- Give us reasonable time to fix the issue before you disclose it
Safe harbour. If you make a good-faith effort to follow this policy, we consider your research authorised, we will not bring legal action against you for it, and if anyone else does, we will make it known that you acted under this policy. This policy never authorises access to another customer's data.
security@tenyq.comReport a vulnerability