Security Policy
Last updated: November 18, 2026
In short
- Passwords are stored with a strong hash (bcrypt) and sessions use signed tokens in protected cookies.
- If an incident affects your data, we will notify the authority and the people affected.
- Found a vulnerability? Write to contact@35mm.com before making it public.
1. How we protect your data
- Encryption in transit: all traffic goes over HTTPS.
- Passwords: our authentication provider (Supabase Auth) only stores a bcrypt hash with its own salt for each user; nobody at 35mm can see your password.
- Sessions: a signed access token that expires after one hour and a refresh token that is replaced every time it is used, stored in an httpOnly, SameSite cookie. The session expires after 30 days without activity, both in the browser and on the server, and is invalidated when you sign out or delete your account.
- Data minimization: we only ask for an email, a username and a password, no sensitive data, and your email is not shown to other people; contact messages are stored separately.
- Access control: moderation features are only available to admins, and access to the infrastructure is limited to the people who need it.
- Server-side validation: every operation checks who is asking and whether they are allowed; keys for external services never reach the browser.
- Providers: we work with infrastructure providers that hold recognized security certifications and keep database backups.
2. Incidents and breaches
If we detect a security breach affecting personal data: we will contain it and assess its scope; we will notify Chile's Personal Data Protection Agency by the fastest means possible and without undue delay (and, where the GDPR applies, the supervisory authority within 72 hours); and we will tell the affected users in plain language when the law requires it or there is a risk to them, explaining what happened and what they can do. We keep an internal record of incidents.
3. Reporting a vulnerability
If you find a vulnerability, write to contact@35mm.com with a description and the steps to reproduce it. We will answer as soon as possible and keep you posted.
We ask you to:
- not access, modify or delete other users' data beyond the minimum needed to show the problem;
- not run denial-of-service, spam or social engineering tests;
- give us reasonable time to fix it before disclosing it.
If you act in good faith and follow these rules, we won't take legal action against you. We also publish our security contact at /.well-known/security.txt.
4. What you can do
- Use a long password that you don't use on other sites.
- Sign out on shared devices.
- Don't post your own or other people's personal data in reviews or comments.
- If you think someone got into your account, write to us right away at contact@35mm.com: we will close all the open sessions of your account.

