Security & Privacy
Trimsy stores customer information, bookings and payment metadata for thousands of Australian service businesses. Here's exactly how we keep it secure, who can access it, and what happens if you ever leave.
At a glance
All customer data stored in Australian data centres. Never leaves the country.
TLS 1.2+ in transit, AES-256 at rest. Bcrypt-hashed passwords with per-password salt.
Bring your own Stripe or Square. Card numbers flow direct from customer to processor — Trimsy gets a token.
Compliant with all 13 APPs. We act as data processor; you stay the data controller.
Per-staff permissions, MFA available for admins, immutable audit log of every sensitive action.
No lock-in. Cancel any time. Full CSV/JSON export on request. 90-day retention then permanent deletion.
Trimsy is hosted on enterprise cloud infrastructure with all customer data stored in Australian data centres. Your business data, customer records, bookings, and payment metadata never leave Australia. The platform is built on a multi-tenant architecture with strict row-level isolation — your data is logically and access-isolated from every other Trimsy business.
All data is encrypted in transit (TLS 1.2+) and at rest (AES-256). Database backups are encrypted with the same standard. Passwords are never stored in plain text — we use bcrypt with per-password salt. Session tokens are rotated regularly and bound to device fingerprints to mitigate session theft.
Trimsy is not a payment processor. You connect your own Stripe Connect account for online payments and/or your own Square Terminal account for in-person payments. Customer card numbers, full PANs, CVVs, and bank details flow directly from the customer to Stripe or Square — Trimsy only receives a tokenised reference. This means: we cannot leak card numbers because we don't have them. PCI DSS scope is reduced because we never store cardholder data.
Funds settle directly from Stripe or Square to your bank account on their standard payout schedules — Trimsy is never in the money flow. We can't withhold payouts, can't take a commission from your sales, and can't "lock" your funds if you cancel.
Trimsy operates under the Australian Privacy Act 1988 and the 13 Australian Privacy Principles (APPs). We collect only the data necessary to provide the service — customer contact details, booking history, staff records, and transaction metadata. We never sell customer data, never share it with marketing platforms, and never expose one business's customer list to another business on the platform.
Customers of your business can request access to or deletion of their personal data via your admin dashboard, in line with APP 12 (Access) and APP 13 (Correction). You retain full control over your data subject rights as the data controller; Trimsy acts as the data processor.
Automated SMS reminders and email confirmations are governed under the Australian Spam Act 2003. Trimsy enforces an explicit consent model: customers who book an appointment via your booking page consent to transactional messages about that booking (reminders, confirmations, changes). Marketing SMS campaigns require separate opt-in and include the legally required identification and unsubscribe options on every message. We never send unsolicited bulk SMS on your behalf.
Every business on Trimsy has a per-role permission system — Admin, Staff, Stylist, Kiosk, Reporting. Sensitive actions (deleting a customer, refunding a payment, changing payouts, granting Admin access) are logged in an immutable audit log retained for 12 months on the Growth plan. Failed login attempts are throttled. Multi-factor authentication for admin accounts is available.
Encrypted backups run on a daily incremental + weekly full schedule, retained for 30 days. The platform has automated health checks and failover for the application tier. Recovery time objective (RTO) is under 4 hours for a full restoration; recovery point objective (RPO) is under 24 hours. We test the restore process regularly — backups that haven't been verified aren't backups.
You own your data. Cancel any time — there are no lock-in contracts. On request we provide a complete export of your customer list, booking history, transaction ledger, staff records, and intake form responses as a CSV or JSON archive. After cancellation, we retain your data for 90 days in case you change your mind, then permanently delete it from production and roll it out of backups within the standard 30-day backup retention window.
Found a security issue? Please email [email protected] with details and a proof-of-concept. We acknowledge reports within one business day and aim to triage within five. We don't currently run a paid bug bounty but we acknowledge responsible disclosure publicly (with permission).
Email [email protected] or book a 20-minute security walkthrough with our team — happy to answer specific questions about your industry's compliance requirements.
Book a security walkthrough