CrewSheet.Pro Data Processing Agreement
Last updated: 27 October 2026
This Data Processing Agreement (DPA) applies automatically to every customer of CrewSheet.Pro and is part of the CrewSheet.Pro Terms of Service. It covers the personal data of crew, clients and contacts that you put into CrewSheet.Pro.
1. Parties and scope
- Controller: the customer who owns a CrewSheet.Pro workspace (“you”). You decide which personal data goes into the workspace and why.
- Processor: Rutger.VO, sole proprietorship of Rutger Van Oosterwijck, Talondreef 28, 2390 Malle, Belgium, company number 1008.467.230 (“we”). Contact: support@crewsheet.pro.
This DPA meets Article 28 of the GDPR. It applies as long as we process personal data for you, and it needs no signature: you accept it with the Terms of Service. If you need a signed copy, ask support@crewsheet.pro. Where this DPA and the Terms disagree on personal data, this DPA wins.
Data about you as an account holder (your login, billing, support) is not covered here: for that we are the controller, as set out in our Privacy Policy.
2. What we process and why
We process personal data only to run CrewSheet.Pro for you: storing your crew, clients and contacts, planning productions, building callsheets, sending them by email or share link, importing from your Rentman account when you connect it, and giving support. Annex 1 lists the data, the people concerned and how long we keep it.
We process for as long as your workspace exists. When it is deleted, the data in it is deleted too (see section 8).
3. Our obligations as processor
- Your instructions only. We process the data only on your documented instructions: the Terms, this DPA and what you do in the app (adding crew, sending a callsheet, connecting Rentman). If we think an instruction breaks data protection law, we tell you. If the law requires us to process data otherwise, we tell you first unless the law forbids it.
- Confidentiality. Only Rutger.VO and people working for us who need it for the service or a support request can access the data, and they are bound to confidentiality.
- Security. We take the measures in Annex 2 and keep them up to date.
- Sub-processors. We only use the sub-processors in Annex 3, under section 4.
- Help with rights requests. If someone asks us to see, correct or delete their data, we pass the request to you without delay. Most requests you can handle yourself in the app; where you can’t, we help.
- Help with your other duties. We help you, as far as reasonable, with security, breach notifications, data protection impact assessments and questions from a supervisory authority.
- No own use. We do not use your workspace data for our own purposes, do not sell it and do not use it for marketing or to train AI models.
- Deletion. At the end we delete the data as described in section 8.
4. Sub-processors
You give general permission for the sub-processors in Annex 3. Each is bound by a written agreement with data protection duties at least as strict as this DPA, and we remain responsible to you for their work.
- New or replaced sub-processor: we email the workspace owner at least 30 days before the change and update Annex 3.
- Objection: you can object by email within those 30 days, with a reason based on data protection. If we cannot solve it, you may end your subscription before the change applies and we refund the prepaid period you will not use.
Rentman is not our sub-processor: when you connect it, we read your own Rentman account on your instruction, with the API token you provide.
5. Transfers outside the EEA
The database is in the EU (Ireland). Some sub-processors in Annex 3 are based in, or use services in, the United States or the United Kingdom. We only allow such a transfer with a valid safeguard under Chapter V of the GDPR: an adequacy decision (such as for the United Kingdom, or for companies certified under the EU-US Data Privacy Framework) or the EU Standard Contractual Clauses.
6. Personal data breaches
If we become aware of a breach affecting your workspace data, we email the workspace owner without undue delay and at the latest within 48 hours. We tell you what happened, which data and people are likely affected, the likely consequences and what we are doing about it, and we add details as we learn them. You decide whether to notify the supervisory authority (within 72 hours) and the people concerned; we help you with that.
7. Your obligations as controller
- You have a lawful basis for the data you put in CrewSheet.Pro and inform the people concerned (your crew, clients and contacts) that you use CrewSheet.Pro.
- You only add the data you need. You do not add special categories of data (health, religion, ID or bank numbers) in free-text fields.
- You decide who receives callsheets and share links, and who you invite to your workspace.
- You keep your own Rentman agreement and API token in order.
8. Audits, liability, term and end
- Information and audits. We give you the information you need to check this DPA, on request. If that is not enough, you may have an independent auditor check once a year, with 30 days’ notice, at your own cost, under confidentiality and without access to other customers’ data.
- Liability. The liability rules of the Terms of Service apply, unless the GDPR or other mandatory law says otherwise.
- Term. This DPA runs as long as we process personal data for you.
- End. You can download your callsheet PDFs before you leave. When you delete your workspace or account, its data is deleted at once and permanently; backups are overwritten within 7 to 30 days. We keep nothing else, unless the law requires it.
- Changes. We may update this DPA to follow the law or the service. For important changes we email the workspace owner at least 30 days in advance.
- Law. Belgian law applies; the courts of Antwerp are competent.
Annex 1: Details of the processing
| Item | Details |
|---|---|
| People concerned | Your crew members (staff and freelancers), clients, venue and supplier contacts, and the members you invite to your workspace |
| Personal data | Name, email address, phone number, function, department, schedule and call times, notes you write; data imported from your Rentman account; delivery and open status of callsheet emails and how often a callsheet link was opened (no IP address or device) |
| Special categories | None intended (see section 7) |
| Processing | Storing, organising, showing, generating callsheet PDFs, emailing, sharing by link, importing from Rentman, deleting |
| Purpose | Planning productions and informing crew, as part of the CrewSheet.Pro service |
| Duration | As long as the workspace exists. Callsheet links stop working 7 days after the project’s last production day. Email delivery status is kept as long as the workspace exists. |
Annex 2: Security measures
- Data encrypted in transit (HTTPS/TLS) and at rest at our hosting providers
- Access rules in the database per workspace and per role (owner, member, read-only)
- Passwords hashed; two-factor sign-in available; one active session per account, with an optional notice for a new device
- Rentman API tokens stored encrypted, never shown again and never sent to the browser
- Unguessable callsheet links that expire 7 days after the project’s last production day
- Platform administrator access only for support, with every action recorded in an audit log
- Automated daily backups with a short retention (7 to 30 days)
- Hard deletes when you delete data, a workspace or an account
- Fonts and code served from our own domain; no advertising or tracking tools in the app
Annex 3: Approved sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication, file storage | EU (Ireland) |
| Lovable Labs Incorporated | Application hosting (Google Cloud, Netherlands; Cloudflare, global), sign-in emails, logs | United States, with EU hosting; Standard Contractual Clauses (sub-processors) |
| Brevo (Sendinblue SAS) | Sending callsheet emails and notifications, delivery and open status | France (EU) |
| OpenStreetMap Foundation | Looking up coordinates for a location address; map tiles | United Kingdom (adequacy decision) |
| Esri | Satellite map tiles when placing a location pin (IP address only) | United States; safeguard under section 5 |
Stripe and Accountable process billing data about you as our customer, not your workspace data, so they are listed in our Privacy Policy, not here.