Trust
Security overview
How Timzen protects your business's bookings, customers and money, written for the person who has to sign off on a new tool.
Version 2026-10-24 · Effective October 24, 2026 · All legal documents
Timzen is a booking platform for local businesses, run by AD Supply NY Corp. This page says what is in place today, and just as plainly what is not yet. If your security team has a questionnaire, the questionnaire pack answers the usual questions in one printable page. Technical readers can also see the developer guide for how the API and webhooks are secured.
Where your data lives
- Timzen runs on Vercel (application) and Neon (Postgres database), both in the United States. Transactional email goes through Resend. Subscription payments to Timzen go through Square; a business's own card payments, where online payments are switched on for it, go through Stripe. Card numbers never touch Timzen. Encrypted backup copies are also kept in a private GitHub repository.
- Every connection is encrypted in transit (TLS 1.2 or newer, HSTS for two years). The database is encrypted at rest by the provider.
- Timzen is operated by AD Supply NY Corp, a New York company. The privacy policy lists every subprocessor.
Keeping each business's data separate
- Every table that holds a business's data has row-level security in the database itself. A query that forgot to filter by business would still only see that one business's rows: the database refuses the rest, independent of the application code.
- Application code never reaches a table directly. It must first take one of six narrow database roles inside a transaction, in exactly one place in the code, and each role sees only what it is for.
- Timzen's own staff cannot read a business's calendar, customers or notes from the platform console: that role has no rights on those tables at all.
- The public API acts as the business that made the key, inside the same row-level security; another business's record is simply not found.
Sign-in and access
- No passwords. Everyone signs in with a one-time code sent to their email (or Google sign-in). Codes are stored hashed, expire in 10 minutes, allow 5 attempts, and are rate-limited per address and per network.
- Two-factor authentication (authenticator app, RFC 6238) is available to every account and mandatory for Timzen's platform administrators. Secrets are encrypted at rest with AES-256-GCM; ten single-use backup codes are stored hashed.
- Roles inside a business: owner, manager, front desk, provider and read-only, each with a fixed set of permissions enforced on the server and again in the database. Providers see only the customers they have served or are booked with unless the owner turns that off.
- An owner can turn a team member's login off at once; this ends their sessions. Sessions use secure, HttpOnly cookies.
Application security
- Every page carries a per-request Content-Security-Policy nonce with no 'unsafe-inline', plus X-Content-Type-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Opener-Policy and frame-ancestors protections. A guard in the build fails if a page could be served without its nonce.
- All database access uses bound parameters; no SQL is ever built from request input. Ids from a browser are never trusted for authorization: the server re-resolves who may see what on every request.
- Webhook addresses are checked against private and internal networks before anything is sent (SSRF protection), and every webhook is signed (HMAC-SHA256) with a per-endpoint secret stored encrypted.
- API keys are stored as SHA-256 hashes and shown once. A key can be read-only, limited to parts of the API, and limited to a list of network addresses. Each key has its own rate limit.
- Secrets are generated with a cryptographic random source, live only in the hosting provider's encrypted environment, and are never printed or committed. The rotation order is documented.
- Automated tests run on every change: several thousand tests against a real Postgres, including cross-tenant isolation tests and guard tests that fail the build when a new table lacks row-level security or a new query skips the visibility rule.
Audit trail
- Every change a person or the system makes to a business's settings, services, team, schedule, customers, bookings, money and keys is written to an append-only audit log with who, when, before and after.
- Owners and managers see their business's log on the Activity log page (under Reports & history in the dashboard menu) and can download it as a CSV, with filters by person, dates and text. Downloading the log is itself logged.
- Timzen's platform actions on a business (for example a suspension) appear in that business's log as a plain fact, so owners always have the full picture.
Backups and continuity
- The database provider keeps point-in-time restore for its retention window. Timzen also takes its own encrypted (AES-256-GCM) nightly snapshot kept 14 daily and 8 weekly, with a weekly automatic restore drill into a throwaway database.
- Each backup run reports to the platform; an alert goes out when the last good backup is over 30 hours old or a drill fails. Silence is treated as the alarm.
- The nightly snapshots are kept on company hardware, and an encrypted copy of each is also kept off-site in a private GitHub repository. The key is held separately and is never stored there, so GitHub cannot read the copies. A weekly drill restores from the off-site copy too.
- Honest limit: this is not a second cloud region. Recovering from a snapshot means restoring it into a new database by hand.
Incident response and disclosure
- A written incident procedure covers containment (turning off an account or suspending a business immediately), evidence preservation, scope assessment from the audit trail, secret rotation in the safe order, and notification.
- Affected businesses and people are notified without unreasonable delay when personal information is, or plausibly is, involved, following the New York SHIELD Act and New Jersey requirements, with counsel.
- Security researchers can reach us through /.well-known/security.txt (RFC 9116). We acknowledge reports and do not pursue good-faith research.
Privacy and your rights
- A business owns its customer data. On every plan, Free included, owners and managers can download the customer list, appointments, locations and the activity log as CSV files. Report CSVs (the report tables, customer and team reports, takings and products sold) come with the Growth plan and up. To close the business and have its data deleted within 30 days, the owner can email info@adwebdesignny.com. Customers can download their own data and delete their own account from their profile.
- Timzen does not sell personal data and does not use a business's customer data for advertising. Marketing email to customers requires their consent, recorded with a timestamp.
- Data of a closed business is removed on the schedule in the privacy policy. Encrypted backups keep 14 daily and 8 weekly copies. The off-site copy follows the same rotation, but older copies stay in that repository's history until it is purged. Backups are used only to recover from a failure.
What Timzen does not have yet
- No SOC 2, ISO 27001 or PCI DSS attestation of its own (card data is handled by Stripe and Square, which hold PCI DSS Level 1). Timzen is a small company; a third-party audit is planned once the customer base justifies it.
- No independent penetration test has been commissioned yet; security review so far is internal and automated.
- No HIPAA business associate agreement: Timzen is not built for protected health information and should not be used to store medical records.
- Single-region hosting (United States); no EU data residency option.
Related documents
- Privacy Policy: what we collect, why, every subprocessor, and how to ask for your data.
- Business Terms & Subscription Agreement: the agreement between Timzen and a business.
- Security questionnaire pack: the usual vendor-review questions, answered.
- security.txt: how to report a vulnerability.