How we protect your shop’s data
- Isolation
- Row-level security
- Payments
- Stripe, PayPal, Mercado Pago
- Trackers
- No third-party ones
- Certifications
- None yet
On this page (11)
Every shop isolated in the database
Each organization’s data is kept apart. On top of the app always filtering by organization, the PostgreSQL database enforces row-level security: every query runs with your organization’s ID and database policies reject any read or write of another organization’s rows. Queries run under a database role that cannot bypass those policies.
Automated tests try to read and write one organization’s data from another and must fail; they also check that every table holding organization data has its policies turned on.
Encrypted connections
In production, all traffic between your browser and Zeder Studio uses HTTPS (TLS). The database is not exposed to the internet; it is only reachable from the server’s private network.
Passwords and sign-in
- Sign-in runs on Better Auth, a mature open-source authentication library; we don’t write our own cryptography.
- Passwords are stored only as a hash (scrypt), at least 10 characters long. Nobody at Zeder Studio can see them.
- Email verification at sign-up and rate limiting against brute-force attempts.
- Optional two-factor authentication (2FA) with an authenticator app.
Roles and money visibility
The owner invites the team with roles: admin, member, viewer or shop floor. Each role has different permissions, and the owner decides who can see costs, prices and margins. Permissions are checked on the server for every action, not just hidden in the UI.
No card data
Payments are processed by Stripe, PayPal and Mercado Pago. Card details are entered on their pages and never reach our servers. Payment notifications are verified with a cryptographic signature before we act on them.
Attachments
Only allowed file types and sizes are accepted. Files are kept in private storage, separated by organization, and served through signed links that expire after 5 minutes.
Backups · planned for launch
At launch, the database will be backed up nightly, encrypted, to external storage in another region, with a monthly restore test. We will update this section once it is running.
Your data, under your control
- The owner can export all of the organization’s data at any time from Settings → Data, even after a subscription lapses.
- A failed payment gets a 7-day grace period; after that the account turns read-only and is never wiped suddenly. We keep data for at least 12 months.
- The owner can delete the organization and all its data whenever they want.
No trackers
No advertising cookies or third-party analytics. We measure product usage with our own events holding only IDs and counts, never names, dimensions or prices of your work. See the cookie policy.
What we don’t have yet
We are a small team and do not hold security certifications (such as SOC 2 or ISO 27001) or external audits. We’d rather say so plainly and explain what we actually do.
Responsible disclosure
If you find a vulnerability, email [correo para reportes de seguridad] with steps to reproduce it. We confirm receipt within [3] business days and keep you posted on the fix.
Please don’t access other people’s data or disrupt the service, and give us reasonable time to fix it before going public. We won’t take legal action against good-faith reports that follow these rules.
More in the privacy notice and the data processing terms.
Cut better starting with your next job
Create an account and use the full Workshop plan for 14 days. No card; afterwards you drop to the Free plan, not a lockout.