Frequently asked questions

Last updated: August 9, 2026 | Version 1.0

This is the plain-language version of the small print. It doesn't replace our Privacy Policy, Terms of Service or Data Processing Agreement, those stay the actual documents, but it answers the questions people actually have before they start using sqnc: why we ask for what we ask for, what happens if something breaks, what "beta" really means here, and how to reach us. One of our users asked for exactly this page, so here it is.

1. Why do we ask for the information we ask for?

Short version: most of it we ask for because the software genuinely cannot work without it, not because we're building a data pile.

• Email and a name — this is how you log in and how a callsheet knows who to reach. There is no version of an account that works without this.
• Role, day rate, availability, portfolio — all optional. You add these so productions can actually book you, and so your work shows up under your name. Skip them and your account still works, you just get less out of it.
• Phone number and address — only needed if a production wants to reach you off-platform or send something physical. Nobody is forced to fill this in.
• The content of callsheets and availability requests — stored because that's the actual product: a callsheet you can look back at, an availability answer that doesn't vanish.
• Anonymous visit statistics — so we know whether a page works, without knowing who looked at it. No cookies, no personal identifiers.

The full breakdown, including the legal basis for each purpose, is in our Privacy Policy under "What data do we collect" and "Why do we process your data."

2. How do we handle your data?

It depends on whose data it is.

If you work at a production company and put crew, contacts or callsheets into your workspace, that data belongs to your company. We only process it on your instructions, as a processor, not as the one deciding what happens with it. That relationship is written out in full in our Data Processing Agreement, live since today. It isn't a document you have to chase down and sign separately: it's an annex to our Terms of Service, in effect the moment you use the platform, with a signable version available on request for anyone whose own procurement process needs one.

For the platform-wide layer, your own account, your public maker profile, the credits that show up on it, sqnc is the one making the decisions, so there we're the controller ourselves. That side of things is covered by the Privacy Policy.

3. What's our privacy policy, in plain language?

The real document is at /privacy. The short version:

• We're a small Dutch business (sole proprietorship, KvK 95955925), not a platform conglomerate.
• We collect account data, the professional details you choose to add, anonymous usage stats, and whatever you send through the platform (callsheets, availability requests).
• We share data with a short list of named service providers who help run the platform (database, video hosting, email, error monitoring, and so on), never with advertisers, and we never sell it.
• You control who can see your profile: public, logged-in users only, or just people you've actually worked with through the platform. The default is the narrowest of the three.
• You can ask what we hold on you, correct it, export it, or delete your account entirely, at Settings → Account → Delete account.
• Everything is encrypted in transit, passwords are never stored in a form anyone (including us) can read, and access to data is enforced at the database level, not just in the app's interface.

If the plain version and the real document ever disagree, the real document wins, but if that happens, tell us at hello@sqnc.studio, because it means this page needs fixing.

4. What happens if something goes wrong?

We mean this specifically: what happens if there's a data breach, some bug or incident that exposes, loses or corrupts personal data. A couple of concrete examples of what would count: an access rule accidentally showing one company's crew list to another, or a leaked key that let someone reach data they shouldn't.

If anyone, a crew member, a client, one of us, suspects something like this happened, they don't need to be sure first. Freek reviews every reported suspicion personally. From there:

• If there's a real risk to people's rights, we report it to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) within 72 hours of finding out, as the law requires.
• If the risk is high specifically for you, we contact you directly, in plain language, without unreasonable delay, on top of that report.
• If the affected data belongs to a production company's workspace (their crew or contacts), we tell that company promptly, so they can meet their own reporting duty as the ones responsible for that data.
• Every incident gets logged internally, even the ones that turn out not to need an official report. Nothing gets quietly dropped just because it didn't cross the reporting threshold.

Think you've spotted something like this? Tell us at hello@sqnc.studio, even if you're not sure.

5. What rules do we follow, and how do we stick to them?

The GDPR (in Dutch, the AVG) applies to us the same way it applies to any company handling data of people in the EU, being small doesn't exempt us. Rather than a policy document nobody checks against, most of it is built directly into the software:

