1. One business cannot see another
This is the one that matters, so it is first. Every record in Fretso — every pet, invoice, booking and clinical note — carries the business it belongs to, and the database itself filters every single query by it, using row-level security tied to your team's memberships.
That is deliberately not a rule the application remembers to apply. It is enforced underneath the application, so a mistake in our code cannot return another business's data: the database will not produce it. We keep an automated check that fails our build if any table carrying a business id is missing that protection.
2. Roles, enforced twice
Owner, admin, manager, staff and read-only each see different things. What the screen shows you is decided in the app; what you are actually allowed to do is decided independently by the database.
Both layers exist on purpose, and the second is the one that counts. Hiding a button is not access control — a read-only account cannot write even if something in the interface suggested otherwise.
3. Payments
Card details never reach our servers. Payment happens on the provider's own checkout — Razorpay for businesses in India, PayPal elsewhere — and we store only a reference to the subscription, never a card number.
A subscription is only ever activated by a cryptographically signed message from the payment provider. We do not take the browser's word that a payment succeeded, because a browser can be told to say anything.
4. Photos and files
Pet photos and grooming before-and-afters are private. They live in storage that is readable only by members of the business they belong to, and are not guessable or shareable by URL.
Your business logo is the one deliberate exception: it has to be publicly readable so it can render inside an invoice email your customer opens next week.
5. Where your data lives
Fretso runs on managed infrastructure with encryption in transit and at rest, daily backups, and point-in-time recovery. Traffic is served over HTTPS only.
We are based in India. If you need a specific data residency arrangement for regulatory reasons, ask us before subscribing rather than after.
6. Who else touches it
We use a small number of specialist providers, each for one job:
- Supabase — the database, authentication and file storage.
- Cloudflare — hosting and delivery of the website and the app.
- Resend — sending the emails you and your customers receive.
- Razorpay and PayPal — taking subscription payments.
We do not sell your data, and we do not use your customers' records to train anything. See the Privacy Policy for the full position.
7. Deletion
Nothing is deleted silently. Archiving a pet keeps its history; an issued invoice can be voided or credited but never quietly edited, so the trail stays intact.
Closing a business makes it unreachable immediately, keeps it for thirty days in case you change your mind, and then permanently deletes it. After that we cannot recover it, because it no longer exists — so export what you are required to keep first. See theRefund and Cancellation Policy.
8. Reporting a problem
If you believe you have found a security issue, email[email protected] with enough detail to reproduce it. We will confirm receipt, keep you updated, and we will not take legal action against anyone who reports a genuine issue in good faith and gives us a reasonable chance to fix it before publishing.