Data Security

Platform data is hosted on Supabase in the AWS Zurich region (eu-central-2), Switzerland. Switzerland holds an EU adequacy decision.

Access is enforced by row-level security. Database data is encrypted in transit and at rest, and documents are held in access-controlled storage. Sipflow staff have no access to the production database.

For operators we hold company details, supplier agreements, uploaded documents, volumes, invoices and related financial data.

Nothing is shared with a supplier or any third party unless the operator has an active deal with that supplier on Sipflow. If there is a deal, the supplier sees the volumes recorded under that deal and, where the deal provides for it, pricing. Nothing else.

Sipflow does not sell, pass on or disclose contract or deal data. It stores it.

Evidence behind volumes (invoices, wholesaler reports, volume declarations) is never transmitted by Sipflow.

If a supplier asks for evidence, Sipflow gives the operator an export. The operator decides what to send and sends it themselves. That exchange is between operator and supplier, not Sipflow.

For suppliers and brands we hold deal terms, pricing and agreements.

Operators see only the terms of deals they are party to. A supplier can view volumes only for venues it has an active deal with. It cannot look up any other venue.

Sipflow works with metadata: whether a contract is uploaded, its status, its start and end dates, and which categories it covers.

Sipflow does not read, scan or analyse the contents of contracts or documents beyond what a feature you run requires.

Sipflow may analyse data in aggregate, for example how many venues hold contracts in a category, and does not disclose anything attributable to a named venue, supplier or agreement.

Sipflow does not use one party's data to give another party an advantage in a negotiation, and does not advise either side on the basis of confidential data. The venue decides who it works with.

Document scanning and analysis use the Google Gemini API under Google's paid terms, where customer data is not used to train Google's models.

Only the document being processed is sent. Account data is not.

Uploaded invoices and documents may contain third-party personal data, such as names and contact details. Sipflow processes them only to extract volumes and deal information, and does not use that personal data for any other purpose.

On cancellation we archive the account so you can return and continue where you left off. Archived accounts are deleted automatically after 24 months.

On request, deletion is completed within 30 days, and backups roll off after that period. You can request an export of your data.

You own the data you put on Sipflow. Sipflow holds a licence only to the extent needed to run the service.

If a security incident affects customer data, Sipflow notifies affected accounts without undue delay and within 72 hours of becoming aware, in line with the GDPR.

Free tools, the waiting list and the newsletter sit outside the secure platform. Here we hold your name, email and any free-tool inputs.

Free-tool inputs are stored and may be used in aggregated, anonymised form to improve Sipflow and publish industry insights. They are never published in a form linked to a named venue or person.

Newsletter and waiting-list sign-ups require an explicit tick-box.

Security and privacy questions:

support@sipflow.io