Privacy Policy

Data we hold, and why

An account is a Firebase Authentication record (your email and password, checked by Firebase, never seen or stored by us) plus one profile document in our Firestore database, keyed to your account: your email, your plan, the minutes you have used and bought this period, and the two dates the account was created and last changed. We hold this because the service cannot meter your plan or sign you in without it.

Each course or video request you make is stored as one job document under your own account: what you asked for, the track and level you chose, its length in minutes, and its status. You can attach up to 5 files to a request, and your own one-line note about each file is stored on the request beside the file name.

A PDF or a text file you attach is never uploaded. Its text is read out of the file in your browser, capped at 20,000 characters, and that text is written onto the request - where our build worker reads it, and where a model reads it to decide the chapter list for your course. If you do not want the contents of a document to travel, name the document instead of attaching it: the source-document box on the first step of the composer takes the file name only and never reads the file.

An image you attach is handled the other way round. It is resized in your browser if it is wider than 1920 pixels, re-encoded, and uploaded to Firebase Storage under a path belonging to your account. The storage rules make that path create-only: no signed-in account can read, replace or delete an object there, including the account that uploaded it, and only our build worker, which holds an administrative credential, ever reads one. So an attached image cannot be fetched back or removed through the app, by you or by us.

A video ZUQ generates for you is stored as a file in Firebase Storage, under a path that belongs only to your account. In this early build, a finished build hands you a fixed sample video rather than a video generated from your own request; the storage path and the access rule are the same either way.

Who can see it

The security rules behind the database and the storage bucket allow only your own signed-in account to read your profile, your requests, and your videos. Nobody else's account can read them through the app.

Cookies and local storage

ZUQ does not use advertising or tracking cookies. Firebase Authentication keeps you signed in using its own local storage in your browser, and the site may keep small local values for things like a course you started planning before you signed in, so you do not lose it. None of this is sold or shared with an advertiser.

Data deletion and export requests

There is no self-serve delete-account button in this build yet. To ask for your account and its data to be deleted, or for a copy of what we hold about you, email support@zuq.si from the address on the account. We will act on a deletion or export request without unreasonable delay.

Not legal advice

We are not your lawyer and this is not legal advice. This is so that when you do talk to your lawyer, you already know which three pages to talk about.

Changes to this policy

We may update this policy as the product changes. The version date at the top of this page is how you tell one version from another.

Contact

Questions about this policy, or a deletion or export request, can be sent to support@zuq.si. Questions for the company itself can be sent to 9owls, Inc. at hello@9owls.com.