TAEONA

Privacy policy

Who we are

TAEONA is a product of Taeona, Inc., 742 S Hill St, STE 903, Los Angeles, CA 90014. Taeona, Inc. is the data controller for the information described here. Privacy questions and requests go to hello@taeona.com — see support.

What the product does with your data

This section describes the software's actual behaviour, written from the code and accurate as of 2026-09-24.

• Your account. Your email address; your name and profile picture if you sign in with Google; your phone number if you sign in by SMS. There is no password: sign-in is a one-time code, or Google.
• Sign-in records. Each session stores the IP address and browser user-agent it was created from, and each one-time code stores the address or number it was sent to and the IP address that asked for it. Both exist to stop other people's accounts being attacked and to stop paid SMS being pumped. Sessions and codes are stored hashed, never in a form that could be replayed.
• Invitations and the waitlist. The beta is invite-only, so we keep the addresses invited, who invited them and when. If you joined the waitlist on our website we keep the name, email, optional brand website and which form you used.
• Your website and catalogue. When you supply a website address, TAEONA reads public pages and, for Shopify stores, the public product catalogue, and stores the product photography it finds so creative can be generated from it.
• Your business's public Google listing. If your site carries little photography, we look the business up by name and address in Google's Places API and store photographs from the listing — some of which were uploaded by customers rather than by you — plus a few short review excerpts as background notes for writing captions.
• A public social profile you name. If you ask the assistant to read a brand's own public Instagram profile, we fetch it through a third-party reader and store what it returns alongside your brand notes.
• What you upload. Images and logos you add yourself.
• Content you create. Your conversations with the assistant, captions, image and video briefs, the generated images and video, and the schedule they are planned against. Automated quality checks on generated frames are also stored.
• Sound in generated video. Films generated by TAEONA carry an audio track, and it is generated with the picture by the same model — the room's own sounds, the action's sounds, and, when the brief calls for a spoken line, a voice reading a script this product wrote. No separate speech service is involved, and when a film has no script we instruct the model that nobody speaks in it. Where one film is rendered in several parts, a short sample of the first part's audio is sent back to the same provider with the later parts so the voice stays the same across the cut.
• Connected accounts. When you connect a social or commerce account, TAEONA stores an access token, the account's name or handle, its follower count where the platform returns one, and the list of destinations (pages, channels, boards, locations, shops) you can post to. Tokens are encrypted at rest with AES-256-GCM and are never shown in the interface, written to logs, or included in error messages.
• Publication records. For each post published, the platform's own identifier and public URL, who approved it, and when.
• Publishing-permission records. Whether this workspace approves each post or has turned automatic publishing on, and for each change: the email address of the person who made it, the time, and which version of the agreement they accepted. No IP address and no browser details are stored with it.
• Credits, and payments once billing is switched on. Your workspace's credit balance and the ledger of what was granted and spent. When billing is enabled, a record of each purchase: which pack, the amount, the currency, the time, and the identifiers Stripe gives us. Card numbers are entered on Stripe's own payment page and never reach us.
• Feedback you send us. The message, the screen you were on, your browser user-agent, any screenshots you attach, recent errors from your browser, and a snapshot of the server's recent log lines so the problem can be reproduced.
• Server logs. Ordinary operational logging, which can include email addresses and workspace identifiers.

What it does not collect

• No customer or order data from your shop. The Shopify integration requests product, file and content permissions only. It does not request access to orders, customers, addresses, email addresses or payments.
• No card details. When billing is switched on, payment details are entered on Stripe's hosted checkout page. We never see or store them.
• No advertising or analytics tracking in the product. One essential cookie keeps you signed in.
• No voice recognition, and nobody's real voice. TAEONA does not transcribe audio, does not accept audio you upload, and does not clone or imitate a real person's voice. The only voice it produces is one the video model performs from a written script.

Who decides what gets published, and when

Connecting an account does not authorise a post. How posts reach your accounts is a setting on your workspace, and it is yours to change:

• Approve each post — the default. Nothing goes to a connected account until someone in your workspace approves that specific post. The approval covers that exact content: if the post is edited afterwards the approval stops applying and we ask again. An approved post goes out at the time it was scheduled for.
• Automatic publishing — only if you turn it on. It is off until the workspace owner turns it on, which is a separate step with its own wording: we record who turned it on, when, and the exact wording they were shown. You can turn it off again at any time, and turning it off withdraws the posts already queued that nobody approved individually.
• Some platforms always ask. Under their own developer rules, a person has to act on each post for X, TikTok, YouTube, LinkedIn, Pinterest and Google Business Profile, so those accounts stay approve-each even while automatic publishing is on, and the app says so next to each of them.

Why we process it, and on what basis

• To provide the service you asked for — reading your site, generating creative, scheduling it, and publishing the posts you have authorised. Basis: performance of a contract.
• To keep the service working and secure — error logs, rate limiting, and detecting abuse. Basis: legitimate interests.
• To take payment, once billing is switched on. Basis: performance of a contract, and legal obligation for the records kept afterwards.
• To meet legal obligations — retaining records of what was published on your behalf and of money taken. Basis: legal obligation and legitimate interests.

