Trust
Security questionnaire pack
Plain answers to the questions a vendor-security review asks about Timzen. Print it, or paste the answers into your own form.
Version 2026-10-24 · Effective October 24, 2026 · Prepared by AD Supply NY Corp · Security overview
Company
- Legal entity and location
- AD Supply NY Corp, New York, United States. Timzen is the product name; the company's earlier name for it is noted on the Legal page.
- Security contact
- The support address published at /.well-known/security.txt.
- Certifications held
- None of Timzen's own yet (no SOC 2, ISO 27001). Payment processors Stripe and Square are PCI DSS Level 1.
- Cyber insurance
- Not held at this time.
Hosting and data
- Hosting providers and regions
- Vercel (application) and Neon (Postgres), United States. Subprocessors: Vercel, Neon, Resend (email), Square (Timzen subscriptions), Stripe (a business's own payments), GitHub (encrypted backup copies only; it holds no key).
- Encryption in transit
- TLS 1.2+ on every connection; HSTS with a two-year max-age and subdomains.
- Encryption at rest
- Provider-managed encryption for the database and file storage; AES-256-GCM for two-factor secrets, webhook signing secrets and the nightly backup files.
- Multi-tenancy model
- One shared database with row-level security on every tenant table, enforced by Postgres itself; narrow database roles per context; cross-tenant isolation tests, and a build guard that fails when a table lacks row-level security.
- Data residency options
- United States only.
- Card data
- Never touches Timzen. Stripe (business payments) and Square (Timzen subscriptions) handle card entry on their own hosted pages or card readers; Timzen stores only the processor's references, the last four digits and the brand.
Access control
- Authentication methods
- Passwordless one-time email codes or Google sign-in; optional TOTP two-factor for every account, mandatory for platform administrators.
- Password policy
- Not applicable: there are no passwords to leak, reuse or reset.
- Role-based access
- Owner, manager, front desk, provider, read-only; permissions enforced on the server and in database policies. Providers are limited to their own customers by default.
- Session management
- Secure, HttpOnly cookies; sessions end when a login is turned off; a two-factor check is tied to one browser session and re-verified every 12 hours.
- Vendor access to customer data
- Timzen staff cannot read a business's calendar, customers or notes from the platform console; the platform role holds no rights on those tables.
- API security
- Bearer keys stored as SHA-256 hashes, shown once; read-only or read-write; optional per-resource limits and IP allow-list; per-key and per-business rate limits; signed webhooks with SSRF checks.
Application security
- Secure development practices
- Code review, typed code (TypeScript, strict), automated tests against a real database on every change, guard tests for row-level security and visibility rules, dependency updates.
- Injection protection
- Parameterised queries only; no dynamic SQL from input; input validated with schemas on every write; user-written text goes through a moderation filter.
- Browser protections
- Per-request CSP nonce (no unsafe-inline), X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, frame-ancestors; a build-time guard for the CSP.
- Penetration testing
- No independent test commissioned yet; internal review and automated security tests only.
- Vulnerability disclosure
- security.txt per RFC 9116; good-faith research is welcome.
Operations
- Logging and audit
- An append-only audit log per business (who, when, before, after) for every change; owners download it as CSV; platform actions are visible to the business.
- Backups
- Provider point-in-time restore plus an encrypted nightly snapshot (14 daily, 8 weekly) with a weekly restore drill and alerting when a backup is late or a drill fails. Snapshots are stored on company hardware, with an encrypted off-site copy in a private GitHub repository (the key is held separately). Not a second cloud region.
- Recovery objectives
- Restore procedure documented and drilled weekly; no contractual RPO/RTO is offered at this time.
- Incident response
- Written procedure: contain, preserve evidence, assess scope from the audit trail, rotate secrets in the safe order, notify affected parties without unreasonable delay (NY SHIELD Act, NJ law) with counsel.
- Change management
- Every change goes through version control, the automated test suite, a production build and a release gate before deployment; migrations are additive.
Privacy
- Data ownership
- The business owns its customer data; Timzen processes it to provide the service. Timzen does not sell personal data or use it for advertising.
- Data export
- 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. Customers can download their own data.
- Data deletion
- To close the business and have its data deleted within 30 days, the owner can email info@adwebdesignny.com; customers can delete their own account. Removal follows the schedule in the privacy policy. Backups keep 14 daily and 8 weekly copies; older off-site copies stay in the backup repository's history until it is purged.
- Regulated data
- Not intended for protected health information; no HIPAA business associate agreement is offered.
These answers describe Timzen as built on the date above and are updated when the product changes. For a question not covered here, write to the security contact in security.txt.