Security
Your files deserve thoughtful protection.
This page explains the architecture as it is built. It does not list certifications Orindle does not hold — that would be a claim, not a security practice.
Encrypted in transit
Every request to Orindle travels over TLS. Uploads go straight from your browser to object storage over an authenticated, time-limited session rather than through a shared application server.
Encrypted at rest
Files live in Cloudflare R2 object storage, which encrypts data at rest. Objects are stored under random keys, so a filename alone never reveals a location.
Short-lived signed access
Downloads are issued as signed URLs that expire. Nobody can construct a permanent public address for a private file by guessing it, and revoking sharing stops new links immediately.
Authorisation on every request
Access checks run on the server for every read and write, using database row-level security so one account can never query another account's rows — even if a client is tampered with.
Scoped secrets
Service credentials live only in server-side environment variables. Nothing privileged is shipped to the browser, and no key is committed to the repository.
Least-privilege billing
Payment processing is handled by Razorpay. Card data never touches Orindle's servers, and webhooks are signature-verified before they can change a subscription.
What happens when you open a file
Four steps, each with a narrowly scoped credential. The application server never holds your file content.
- 01
You sign in
Supabase Auth verifies your identity and returns a short-lived session token.
- 02
Orindle authorises
The server checks your session and your row-level permissions for the folder you asked for.
- 03
Storage issues a signed URL
Cloudflare R2 hands back a one-time, expiring upload or download URL scoped to a single object.
- 04
Bytes move directly
Your file travels between your browser and R2. It is never buffered on the application server.
What Orindle does not claim
- No SOC 2, ISO 27001 or HIPAA certification is held today.
- No third-party penetration test has been published yet.
- No end-to-end zero-knowledge encryption — the service can decrypt data to serve it to you.
- No enterprise SSO or SCIM provisioning — those are on the roadmap, not shipped.
If a certification becomes relevant to your organisation, write to support and we will tell you precisely where things stand rather than sending a badge we have not earned.
Privacy and security questions.
Still unsure? Ask us directly.
Your next home for files starts here.
Get started with 10 GB of free cloud storage.