We do not sell your data, and we do not use your brand assets or generated content to train our own models.

How long we keep it

• Access tokens — until you disconnect the account, or the platform revokes them. Deleted on disconnect.
• Your workspace (brand kit, catalogue, generated media, calendar, conversations) — for as long as your account is open, then deleted within 30 days.
• Publication records — kept for two years, because they are the record of what was posted on your behalf and are what a platform asks for after the fact.
• Sign-in and invitation records (invitations, one-time-code records, waitlist entries) — kept for twelve months. These are keyed to an email address rather than to a workspace, so they outlive a deleted account.
• Feedback you sent us, and its screenshots — kept after account deletion, because a bug report is addressed to us and has to survive the workspace it came from. Kept for two years.
• Billing records — once billing is switched on, the record of a payment is kept after the workspace is deleted, because tax and accounting rules require it and because a refund can arrive later. It holds the workspace id, the amount, the time and Stripe's identifiers; it holds no content. Kept for seven years, the period United States tax and accounting rules require.
• Publishing-permission records — kept after the workspace is deleted. One record is kept deliberately: the log of when a workspace turned automatic publishing on or off, and the email address of the person who did. It is the evidence that posting was authorised, it is the record a platform asks for after the fact, and it would be worthless if closing the account erased it. It holds no post content.
• Deletion records — when posts or a workspace are deleted we keep a line saying what was removed and when, with identifiers and counts only and no content, so we can answer "where did this go".
• Logs — application logs are kept for 30 days. Our hosting provider keeps its own request logs under its standard retention, which we do not control.

Deleting your data

Disconnect an account in the app to revoke its access and delete its credentials — any post already queued for it is cancelled at the same time. Delete account removes your user record, the workspaces where you are the only member, and the files in them; the exceptions are listed above. Facebook and Instagram users can also request deletion through Meta; see data deletion.

Who else processes it

We use the following processors. Each receives only what it needs to do its job.

• Supabase — the database and the file storage that hold your workspace, including the encrypted tokens and the generated media.
• Railway — hosting for the application and its server logs.
• OpenAI — generating text and images, describing photographs, and web research for trends. Receives your brand information, your product photography and the briefs written from them.
• Atlas Cloud (Seedance) — generating video, and the sound and any spoken line in it. Receives the product photograph, the shot brief for that film, the spoken script when there is one, and — for a film rendered in several parts — a short sample of the audio it returned for the first part, so the voice does not change halfway through.
• Resend — email delivery: sign-in codes, beta invitations, waitlist confirmations, and the internal alert that tells our team you sent feedback (which carries your address and an excerpt of your message).
• Twilio — sending sign-in codes by SMS, where phone sign-in is offered. Receives the phone number.
• Google — three separate things: Google sign-in, if you use it, which returns your Google account id, email, name and profile picture; the Places API, which receives your business's name and address and returns the listing, its photographs and review excerpts; and Google Fonts, from which the sign-in page and the app load typefaces, so your browser's IP address and user-agent reach Google when a page loads.
• Apify — reading public web data: trend research, and the public social profile you asked us to look at. Receives the handles and URLs you supply.
• Firecrawl — reading public web pages during a crawl. Receives the URLs you supply.
• Cloudflare — DNS for our domains and hosting for our marketing website, including the waitlist form.
• Stripe — payment processing, when billing is enabled. Stripe collects your payment details directly on its own hosted page and tells us only the outcome, an amount, and identifiers. Until billing is switched on, no payment data exists at all.
• The platforms you connect (Meta, Google, TikTok, LinkedIn, Pinterest, X, Shopify) — receive the content you have authorised for publishing, and nothing else.

Each of these processes data on our behalf under its own standard service and data-processing terms. We do not sell data, we do not use it for advertising, and we do not share it with anyone outside this list.

Where it is processed

Taeona, Inc. is a United States company and your data is stored and processed in the United States. If you are outside the United States, using TAEONA means your data is transferred there. Where a provider moves data across borders on our behalf, it does so under the data-transfer terms of its own standard agreement.

Your rights

Depending on where you live you may have the right to access, correct, delete, export or restrict the processing of your personal data, and to object to processing based on legitimate interests. Most of these you can exercise yourself in the app — Disconnect for a single account, Delete account for everything. For anything else, write to hello@taeona.com and we will respond within 30 days. You may also complain to your local data protection authority.

Cookies

We set one essential cookie, which keeps you signed in. There is no advertising or analytics tracking in the product, and no third-party tracking pixels. Because the only cookie we set is the one that signs you in, there is nothing to consent to and no consent banner.

Children

TAEONA is a business tool and is not intended for anyone under 18.

Changes

If this policy changes materially we will tell you by email and in the app before the change takes effect.