Who we are
Fil (fil.design) is operated by Design+Code (“we”, “us”). This policy covers Fil’s website, studio and MCP server: what we collect, why, who we share it with, and the choices you have. We handle personal data under Singapore’s Personal Data Protection Act 2012 and, where they apply to you, the GDPR and UK GDPR.
Questions and requests go to support@designcode.io, which also reaches our data protection officer.
What we collect
- Account details. Your email address. If you sign in with Google, the name, email address and profile picture link that Google shares for basic sign-in. Connecting YouTube and connecting Google Calendar are separate, optional permissions, each described below. Your display name is your Google name or, without one, the part of your email before the @.
- What you make. Prompts, canvases and their nodes, chats on a canvas and their messages (shared with everyone in the workspace, like the canvas), files you upload, links you paste (we fetch the public page or image they point to), the text of documents you attach (the document file itself isn’t kept), and everything generated for you: images, video, 3D models, pages, audio and skills.
- Posts you send from Fil. When you post to a connected account, its ID and link on that platform, and the numbers the platform gives for it (such as views, likes, replies and link clicks), read over time and shown only to you.
- Your sites’ visitors. If you publish a site with Fil, what its visitors send through its forms and the page views it counts, kept for you (see Visitors to sites made with Fil, below).
- Teams. The workspaces you belong to, your role in each, and the email addresses you invite. Invite links are stored only as a hash and expire after seven days.
- Friend invites. While Fil is invite-only, who invited whom: the email address a member invited (directly, or by sharing a canvas, a team or a meeting with someone not on Fil), or the account of a friend who came in by their link, when, and whether the friend joined and made something. Members see the friends they invited; the address of someone who came by their link stays hidden from them.
- Waitlist. If you join the waitlist: your email address, when you joined and confirmed it, how many confirmation emails we’ve sent it and when we sent its reminder, and the campaign links that brought you to Fil (see Campaign links, below). The confirmation link is stored only as a hash. If you join while signed in to Fil with the address your account has already verified, your account confirms it and we send no confirmation email.
- Survey. If you answer the waitlist survey: your answers, the email address they came from, and when you sent them.
- Questions in Fil. If Fil asks you a question in the studio or by email (such as what stopped you, or how you’d feel if you could no longer use Fil): your answers, where you gave them, when the question showed, and whether you closed it.
- DesignCode Product Pass. If you claim Fil from your DesignCode Product Pass, DesignCode sends us the verified email address of your membership and your DesignCode member ID. We keep them with when you claimed, to invite that address and so a pass is claimed only once.
- Public profiles. If you join the waitlist, we may look up the profiles you publish about your work, such as LinkedIn, X, Threads, Instagram, TikTok, YouTube, GitHub or your website, from your email address and the name on your Fil account. We keep their links, your name and what you do as they show it, and their follower counts. We never look for home addresses, phone numbers or other private details, and we don’t use people-search sites.
- Runs and credits. Each run’s model, settings, status, cost and credits, and your credit balances, check-ins, transfers and history.
- Payments. If you buy a plan or credits, Stripe collects your payment details. We keep your Stripe customer ID, plan, invoices, orders and the payment events Stripe sends us. We never see or store your full card number.
- Arena. If you turn Arena on: your consent (when you gave or withdrew it, and to which version), and each battle’s prompt, settings, the two models it picked, their results, your vote and how long you took to vote.
- Agents. Agent keys you create (stored as a SHA-256 hash with their last four characters, name and daily cap), apps you approve over MCP, and a log of each change an agent makes: the app, tool, canvas, run, credits and a short summary.
- Use of the studio. How many minutes a day you spend in each part of the studio (such as canvases, the Design tab or the video editor), counted by Fil itself while you use it, and whether you were in Fil for Mac or a browser. It doesn’t record what you click, type or look at. From those minutes and what you do in Fil (your runs and the credits they used, which parts of Fil you used, your check-ins and invites, and whether you published, exported, downloaded, reused or shared something), we keep a short summary of each day you use Fil, to see what helps people come back. The first time you take Fil’s tour, which of its screens you reached and whether you finished it, skipped to its last step or closed it.
- Emails from Fil. Which of our tips and news emails we sent you, when and in which version (such as the next step it suggested), whether you opened a link in one (each link carries a code that tells us, once, when the page it opens loads), and whether you came back to Fil in the days after. For the one about Fil for Mac: whether you’ve signed in to Fil from a browser on a Mac (from the kind of computer your browser names when you sign in) and whether you’ve used Fil for Mac, so it goes only to people on a Mac who don’t have the app, and whether you signed in to the app after it. If you were invited and haven’t used Fil yet, when we reminded you that your invite is waiting, whether you opened its link, and whether you signed up or used Fil in the two days after. If you have invites to give: each time you got more and why (a friend you invited made something, your plan, or from us), when we emailed you about them, and whether you invited a friend in the three days after. Your answer to our newsletter (yes or no), when you gave it and where: when you first open Fil, in Profile, by unsubscribing, or when you ask us to stop. If you unsubscribe, your email address, so we don’t send you them again.
- Campaign links. When someone without access to Fil opens a page of fil.design, we count the visit to learn which posts and pages bring people to Fil: the page, the site or campaign link that sent you (its source, medium, campaign, post and any ref code), your country (from your IP address) and your type of device. Clicks on our short links (fil.design/go/…) are counted the same way. Each carries a code made from your IP address and browser with a random key that changes every day and is deleted after two days, so it can’t be matched to you later. We don’t keep your IP address and use no cookies for this. Where you agree to it (we ask in the regions that require it), your browser keeps the first and last campaign link that brought you, for 90 days, and they go with your waitlist sign-up and, when you create an account, to your account.
- Technical data. Our hosting providers record IP addresses, browser details and requests to run and secure the service.
How we use it
- To sign you in, run Fil, and show your work to you and the teammates you share it with.
- To keep what visitors send through your published sites’ forms, and count their page views, for the people who can edit those sites.
- To run what you ask for, by sending each run’s inputs to the provider of the model you chose, or in Arena to the providers of the models it picks (below).
- To charge and refund credits, bill plans and credit packs, and prevent fraud and abuse.
- To send the email the service needs: sign-in codes and links, team invitations, the invitations members send their friends, and the waitlist’s confirmation (and one reminder if you haven’t confirmed a day later), its survey and your invite. If an invite hasn’t been used two days after it was sent, we send one reminder that it’s waiting, with a link to unsubscribe.
- To send people with a Fil account tips by email in their first month, to help them get going: for example, the day after your first day in Fil, if you haven’t been back, what you made that day with one next step and that day’s free credits; or, after a few quiet days, a question about what stopped you; or, a few days in, if you use Fil from a browser on a Mac, a note about Fil for Mac. Now and then, a personal note from us if you haven’t made anything yet or haven’t been back in a while. Its pictures of your work load from Fil through links that stop working after 30 days. Each has a link to unsubscribe; sign-in emails, invitations and receipts still come. We count who comes back in the days after each one, to learn which help.
- To send our newsletter, big product updates, tutorials and promotions, only to people who said yes to it, when they first opened Fil or in Profile. No answer means no newsletter. Turn it off in Profile or with the link in any of them; unsubscribing turns it off too.
- To decide what to build, how to price it and whom to invite to the beta first, from survey answers, the answers to Fil’s questions and the public profiles of people on the waitlist, and to follow up only where you’ve ticked that we may.
- To see which parts of Fil are used, and where time and credits go, so we know what to improve, and to spot problems such as failing models or unusual spending.
- To learn how people find Fil and which of its pages and features they use, with Google Analytics (see Analytics, below).
- To learn which of our posts, links and pages bring people to Fil, from the visits and campaign links we count on fil.design.
- To keep Fil secure, fix problems and enforce our Terms of Service.
We don’t use your data for advertising, and we don’t sell it or give your prompts and files to anyone to train AI models, except the Arena battles you choose to share (see Arena, below).
Connecting YouTube
Fil uses YouTube API Services when you choose to connect a channel in Plugins. Google asks you which account and channel to connect and which permissions to grant. Signing in to Fil with Google does not connect YouTube, and connecting a channel does not upload anything by itself.
- Access and use. We request permission to upload videos (youtube.upload) and view your YouTube account (youtube.readonly). We use read access to identify the channel you authorized: its ID, name, handle and profile picture. When you set up an automation, we also use it to list your videos and playlists so you can pick one. We use upload access only when you confirm a post, to send the video you selected, its title, description, optional thumbnail and visibility setting to that channel. We keep the returned video ID, link and upload status so you can see how your post went, and we read that video’s view, like and comment counts to show them to you. We do not download your existing YouTube videos or read your viewing history.
- Automations. When you set up a YouTube automation or comment guard, we also ask for permission to manage your YouTube account (youtube.force-ssl); connecting a channel to publish doesn’t ask for it. We use it only for what you set up and turn on, and it runs without asking you each time until you turn it off. We read new comments on your channel’s videos about every two minutes and reply with the words you wrote to comments with your keywords. When a new video goes public, we can add your comment under it, add it to the playlist you picked, add its title and description in the languages you picked, and send its link to a canvas’s agent. A comment guard you turn on sends new comments and their authors’ names to Anthropic’s Claude, which holds spam and abuse for your review in YouTube Studio or answers a question from what you told it, under your channel’s name. Translating a video sends its title and description to Anthropic’s Claude. We never delete your videos, comments or playlists.
- Storage and sharing. Your channel details, granted permissions and connection dates are stored in our Supabase database. Access and refresh tokens are encrypted and used only by our server code; Fil does not receive your Google password. Netlify and Supabase process this data to run the connection. Your connected channel is shown to you, and the content you confirm is sent to YouTube with the visibility you choose. For each comment an automation or guard handled, we keep the commenter’s channel ID and name, the comment’s ID and words, the reply and what was done, and show them only to you in Automations. Anthropic processes what a comment guard or translation sends it. Google handles that content under the Google Privacy Policy.
- Limited Use. Fil’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, or use it to train AI models. Google user data is not included in Arena data sales or training. Human access is limited to your explicit permission, security investigations, or legal requirements.
- Retention and disconnecting. We periodically check Google authorization and refresh channel details. If access is revoked, we delete the connection and its YouTube posting receipts when that check detects it. A daily cleanup removes channel data that has not been refreshed for 28 days and YouTube posting receipts older than 28 days, with their counts. What an automation or guard keeps about people who commented is removed within 30 days, while its counts stay, and what YouTube returned about new comments is deleted within seven days of being handled. The ID of each new video an automation acted on stays with the automation so it doesn’t act twice, and the video or playlist you picked stays until you change it. Disconnecting, or revoking Fil’s access, also deletes the channel’s automations, what they kept and those comments. In Plugins, open your YouTube account and choose Disconnect to request revocation and immediately delete the connection, encrypted tokens and its posting receipts. You can also revoke access in Google’s security settings. Disconnecting does not delete videos already uploaded to YouTube; manage those in YouTube Studio. Your original Fil files and canvases remain until you delete them or request deletion.
For questions, complaints or deletion of stored YouTube data, email support@designcode.io from your Fil account’s address. We delete requested YouTube API data within seven days; you can remove the connection and its posting receipts immediately with Disconnect. YouTube and Google also apply their own terms and privacy policies to their services.
Connecting Google Calendar
Fil uses the Google Calendar API when you choose to connect Google Calendar from the calendar beside My Chat (Sync calendar). Google asks you which account to connect and which permissions to grant. Signing in to Fil with Google does not connect your calendar.
- Access and use. We request permission to see the list of your calendars (calendar.calendarlist.readonly), see the events on them (calendar.events.readonly), and make a calendar called Fil and manage its events (calendar.app.created). We use the list so you can choose which calendars to show in Fil. From the calendars you choose, we read events from 30 days ago to a year ahead (title, start, length, all-day, time zone, place and the event’s link) and show them to you, read-only, in your Fil calendar. We write your Fil events and the meetings you host only to the Fil calendar we make. We never change or delete events on your other calendars.
- Storage and sharing. Your calendars’ names and colours, the events we read and the connection details are stored in our Supabase database, readable only by you. Access and refresh tokens are encrypted and used only by our server code; Fil does not receive your Google password. Netlify and Supabase process this data to run the connection. Events read from your Google calendars are not shown to other people, to Fil’s agents or AI models, or to apps you connect to Fil.
- Limited Use. Fil’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, or use it to train AI models. Google user data is not included in Arena data sales or training. Human access is limited to your explicit permission, security investigations, or legal requirements.
- Retention and disconnecting. Events are refreshed when you open your calendar, while it’s open and hourly, and events no longer on your calendars are deleted at the next refresh. In Sync calendar, choose Disconnect to delete the connection, its encrypted tokens and every event we read, and to remove the Fil calendar from your Google account. To remove Fil’s access in Google too, use Google’s security settings.
For questions, complaints or deletion of stored Google Calendar data, email support@designcode.io from your Fil account’s address. We delete requested Google Calendar data within seven days.
Connecting Instagram
Fil uses the Instagram API with Instagram Login when you choose to connect a professional (Business or Creator) Instagram account in Plugins. Instagram asks you to sign in and which permissions to grant. Connecting an account does not post anything by itself.
- Access and use. We request permission to see your profile and posts (instagram_business_basic), publish posts as you (instagram_business_content_publish) and manage the comments on your posts (instagram_business_manage_comments). We use your profile (its ID, username, name and profile picture) to show which account you connected, and your posts so you can choose one for an automation. We publish only when you confirm a post: the pictures and videos you chose, the caption, and any comments you wrote to go under it. We keep the returned post ID and link so you can see how your post went, and we read that post’s like and comment counts to show them to you. We don’t read your followers, follow anyone, like posts or delete your posts.
- Automations. When you set up an automation, we also ask for permission to manage your messages (instagram_business_manage_messages). An automation reads new comments on the posts it watches and the messages people send you, replies to them, and sends the direct messages you wrote. For each person it answers, we keep their Instagram ID and username, the words of their comment or message, what the automation did and when, and, when the automation asks, whether they follow you and the email address they give it. A comment guard you turn on sends new comments to Anthropic’s Claude to hide spam and abuse or answer a question. Fil’s Inbox reads your conversations from Instagram each time you open it; we keep only how you marked each one, not the messages.
- Storage and sharing. Your account details, granted permissions and connection dates are stored in our Supabase database. Access tokens are encrypted and used only by our server code; Fil does not receive your Instagram password. Netlify and Supabase process this data to run the connection. What you publish is sent to Instagram, which handles it under the Meta Privacy Policy. We do not sell Instagram data, use it for advertising, or use it to train AI models, and it is not included in Arena data sales or shared runs.
- Retention and deletion. What Instagram sends us about new comments and messages is deleted after seven days. What an automation keeps about the people it answered stays while the automation and your connection do, and how you marked an Inbox conversation until 180 days without a change. In Plugins, open your Instagram account and choose Disconnect to delete the connection, its encrypted tokens, its automations and what they kept; posts you published stay on Instagram. You can also remove Fil in Instagram’s settings under Apps and websites (instagram.com/accounts/manage_access): Fil’s access stops, and when you ask Meta to delete your data, we delete the connection, its automations and what Instagram sent us about the account as soon as Meta tells us.
For questions, complaints or deletion of stored Instagram data, email support@designcode.io from your Fil account’s address. We delete requested Instagram data within seven days.
AI model providers
When you run a node, its prompt, settings and the references wired into it (images, video, earlier pages and document text) go to the provider of the model you chose; an Arena battle sends its prompt and settings to the providers of the two models it picks. Images usually go as links that expire within an hour; some providers receive the file itself.
- OpenAI: GPT Image images, edits and cutouts, GPT pages and skills, and GPT-4o mini voiceover. If you connect your ChatGPT plan in Settings, the pages and edits you run on its models, and what you ask the canvas’s chat and the 3D, Slides and video editors’ agents on them (with the canvas as the chat sees it, and pictures of the model or slides), go to OpenAI with your own ChatGPT sign-in and count against your plan; we keep that account’s email, plan and models, with its tokens encrypted, until you disconnect.
- Anthropic: Claude pages and skills.
- Google: Nano Banana images, Gemini Omni video, Gemini pages, Gemini voiceover and Lyria music.
- xAI: Grok Imagine video, Grok pages and skills, and Grok voiceover.
- MiniMax: MiniMax H3 Max video, and MiniMax M3 and M3.1 Flash pages and skills.
- Moonshot AI: Kimi pages and skills.
- StepFun: pages and skills, only on accounts given early access to its models.
- SenseNova (SenseTime): pages, skills and images, only on accounts given early access to its models.
- Meta: Muse Image images and edits, and Muse Spark pages and skills, on Meta’s standard tier, which doesn’t train on what it’s sent.
- Black Forest Labs (BFL): FLUX 3 images, edits and video.
- Kling: Kling 3.0 video.
- BytePlus (ByteDance): Seedream 5.5 and 5.0 images, and Seedance 2.5, 2.0, 2.0 Fast and 2.0 Mini video; and, on BytePlus Vision AI, DreamActor M2.0, which receives the picture of a character and the video whose motion it copies, and OmniHuman 2.0, which receives the photo of a person and the sound they say.
- Microsoft: MAI-Image images and edits, sent through OpenRouter, which passes each request on to Microsoft’s Azure.
- Higgsfield: Grok Imagine 2.0, Soul 2 and Qwen Image 3 images, and Kling 3.0 Pro, Kling 4.0, MiniMax H3, Wan 3.0 and HappyHorse 1.1 video. Higgsfield may pass requests on to those models’ developers.
- Ideogram: Ideogram images, edits and cutouts.
- Magnific: upscaling and cutouts.
- HeyGen: talking photos (HeyGen Avatar IV, Avatar V and Avatar 6): it receives the photo of the person and the words they say, and sends back the video. For Avatar V and Avatar 6 it first makes the photo a photo avatar, which stays in Fil’s HeyGen account.
- Tripo and Meshy: 3D models, rigging and animation.
- ElevenLabs: voiceover, sound effects and music, captions, a meeting’s notes and transcript (the voices of a meeting whose notes are taken, heard once it ends) and its live captions when they’re on (those voices heard as the meeting goes, the words sent back to everyone in it), and the teleprompter following your voice when you turn that on: it hears your microphone while a take records and sends back the words it hears.
- Cleanvoice: cleaning up a voice when you ask (a voice recording, or a sound or video in a video edit with Studio Sound): it receives that file and sends back the clean sound.
- NVIDIA: eye contact when you ask, on a video in its Edit tab (in early testing, for Fil’s owners only): it receives that video and sends back one with the eyes redrawn looking into the lens.
- fal (fal.ai): finer edges when you ask, on a person cut out of a video in a video edit, made by VEED’s video background removal: it receives the stretch of that video the clip plays (the picture only, without its sound) and sends back a WebM of the person on a see-through background, which we ask fal to delete once we have it.
Fil also uses some of these models itself to help you. Anthropic’s Claude reviews a run’s prompt, settings and up to four reference images before it starts, answers in a canvas’s chats (reading the chat’s recent messages, a list of the canvas’s nodes and their prompts, and up to four images sent or mentioned), plans nodes from an Auto prompt or a chat, suggests variations, plans a page’s images, checks a 3D reference image, names canvases from their prompt and a small preview, and checks Arena prompts for personal details before a battle can be shared. OpenAI’s GPT Image paints covers for videos, pages and 3D models from their prompts.
Providers can refuse a run under their own safety rules. Each handles what it receives under its own terms and privacy policy, and some keep requests for a limited time to monitor abuse.
Other services we use
- Supabase handles sign-in and stores accounts, the database and your files, in Singapore.
- Netlify hosts the website and runs our server code.
- Stripe processes payments.
- Resend delivers sign-in, invitation and waitlist emails, our tips and news, survey answers to us, and the answers to a site’s forms to the people who ask to be emailed them.
- Anthropic’s Claude searches the web for the public profiles of people on the waitlist.
- Google provides Google sign-in, the optional YouTube and Google Calendar connections described above, Google Analytics (see Analytics, below) and the fonts the site loads from Google Fonts.
- The public Images, Videos and 3D pages load pictures from Aura Assets’ storage and sample 3D models from jsDelivr, which see your IP address as any site you load content from does.
These providers process data for us to run Fil and may be outside your country, including in the United States. Where the law requires it, we rely on their data processing terms to protect these transfers.
What becomes public
What you make is private to your workspace. A team workspace is shared with its members, who can see your display name, your work in that workspace and, while you’re on a shared canvas, your cursor and selection.
On the Free plan, each image, video and 3D model you generate is shared to Explore as it’s made. On Starter, Pro and Max, a file is shared only when you choose Share to Explore, or share new runs with the lock in the studio. A shared file is public on Fil’s Images, Videos or 3D pages, with its prompt, model, type and size, the date it was shared and your display name. Anyone can view it and reuse the prompt. Moving it to the trash takes it off Explore, and on Starter, Pro and Max so does unsharing it, but we can’t recall copies others have already saved.
Arena’s public leaderboard shows only totals for each model, never your prompts, results or votes.
To change your display name, email support@designcode.io.
Visitors to sites made with Fil
People publish sites with Fil, and their pages can have forms, such as a survey, a contact form or a sign-up. This section is for the people who visit those sites.
- Forms. When you send a site’s form, we keep what you filled in, the form’s name, the page you sent it from and when.
- Page views. For the site’s Analytics we count each page you view: the page, when, how long you looked at it, the site or campaign that sent you, your country (from your IP address), and your type of device, browser and system. The site’s people see only totals.
- No address kept. Answers and views carry a code made from your IP address and browser with a random key that changes every day and is deleted after two days. It counts visitors and limits how many answers one visitor can send (20 an hour), and once its key is gone it can’t be matched to you. We don’t keep your IP address.
- Who decides. The site’s owner decides what its forms ask and what happens to the answers; we keep them on the owner’s behalf. Only the people who can edit the site in Fil’s studio can read its answers: in the studio, as a CSV file they download, in an email for each answer if they turn that on, or through an agent they connect over MCP. We don’t use answers for anything else, except where we must to keep Fil secure or comply with the law.
- Emails. If someone who can edit the site turns on Email me each answer, we email them each answer through Resend: what you sent, by question, and the page you sent it from. If the form asked for your email address, they can reply to you straight from it. That email then sits in their inbox, outside Fil, so deleting your answer in Fil doesn’t delete it; ask them to delete it too.
- Your answers. To see, correct or delete what you sent, ask the site’s owner, who can delete answers at any time. If you can’t reach them, email support@designcode.io with the site’s address and enough about what you sent for us to find it, and we’ll pass your request on, or act on it ourselves where the law requires.
- How long. Answers stay until the site’s people delete them, or the site, its canvas or the workspace it’s in is deleted. Emailed copies stay in their inboxes until they delete them. Page views are deleted after 25 months.
The site’s owner made its pages and is responsible for telling you what they collect and why. Anything else their pages load, such as fonts, videos or other services, is covered by those services’ terms and the owner’s own notice, not this policy.
Arena
Arena is optional. Each battle runs your prompt on two models Fil picks at random, from any of the providers above, and shows both results without the models’ names; you vote for the better one, and the battle is free (see the Terms of Service). You turn it on yourself, in the studio, after reading what it shares. In a team workspace, the team’s owner must turn it on for the team as well. Nothing else you make in Fil is shared this way.
- What we share. For each battle you vote on, we may share and sell a record of it to AI companies such as OpenAI and Anthropic, who may use it to evaluate and train their AI models. A record holds the prompt and its settings, both results, which models made them, your vote, how long you took to vote, the month, and a code that’s different in every delivery: a buyer can tell which votes in a delivery came from the same person, but can’t link them to you or to other deliveries.
- What we leave out. Your name, email address, account, workspaces, canvases, IP address and exact times. Battles can’t use uploads, reference images, documents or links, so none of your files are included. Before a battle can be shared, Claude checks its prompt for personal details (private people’s names, email addresses, phone numbers, street addresses) and for named real people, and we leave out every battle it flags.
- Stopping. Turning Arena on is your consent, and you can withdraw it at any time in Arena’s settings or by emailing us. We then stop collecting, delete the battles we haven’t delivered and our copies of their results, and take your votes off the leaderboard. Battles already delivered to a buyer can’t be recalled.
- What it’s worth. Free battles are what we give you for these records (in California, a financial incentive). We value a shared battle at what we give back for it: the full cost of its two runs at our providers’ list prices: under 25 US cents for an image battle, under $1.50 for a 3D model, under $2 for a page and under $3.50 for a video. You join by turning Arena on, and can leave as above.
- Buyers may be outside your country, including in the United States, and handle what they receive under their own terms.
Even so, don’t put personal or confidential information, or client work, into an Arena prompt.
Analytics
Fil uses Google Analytics on its own pages (the website, the docs, the workflows, Community and the studio) to learn how people find Fil and which of its pages and features they use. It isn’t on sites made with Fil, whose owners choose their own, and it never sees what you make: no prompts, canvases, files or the words on your pages.
- Pages. The address of each page you view, with its private parts taken out first (invitation, confirmation and sign-in codes, a survey link’s token, and the ids of canvases and other things you open), its title, the page you came from and the site or campaign that sent you.
- A few moments. Joining the waitlist, creating an account (and whether with Google or email), opening the studio for the first time, checking in for credits, and starting and finishing a checkout (the plan or credit pack and its price). In the studio, which parts you open (such as a canvas, the Design tab or the video editor), each run you start (image, video, 3D, code or audio, and its model), the workflows you start and run (which one, and how many steps) and publishing a site. Never your email address, your name, anything you type or what you make.
- Your device. Your type of device, browser and system, its language and screen size, and your rough location (country and city), which Google works out from your IP address without storing the address.
- Cookies. Google Analytics sets first-party cookies (named _ga and _ga_ followed by an id) holding a random number, so visits from one browser count as one visitor. They expire 13 months after your last visit.
Your choice. In the European Economic Area, the UK and Switzerland, Fil asks first: no Analytics cookies are set unless you choose Accept. To know whether to ask, a page whose time zone could be there checks once a visit which country you’re in, which our host Netlify works out from your IP address; the address isn’t kept. Until you choose, Google receives page views and moments without cookies or a lasting id, which it uses only to estimate totals. Elsewhere, Analytics is on unless you choose Decline. If you decline, Fil deletes its Analytics cookies and stops loading Google Analytics. Change your choice at any time in Cookie settings, also linked from the foot of Fil’s pages, or block Google Analytics on every site with Google’s opt-out add-on.
No advertising. Google signals and ad personalization are off, and nothing goes to Google’s advertising products. Google processes this data for us under its data processing terms; see how Google uses information from sites that use its services. Google Analytics keeps it for 14 months, then deletes it, and we see it as reports.
Cookies and local storage
Fil uses no advertising cookies. Its only cookies are Google Analytics’, as above. Your sign-in session, your preferences (such as theme, recent models and settings), your cookie choice, which one-time moments Analytics has counted (so they count once), the country checked for your cookie choice (until you close the tab), the first and last campaign link that brought you (90 days, once you agree; see Campaign links) and short hand-offs (such as a prompt you start on the public site, kept for an hour) are stored in your browser’s local storage. Clearing it signs you out, and Fil asks for your cookie choice again where it needs one.
How long we keep it
- Your account, content and run history, your minutes of use and how far you went in the tour: while your account is open.
- Which tips and news emails we sent you, and your answer to our newsletter: while your account is open. That we reminded an invited address: while its invitation stands. An address that unsubscribed: for as long as we send such emails, so it isn’t emailed again.
- Arena battles you share: while your consent stands; withdrawing deletes those not yet delivered, and buyers keep what they received under their own terms.
- Files in the trash: they stay recoverable until your account is deleted, or until you ask us to remove them sooner.
- Waitlist addresses, and the public profiles we found: until you’ve had your invite, or until you ask us to take you off the list. An address that’s never confirmed: 14 days after our last email to it (its reminder).
- The campaign links that brought you: with your waitlist address; once you’re invited, with your invitation and then your account, while it’s open. Visits and short-link clicks counted on fil.design: 25 months; the daily key behind their codes: two days. In your browser: 90 days, or until you clear it or say no.
- Survey answers, and answers to Fil’s questions: while they help us plan Fil, and no longer than two years, or until you ask us to delete them. Answers to Fil’s questions also go when your account does.
- A DesignCode Product Pass claim: while your access to Fil lasts, so the pass isn’t claimed twice, or until you ask us to delete it.
- Who invited whom, and the addresses members invited: while the member’s account is open, or until the person invited asks us to delete theirs.
- Answers sent through a published site’s forms: until the site’s people delete them, or the site, its canvas or its workspace is deleted; copies emailed to them stay in their inboxes until they delete them. Page views counted for a site’s Analytics: 25 months; the daily key behind visitor codes: two days.
- Sign-in codes expire after an hour, invitations and waitlist confirmation links after seven days and MCP approval codes after five minutes.
- Payment records: as long as tax and accounting law requires, even after your account is deleted.
- Google Analytics data: 14 months; its cookies: 13 months after your last visit.
- Server logs: for the limited time our hosting providers keep them.
Deleting your data and your rights
To delete your account, email support@designcode.io from the address you sign in with. Within 30 days we’ll delete your account, your personal workspace and its files, revoke your agent keys, take down anything you shared to Explore and delete the Arena battles we haven’t delivered. Teams you own are handed to another member if you ask, or deleted. We keep only the payment records the law requires, and copies in backups are overwritten on their normal cycle.
To leave the waitlist (with the public profiles we found), or to have your survey answers deleted, email support@designcode.io and we’ll delete them.
To see or delete what you sent through a form on a site made with Fil, ask the site’s owner, or us if you can’t reach them (see Visitors to sites made with Fil).
You can also ask for a copy of your data, to correct it, to delete particular files for good, or to stop a use you’ve agreed to. You can download your files from the studio at any time.
Depending on where you live, you may have further rights, such as to object to or restrict how we use your data, or to complain to a data protection authority (in Singapore, the Personal Data Protection Commission). We answer requests within 30 days.
Security
Files are kept in private storage and opened through links that expire. Database rules limit every record to the people who should see it. Server keys for model providers and payments never reach your browser, and agent keys are stored only as hashes. No system is perfectly secure, so keep your sign-in email and agent keys safe, and tell us at once if you think someone else has used them.
Children
Fil isn’t meant for anyone under 18, and we don’t knowingly collect data from children. If you believe a child has given us personal data, contact us and we’ll delete it.
Changes to this policy
We’ll post changes here and update the date at the top. If a change materially affects how we use your data, we’ll tell you by email or in the studio before it takes effect.