• Row-level security on every database table, access control enforced by the database itself, not something that can be bypassed by calling the right endpoint.
• Everything encrypted in transit, passwords never stored in readable form.
• Database changes go through a reviewed, versioned process, never a live hand-edit to production.
• Automated daily checks that catch things like a table missing an access rule, or data leaking across a workspace boundary, before they become an incident.
• For sqnc.site workspace customers specifically, a Data Processing Agreement spelling out exactly what we do and don't do with the crew and contact data you put in, including who our own subprocessors are, and a commitment to tell you before adding or swapping one.

Full detail lives in the Privacy Policy and the DPA, not repeated here.

6. What does "beta" actually mean?

Being honest about this one: sqnc is genuinely early. sqnc.site, the paid studio product, is invite-only while we roll it out, and free for now, that's a beta thing, not a permanent promise. Once beta ends, pricing applies as described in our Terms of Service. sqnc.space, the crew portfolio side, is free regardless of beta status.

What being in beta actually changes for you:

• Features move fast. Things get added, changed or reshuffled based on real feedback, sometimes within days.
• Rough edges happen. A bug is more likely here than in a mature product. There's a feedback button in the app for exactly this, and the team actually reads it.
• Availability isn't guaranteed. We aim for the platform to just work, but we can't promise zero downtime. Planned maintenance is announced ahead of time.

What doesn't change because of beta: your data protection. Privacy and security aren't dialed down while we're early, the standards in this document and in our Privacy Policy apply from day one. And if we ever discontinued the service, our Terms already commit us to giving you at least 90 days to export your data before that happens.

7. How do you report abuse or file a complaint?

Depends what you're reporting.

Something on a profile or a post. Every profile and feed post on sqnc.space has a "Report" control right on the page. Pick a reason, impersonation, a rights issue, explicit content, spam, or something else, add a note if you want, and send it. Nothing happens automatically: a person on our team reads and reviews every single report by hand.

Anything else. A complaint about the platform itself, about how your data has been handled, or something that isn't covered by a Report button yet, email hello@sqnc.studio. A real person reads it.

Specifically about your personal data. If you've raised it with us and you're still not satisfied, you can also complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens), the same route listed in our Privacy Policy.

8. Why does opt-in or opt-out work the way it does?

Almost everything on sqnc is opt-in: you make an account, you decide what goes into your profile. One thing works the other way around, and we'd rather explain the reasoning than leave it unexplained.

If a production company credits you, name, role, the production's title, that can appear publicly on sqnc even if you've never made an account yourself. That's opt-out, not opt-in. Here's why we think that's the right default, not just a convenient one:

• Film credits have always worked this way, aftiteling, IMDb-style registers. sqnc digitizes an existing norm, it doesn't invent a new kind of exposure.
• What's actually shown is narrow: name, role, production title. Never contact details, never a rate, never an address, those stay inside the production company's private workspace and never reach the public page.
• Anyone who worked on a production reasonably expects their name to be associated with it, that's inherent to the work. What they might not expect is that association becoming searchable and aggregated across multiple productions, which is exactly why the controls below aren't optional extras, they're the condition this default relies on.

The controls, concretely:

• Every unclaimed profile has a direct link on the page itself: "this isn't me" sends a takedown request, no account needed.
• Once you claim a profile, a second link appears: "this is my page, hide it," which removes it from public view immediately, no waiting on a review.
• You can opt out of public visibility entirely, at which point nothing about you shows up this way again.

9. Why does signing up work the way it does?

sqnc.site (the studio product) and sqnc.space (the crew side) both gate full access behind a manual approval step, and it's worth explaining why that isn't just friction for its own sake.

On sqnc.site, we're invite-only while we roll the product out carefully, requests are reviewed by hand, not because we distrust any individual signup, but because it's genuinely early and we want every studio that comes in to have a good first experience, not a half-finished one.

On sqnc.space, signing up creates your account right away, but full access needs one of two things: you've already been credited by a production company under an email or phone number you've verified, which unlocks everything automatically the moment that match is confirmed, or you're approved from a manually reviewed waitlist. Reviews are done by hand, usually within a day, and you get an email the moment you're approved.

The most common snag: you verified a different address than the one your producer used to credit you, say a personal address instead of the work email they had on file. The fix is adding and verifying that specific address from Settings, not waiting it out. Still stuck after a few days, or think you're signed in with the wrong account entirely? Email hello@sqnc.studio and we'll take a look.