This policy explains what personal data we collect when you visit this website or use Quenzo, why we collect it, who we share it with and what rights you have. We follow the EU General Data Protection Regulation (GDPR).
1. Who is responsible
The controller of your personal data is Gigo Interactive OÜ, registered in the Estonian Business Register with registry code 17411998, Tallinn, Estonia. Email legal@gigointeractive.com for anything about your data.
If you work in someone else's organisation in Quenzo, that organisation's owner also decides about the work made there. Section 6 explains who decides what.
2. The short version
- We collect as little as we can, and we use what you upload and write only to make and edit your videos for you.
- We store your account, files and videos in the European Union.
- We do not sell your data, and we do not use your videos to train AI models.
- Raw clips you upload are removed automatically, on a schedule set by the organisation's plan (section 9).
- We use PostHog, in its EU cloud, to count how people use this website and the app. It stores something on your device only if you agree in our cookie banner, and it records no sessions.
- We run no advertising scripts, and we do not share your data with advertising networks.
- If you work in someone else's organisation, its owner decides what happens to the work made there, and its owner and admins can see who did what.
- You can see, download, correct or delete your data at any time. If other people are in an organisation you own, you first hand it over or remove them, and then you can delete your account (section 6).
3. News sign-up (this website)
If you leave your email on this website for news about Quenzo, we store:
- your email address;
- that you ticked the consent box, the exact words you agreed to and when;
- the page you signed up on, and campaign tags in the link you followed (such as
utm_source), if there were any; - if you typed an idea into the "What do you want to make?" box before signing up, that text and the kind of video you picked, so we can send it back to you at launch;
- if you signed up with a "Tell me when it lands" button on a feature we had not released yet (our website showed these buttons until early November 2026), which feature or features you asked about. The website no longer has these buttons, so new sign-ups leave this empty.
We do not store your IP address or browser details with your sign-up.
Why and on what basis: to email you news about Quenzo, such as early access and new features, with your idea if you left one, to email you when a feature you asked about is ready, and to send occasional product news, based on your consent (GDPR Article 6(1)(a)).
How long: until you unsubscribe or ask us to delete it.
Withdrawing consent: use the unsubscribe link in any email, or write to legal@gigointeractive.com. Withdrawing does not affect emails already sent.
4. Visiting this website
When you visit, our hosting provider Cloudflare processes your IP address and basic request details (such as the page and browser type) to deliver the page and protect the site from attacks. This is in our legitimate interest in running a secure website (Article 6(1)(f)). We do not use this data to identify you or to track you across sites.
Our own visit counts. Our website also adds up its visits and clicks per day: the page, the day, the country, the kind of site you came from and the campaign tags in the link you followed. We store no IP address, no visitor code and no cookie with these counts, so they cannot identify you. This is in our legitimate interest in knowing how people find us (Article 6(1)(f)).
Analytics with PostHog. We also count how people use this website with PostHog, as "Product analytics" in section 5 explains.
5. Using the app
When you use Quenzo, we process:
| What | Examples | Why | Legal basis |
|---|---|---|---|
| Account data | Email address, name, how you sign in (an email link, a password or Google), the country you are in | To create and secure your account and charge the right tax | Contract (6(1)(b)), legal obligation (6(1)(c)) |
| Organisations and people | The organisations and workspaces you belong to, your role in each, invites you sent or received, spending limits set for you, and who made each file | To let people work together, decide who may do what, and show an organisation's owner and admins who did what | Contract (6(1)(b)), legitimate interest (6(1)(f)) |
| Your videos and files | The clips you upload, the sound in them, the words you say (as a transcript with timings), music you upload, the line, brief or script you write for a video, voiceover scripts, your edits, previews, finished videos, covers, brand colours and saved styles | To make and edit your videos, show you previews, store them and deliver the finished files | Contract (6(1)(b)) |
| Series and Memory | The series you set up (what each is about, its look and how often it posts), and what you add to a workspace's Memory: text you paste, a channel description, and the topics and short quotes we draw from them | To suggest ideas and make the videos of your series | Contract (6(1)(b)) |
| Posts and their numbers | The social accounts connected in a workspace (name, handle and picture), each post with its caption, time and link, and its numbers, such as views, likes and how long people watched | To publish your videos when you ask, and show you how each post did | Contract (6(1)(b)) |
| Credits and purchases | Plan, credit balance, what each edit cost, who spent the credits and in which workspace, receipts from our payment partner, and the company name and tax number if the organisation buys as a business | To run the organisation's account and keep the records the law requires | Contract (6(1)(b)), legal obligation (6(1)(c)) |
| Activity log | Who changed what in an organisation and when, such as an invite sent, a role changed or a workspace made | So an organisation's owner and admins can see who changed what, and to keep Quenzo safe | Legitimate interest (6(1)(f)) |
| Consent for faces and voices | Your confirmation, given once when you accept our terms, that any face or voice you use in a video is your own, or that you have that person's permission: who accepted, when, and which version of the terms | To show that permission was given, if anyone asks | Legitimate interest (6(1)(f)) |
| Safety data | The result of the automatic checks on each upload and on the words of each video you ask us to make, with the words that matched our rules; the text itself when our word list flagged it and our AI check allowed it (section 11); reviews by our team, reports, warnings and bans, and copies of content kept as evidence | To keep Quenzo safe and follow our rules | Legitimate interest (6(1)(f)), legal obligation (6(1)(c)) |
| Error reports | What broke and when, with a code that stands in for your account | To find and fix problems | Legitimate interest (6(1)(f)) |
| Support messages | What you write to us and our replies | To help you | Contract (6(1)(b)), legitimate interest (6(1)(f)) |
| Product analytics | The pages you view on this website and in the app, and the steps you take in the app, such as starting or finishing a video. If you decline in our cookie banner, this is counted without cookies and without any code for you. If you agree, a cookie and a random code for your browser are used, never your name or email | To see what is hard to use and improve Quenzo | Legitimate interest (6(1)(f)) for counting without cookies. Consent (6(1)(a)) for analytics with a cookie |
How a drawn video is made. When you ask for a drawn video, an AI model writes a script from your line, or we use the script you wrote. The words are checked against our rules (section 11), and an AI model plans the scenes from our own library of drawings. One of our free AI voices reads the script on our own servers, so the script goes to no voice company. If you choose a premium voice, the script's text is sent to Inworld, which reads it aloud for that video and nothing else. A drawn video does not use your face or voice.
How an edit of your own clip works. To edit a clip, AI models listen to its sound to write down your words, look at frames of it to check it is allowed and to plan the cut, and choose where captions, zooms, effects and sound go. If you add a voiceover, the words of the script are sent to an AI model that reads them aloud in one of our AI voices. Your face and voice are used only to edit that video for you.
People in your uploads. If other people can be seen or heard in what you upload, you upload it for your own videos, and you confirm that they agreed, as our terms say. We use their images and voices only to edit your video, in the same way as yours.
Voices made from a recording. We do not make a voice from a recording of a person today. If we offer it later, a voice provider will make the voice, and we will name that provider in section 7 before the feature starts.
Videos you share. If you share a video by link, anyone with the link can watch it until it is turned off or the video is deleted. A link you shared in a workspace stays live after you leave that organisation or delete your account, until someone who works there turns it off or deletes the video. Deleting a workspace ends every link shared from it.
Styles you save are kept in the workspace you saved them in. People who work in that workspace can see and use them.
Posting to your social accounts. If someone in your workspace connects Instagram, TikTok, Facebook or YouTube and schedules a post, we send the video to Upload-Post, run by TONVI TECH S.L. in Spain, which publishes it at the time chosen. You sign in on the platform's own screen, so neither we nor Upload-Post see your password. Upload-Post keeps the access the platform gives. We send it the video file, the caption, the platform options and a code for the workspace, never a name or an email address. We keep the connected account's name, handle and picture, and a link to each post. We do this to publish at your request (contract, Article 6(1)(b)). Once a platform receives your post, it uses it under its own terms and privacy policy.
How your posts are doing. After a post goes out, we read its numbers from Upload-Post for 30 days, such as views, likes, shares, reach and how long people watched, and keep them in the workspace so you can see how each post did. These are totals for the post, never details about the people who watched it.
Memory. The owner and admins of a workspace can add sources to its Memory, such as text they paste or a channel description. An AI model reads each source once and keeps topics from it, each with a short quote copied from the source. Memory stays in its workspace: people who work there can see it, it never reaches another workspace, and we do not use it to train AI models. Text you add is kept with its source until you remove it. When you remove a source, it is hidden at once, with its title and the quotes taken from it, and you can undo that for a short time. Then we delete its text, its title and its quotes. What Memory learned from it (a topic's title, summary and facts) stays only if another of your sources, or a video you made, also rests on it; otherwise we delete that too. We keep a small record of the removal for 30 days for billing: when the source was read, what reading it cost, and who removed it and when. Then we delete that record.
Product analytics. We use PostHog to see how people use this website and the app, so we can find what is hard to use and fix it. PostHog, Inc. runs it for us in its EU cloud, and the data is held in the European Union.
- Before you answer, and if you decline. Before you answer our cookie banner, no analytics is sent. If you decline, PostHog runs in a mode without cookies. Nothing is stored on your device: no cookies and no local storage. No sessions are recorded. PostHog counts the pages you view and, in the app, the steps you take, such as starting or finishing a video. On this website and in the app it also counts clicks on buttons and links (never their text), form submits, rage clicks (several quick clicks in one place) and how far down a page you scroll. To tell one visit from another, PostHog's servers make a code from your IP address, your browser details and a secret that changes every day. PostHog may work out an approximate location (country, region, city) from your IP address; the address itself is not kept. We do this in our legitimate interest in understanding and improving Quenzo (Article 6(1)(f)).
- If you accept. PostHog uses a cookie and local storage on our own domain to recognise your browser on later visits. This is based on your consent (Article 6(1)(a)), and you can change your choice at any time. If you decline, PostHog keeps counting without cookies, as described above.
- What PostHog never gets. We never send PostHog your name, your email address, your files or the words in your videos. We do not use analytics for advertising, and we do not share it with advertising networks.
- How to say no. You can object at any time: write to legal@gigointeractive.com and we stop analytics for your account and delete what PostHog holds under your account's code. You can also decline in our cookie banner, or withdraw a yes at any time with "Cookie settings" at the bottom of every page of this website, or in the app under Settings, Your data. Blocking scripts in your browser stops PostHog too, and Quenzo works the same without it. If your browser sends Do Not Track or Global Privacy Control, this website and the app send no analytics to PostHog.
6. Organisations, workspaces and the people in them
What they are. When you sign up, you get your own organisation with one workspace, and you are its owner. An organisation holds the plan, the bill, the credits and the people. A workspace holds the videos, files and styles for one channel or brand. An organisation can have several workspaces, and you can belong to several organisations.
Who decides. The owner of an organisation decides who works in it and what happens to its workspaces and to everything made in them. We run Quenzo for the organisation and follow those choices. If you want work made in someone else's organisation changed or deleted, ask its owner. For your own account, write to us.
Who sees what.
- Everyone in a workspace can see everything in that workspace, including who made each video or file.
- An organisation's owner and admins can see every workspace in it, the people and their roles, the open invites, the seats, how many credits the organisation has, what was spent by workspace and by person, and the activity log.
- A workspace's admins can invite people to that workspace and see who works in it.
- Only the owner sees the bill: what was bought, and the company details.
- Everyone else who may spend credits sees only how much they can spend, not the organisation's total.
When someone invites you. We store your email address, the role and the workspaces the invite offers, who sent it, and when it was sent, accepted or ended. We send you one email with a secret link, and only an account signed in with that same address can accept. If you never accept, we remove your address from the invite 12 months after it was last sent. If you have an account and delete it, we remove your address from every invite at once. We do this so the person who invited you can add you, and so the organisation's owner and admins can see who was invited (legitimate interest, Article 6(1)(f)).
The activity log. Each organisation has an activity log that only its owner and admins can read. It records changes such as an invite sent, accepted or ended, a role changed, a person removed or leaving, a workspace made, renamed, archived or deleted, a spending limit changed, a plan changed, and the company details changing. Each line stores who did it as an account code, never a name. The name is read from the account when the page is shown, so a person who deleted their account shows as "a deleted user". There is one exception: a line about an invite that was never accepted shows the invited email address, read from the invite. It disappears when we remove the address from the invite, 12 months after the invite was last sent. A line about a workspace keeps that workspace's name until the workspace is deleted. The page shows the last 12 months.
Company details. If the organisation buys as a business, our payment partner's checkout asks for the company name and a tax number, such as a VAT number. We keep a copy of them, read back from Stripe, and show it to the owner on the billing page. To change them, write to legal@gigointeractive.com.
When you leave, or are removed. You can leave an organisation you do not own, and its owner or an admin can remove you. You lose access at once. What you made there stays with that organisation, and so do links you shared there. Your AI connections and phone links there end, your spending limit there is removed, and the invites you sent that are still open end. The activity log records that you left or were removed. You keep your own account. If you own no organisation, we give you a new one of your own, without welcome credits.
When an organisation is handed over. The owner can hand the organisation to a person already in it. Nothing changes until that person accepts. Then they become the owner and decide from then on, and the old owner becomes an admin. The plan, the bill, the credits, the workspaces and everything in them stay with the organisation.
When you delete your account.
- While anyone else is in an organisation you own, or has an open invite to it, we cannot delete your account. Hand the organisation over or remove them first.
- Otherwise, we sign you out everywhere, take you out of every other organisation at once, and delete the organisations you own, with their workspaces and everything in them. A paid plan of an organisation you own ends at once.
- What you made in someone else's organisation stays with that organisation, and so do links you shared there.
- We also delete the analytics and error reports PostHog holds under your account's code.
- We start removing your data within the hour. Section 9 says when it is gone, and what we keep.
When a workspace is deleted. Only the organisation's owner can delete a workspace. Its share links, AI connections and phone links end at once, and so do invites to it. The owner can restore it until we remove it, normally within 24 hours. Then everything in it is deleted.
Downloading your data. "Download my data" gives you your account and the workspaces of the organisations you own. Work made in someone else's organisation belongs to that organisation, so it is not in your download. Ask its owner for it.
7. Who receives your data
We share personal data only with the service providers who help us run Quenzo, only for that purpose and under data processing agreements:
| Provider | What they do for us | What they receive |
|---|---|---|
| Cloudflare | Hosting, storage, databases, video processing, email sending, bot protection on sign-in, and the gateway our AI requests pass through | All data we store and send |
| Google (Gemini models) | Writing down the words in your clip, understanding reel clips, planning effects, and reading voiceover scripts aloud in an AI voice | The sound of your clip, reel clips, the text of your words, and the text of voiceover scripts |
| Anthropic (Claude models) | Checking the words of each video you ask us to make (your line, brief or script) against our rules before we make it, checking uploads against our rules, planning reel cuts, writing scripts and planning scenes for drawn videos, and reading the sources you add to Memory | Frames from your clips, the text of your words and plans, the line, brief and script of a drawn video, and the text of Memory sources |
| Inworld | Reading a drawn video's script aloud, only when you choose one of our premium voices for it | The text of that script, never your name or email |
| Google (sign-in) | Signing you in, only if you choose to sign in with Google | Your Google account email and name |
| Link (Sold through Link, LLC) and Stripe | Payments. Link is the merchant of record and decides how it uses payment data as its own controller | Your email, country, payment details and purchase details. We never see your full card number. Stripe sends us back the company name and tax number if the organisation buys as a business |
| Upload-Post (TONVI TECH S.L., Spain) | Publishing your videos to the social accounts you connect, when you schedule a post | The video file, the caption, the platform options and a code for each workspace, never a name or an email address. You sign in on the platform's own screen, and Upload-Post keeps the access the platform gives. It sends us back the connected account's name, handle and picture, and each post's numbers |
| PostHog, Inc. (EU cloud, data held in the EU) | Error reports and product analytics on this website and in the app | Usage events with a cookie and a random code for the browser for people who agree, otherwise counted without cookies and without any code; error reports carry a code that stands in for your account. Never your name, your email or your files. Your IP address and browser details, used to make the daily visit code and an approximate location (country, region, city), and not kept |
Our AI providers process your content only to make your video for you, under business terms that do not allow them to train their models on it. We check each provider's terms before we add or change one. AI requests pass through Cloudflare's gateway. Cloudflare keeps a record of each AI request (which model, its size, cost and whether it worked), never the words sent or returned. Section 9 says how long. When an AI voice reads a voiceover, we also ask Google not to keep the request.
Inside Quenzo, the people in your organisation see what section 6 describes. We do not show your data to other organisations.
We may also share data when the law requires it, or to protect our rights and the safety of others.
8. Where your data is, and transfers outside the EEA
Your account, files and videos are stored in the European Union. Some providers above process data outside the European Economic Area, for example in the United States. Where that country has no EU adequacy decision, we rely on the European Commission's standard contractual clauses or, for US providers that are certified, the EU-US Data Privacy Framework. Upload-Post keeps data in the European Union and uses standard contractual clauses where data leaves it. PostHog keeps our analytics data in the European Union. PostHog, Inc. is based in the United States, so where its team or its own providers reach that data from outside the EEA, the same safeguards apply. You can ask us for a copy of the safeguards.
9. How long we keep it
| What | How long |
|---|---|
| Raw clips you upload | Removed automatically, depending on the organisation's plan (Free 2 days, Creator 7, Studio 30, Agency 90), counted from when your edit is ready or from your last export of it, whichever is later. We email the owners and admins of the organisation and of the workspace before: 3 days before when the plan keeps clips that long, and again the day before |
| Finished videos | While the organisation's paid plan is active. On the free plan, 30 days after your last export |
| Projects of an account that has never paid | Deleted after 14 days without activity, with an email 3 days before. The Default project stays |
| Previews and working files | Previews, up to 14 days. The working files of a video that failed or was refused, and uploads that never finished, 7 days. The script, scene plan and voice of a finished drawn video stay with the video |
| After a plan is cancelled, or a payment fails | The organisation's workspaces become read-only for 30 days so everyone can download their work, then every project except the Default project is deleted. When a plan ends while the organisation still has pack credits, this waits until they are used up or expire |
| Deleted projects | Removed in our daily clean-up, normally within 24 hours |
| Deleted workspaces | Removed in our daily clean-up, normally within 24 hours. Until then the owner can restore one |
| Deleted accounts | We start removing them within the hour. Section 6 says what goes, and "Records about a deleted account" below says what stays |
| Backups | Our database keeps its own restore history for 30 days. Full copies of the database that we make by hand before a change are kept until we delete them |
| Invites never accepted | The email address is removed 12 months after the invite was last sent |
| Activity log | The page shows the last 12 months. Older lines are kept. Lines hold account codes, not names, so once a person's account is deleted their lines no longer name them |
| Series | Kept until the workspace is deleted, also after you delete the series |
| Sources you add to Memory | Kept until you remove the source. Once the time to undo has passed (an hour, and never more than a day), we delete its text, its title and its quotes, and the topics that nothing else of yours rests on. A small record of the removal is kept for 30 days for billing, then deleted |
| Post numbers | Kept until the workspace is deleted |
| Files in a workspace under a safety case | While someone who works in a workspace is under review or banned, we keep that workspace's files and pause deletions there until our team closes the case |
| Copies kept as evidence | While a safety case needs them, then deleted |
| Text our word list flagged and our AI check allowed (section 11) | 12 months, or until the project, the workspace or the person's account is deleted, if that comes first. Kept longer while a safety case is open in that workspace |
| Results of our safety checks | No end date yet, also after the account is deleted. They hold the result, its codes and the words that matched, never the whole text |
| Records about a deleted account | Purchase, credit and usage records, the records of our safety checks, reports and actions, and the activity log stay after you delete your account, linked to a code instead of your name. We also keep a scrambled form of your email address, so welcome credits are given only once per person |
| Sign-ups never confirmed | Deleted within 7 days |
| Records of what a connected AI assistant did | 12 months. The tasks it started, 90 days |
| News sign-up (section 3) | Until you unsubscribe or ask us to delete it |
| Request logs | Up to 7 days |
| Logs of AI requests | Deleted automatically by Cloudflare's gateway, oldest first. We have not set a fixed number of days yet |
| Error reports | Up to 12 months |
| Product analytics | Up to 12 months |
| Purchase records, with the company name and tax number | At least as long as tax and accounting law requires: in Estonia, seven years. We do not delete them automatically yet |
You can download your data or delete a video, a project or your whole account at any time, as your role allows. Section 6 explains what happens when other people are in an organisation you own.
10. Your rights
You have the right to:
- access your data and get a copy;
- correct data that is wrong;
- delete your data;
- restrict how we use it;
- move your data to another service (portability);
- object to processing based on our legitimate interest;
- withdraw consent at any time, without affecting what happened before.
To stop analytics, see "Product analytics" in section 5. For anything else, write to legal@gigointeractive.com. We answer within one month. If your request is about work made in someone else's organisation, we may ask that organisation's owner first, because they decide about it. You also have the right to complain to a data protection authority: our lead authority is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee), or you can go to the authority where you live or work.
11. Automated decisions and safety cases
Every upload, and the words of every video you ask us to make, is checked automatically before we use it. If the check finds something our rules do not allow, it cannot be used and nothing is charged. If the check is unsure about an upload, a person on our team looks at it.
Our word list. Our word list looks for sexual words and words about children. In the words of a video, the list alone does not refuse it: our AI check decides. Words we would show on screen, such as titles, are refused when the list flags them. When the list flags words that our AI check allows, we keep that text, who wrote it and in which workspace for 12 months, and our team reviews it to find accounts that misuse Quenzo. A review can lead to a warning or a hold on the account.
You can always ask a person to review a refusal, with the "Ask for a review" button or by writing to legal@gigointeractive.com. We make no other decisions about you by automated means that have legal or similarly significant effects.
Inside an organisation. A warning or a ban goes to the person who made the content, not to everyone in the organisation. If we remove content from an organisation, its owner gets our notice about it. If someone who works in an organisation is acted against for content made elsewhere, its owner gets a short notice without the reason. A ban freezes the workspaces of the organisations the banned person owns, and ends the share links and phone links they made. While someone who works in a workspace is under review or banned, we keep that workspace's files as section 9 says. We keep copies of the content concerned as evidence while a case needs them, then delete them.
12. Children
Quenzo is for people aged 13 and over. We do not knowingly collect data from children under 13.
13. Security
We encrypt data in transit and at rest, limit who can access it, and keep provider keys out of our code. No system is perfectly secure. If a breach puts your rights at risk, we tell you and the authorities as the law requires.
14. Changes
If we change this policy in a way that matters, we tell you by email or in the app before the change applies.