Privacy Policy

TRNCH is run by TRNCH LLC, an Arizona limited liability company, and “we” and “us” in this policy mean TRNCH LLC. It covers the TRNCH website and the tool you sign in to, and it says what we hold about you, why, who else sees it and what you can make us do about it.

For anyone in the EU or the UK: the controller of the personal data described here is TRNCH LLC, an Arizona limited liability company. Write to [email protected] for anything in this policy.

Ten kinds of thing, and nothing else.

Your account

The name and email address you sign up with and your password, which is stored only as a one-way hash, so nobody here can read it. When you sign up we email you a link to confirm your address, and we record whether you have.

If you sign in with Google. Google asks you first, and then gives us only your basic profile: your name, your email address, whether Google has confirmed it, the address of your profile picture and an identifier for your Google account, with the sign-in tokens it issues. We ask for nothing else: no contacts, no Gmail, no Drive, no calendar.We keep the profile with your account in our database (see hosting), and we don’t keep Google’s sign-in tokens: any kept before 27 October 2026 are erased the next time you sign in with Google. We use the profile only to make your account, sign you in and show your name and picture in the account menu, and you need no password with us. Your name and email address are otherwise used as they are for every account: by Stripe when you pay, by Resend for account emails, and in the record of what you agreed to at sign-up. We do not sell any of it, use it for advertising, share it with anyone else, or use it to train any AI model, and the profile is deleted with your account. You can take away our access at any time in your Google Account’s security settings (myaccount.google.com/connections). TRNCH’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Sign-up asks for no code. If your account was made with one, we record which code it was, and when (the code’s own row, never the code itself, which we keep only in a form that can’t be read back), and so whether it is an early access, creator or tester account, and when a tester’s free days end.

When you create an account we also keep a record that you agreed to the Terms of Service and this policy: the time, the exact words beside the box you ticked, which version of each document was in force, the account and email address it belongs to, and the IP address and browser user-agent the sign-up came from. It is kept apart from your account, so closing the account does not delete it (see below).

Your sessions

Each time you sign in we record a session: a random token, the time it was made, the time it expires, the IP address it came from and the browser user-agent string. That is how you stay signed in and how we can tell one person from another account sharing the same login. Signing in signs your account out everywhere else, so an account has one session at a time.

Your subscription

Your Stripe customer identifier, your Stripe subscription identifier, which plan you are on, its status, the date the current period ends and whether it is set to cancel. Card numbers, bank details and billing addresses are handled by Stripe on Stripe’s own pages and never reach our servers. So that each person gets one free trial, we keep the fingerprint Stripe gives the card that started one (a code that tells two uses of the same card apart from others; it is not the card number and can’t be turned back into it), or, for a Stripe Link wallet, a code made from the wallet’s email address; for an Apple Pay or Google Pay card, also a code made from its brand, last four digits and expiry date; a code made from your email address, which also keeps welcome credits to one per address; and a code made from your IP address, which lets us count the trials started from one internet address in 30 days. These codes are one-way: they hold no address and can only be matched against the same address again. We keep the card and email records with the account and subscription they belong to, after the account is deleted, for as long as we offer a free trial. The IP address code goes with the subscription and is deleted about 30 days later. Your Stripe customer record (your name, email address and payments) stays with Stripe after you delete your account, because payment records must be kept for tax; when a new account starts a plan, we ask Stripe whether its email address has had a plan before, and if it has, the plan starts without a free trial.

If you tell us why you are cancelling, the reason you pick and any words you type are saved on your subscription at Stripe. On a paid plan, press Keep before the plan ends and they are removed. Otherwise they stay with your Stripe record, including after you delete your account.

When you start a plan we also keep a record of the checkout: when it happened, whether you ticked the box agreeing to the terms and to automatic renewal, the exact words shown beside that box and the pay button, which version of the Terms of Service and of this policy was in force, the plan, price and trial end you were offered, and the Stripe identifiers. Stripe keeps a copy of the same facts.

When you buy a credit pack we keep a record of it in the same way: when, which pack, what you paid, whether you ticked the box agreeing to the terms, the words shown beside the pay button, and the Stripe identifiers. Every credit added to or taken from your account is a line in your credit history (welcome credits, a pack, a credit used on a validation or a store build, a credit given back, free credits that expired), because your balance is counted from it. Each time you build a new store we also record that one store build was used, which store it was for, and whether it came from your plan or from credits.

What you do in the tool

The products you save, the filter sets and quick-pick numbers you save, which categories you have opened, each on-demand check you run (which product, which kind of check, the search words, when) and each video download you ask for (which clip, whether it succeeded, how large the file is). These exist because your plan has limits and because a saved list is the feature. We also keep the time zone your browser reports, so your daily limits start again at your own midnight.

Your stores

For each store you make with the store builder: its settings and words, the photos and videos you upload, the business details you enter for its legal pages (business name, street address, phone number and support email, which are personal data if you trade under your own name), and the store’s files. They are kept so we can show, edit and export the store, and deleted with it. Separately, we keep a record each time you confirm the statements the builder asks for before a download (one of them written from your store’s own settings: its offer, countdown, delivery time, warranty and guarantee), each reminder it shows you about the words you typed (a review or rating, a health claim, “#1” or “best seller”, urgency, a price or a warranty) or about your store’s settings (a “free” offer or crossed-out prices, the countdown, a warranty, “risk-free”, delivery days shorter than the product’s listing, another company’s brand on the product), your answer to each warning window that shows those reminders (its button, or closing it), and each download: the store, your account, the time, the wording you saw, the words or setting that brought up a reminder, which reminders an answer was to, the statement about your store’s settings as it stood, and a copy of any row of stars or review words on the page at that moment. Each time you upload a video we also record your confirmation that you filmed it or have its creator’s permission, with the store, your account, the time, the wording, the file’s size and a fingerprint of it (a SHA-256 hash, from which the video can’t be rebuilt). We delete the file you upload once we have made the store’s own copy of it, and the location data and other metadata in an uploaded photo or video go with it. That record is not deleted with the store (see below).

If you connect a Shopify store through the TRNCH Store Builder app: the store’s Shopify address (its myshopify.com name), its name and currency, which TRNCH account connected it and when, the permissions you gave the app, and the keys Shopify gives the app to act for your store, which we keep encrypted and never show to anyone, you included. To fill in your details for you, we read the store’s contact email and address, whether it has a plan, and the policies already written on it. When you put a store on Shopify, we send it the product with its photos, options and the cost you enter, the policies and the shipping rates from your store in the builder, and we read back what Shopify made and the product’s state there, such as draft, active or changed since you sent, so we can show you. We also check the store’s public front page for whether it asks for a password and which theme it shows. The app does not read your customers or orders, and it keeps no customer data. If we add a view of your sales, it will ask Shopify’s permission first, when you open it, and read only the order lines for the products the builder put on your store: which product, how many, the price paid, discounts and refunds, and the cost per item you entered in Shopify. Never a buyer’s name, email address, phone number or address. We use them only to show you your own sales.

Your Meta connection (the ads manager)

If you connect Meta in the ads manager, you sign in on Meta’s own screen (Facebook Login for Business) and choose which ad accounts, Pages and pixels TRNCH may use. Meta then gives us your Facebook user ID and name, a key (an access token) that lets TRNCH act in what you chose, and the ad accounts, Pages and pixels themselves (their IDs and names). We keep the key encrypted on our server and never show it to anyone, you included, along with the ad account, Page and pixel you picked and when you connected.

While you use the ads manager we read from Meta, for the ad account you picked: its status (and why, if Meta has disabled it), whether it has a payment method, its spending cap, amount spent, currency and time zone; its campaigns, ad sets and ads, each ad’s review state and Meta’s reasons; and their results: spend, impressions, reach, clicks, adds to cart and purchases. We read them when you open the ads manager to show them to you, and once a day if you switch on the daily email. To load pages quickly we hold Meta’s last answer in our server’s memory for up to ten minutes (an hour for lifetime totals); it is never written to disk, and then it clears itself. When you press Send to Meta, we create the campaign, ad set and ads you made, with their videos, pictures and words, in your ad account, all paused. We change something there (pause, turn on, change a budget, a stop date or Audience Network, copy an ad or campaign, add a batch) only when you press for it, and when you switch on Stop loss we add a rule to your ad account that Meta runs itself, and we keep a record of each change: what it was, what it became and when, so you can undo it.

We use what we get from Meta only to run your own ads manager for you. We never sell it, never use it for the research side of TRNCH or for any other customer, never combine it across customers, and never use it to build a profile of you or anyone else. To have it deleted: press Disconnect in the ads manager; remove TRNCH from your Facebook settings (Settings & privacy › Settings › Business integrations), which sends us Meta’s deletion request and gives you a confirmation code and a page that shows its status; delete your TRNCH account; or write to [email protected]. Each deletes the key, the connection, the record of changes and the Meta IDs we kept of what we created for you (ad account, campaigns, ad sets and ads, in your drafts and their results). The campaigns you drafted in TRNCH are your own work and stay, without those IDs, until you delete them; what we created in your ad account stays in Meta, under your control.

Support and server logs

Anything you send us asking for help, and what we reply; it is kept in our Google Workspace mailbox. Our server logs events and errors (for example that an email was sent or a sign-in failed, with the account’s internal number or a Stripe identifier, and the time) for security and debugging. It does not log the pages you visit. Cloudflare, which carries every request to the site, keeps its own request logs.

The affiliate program

If you apply to be an affiliate or a paid creator: your name, your email address, the accounts you give us (TikTok, Instagram, YouTube, X, Facebook, a website or another link, as the handles or links you type), your follower range, your niche, what you tell us about why you would be good, and the record that you agreed to the Affiliate Program Terms (when, the words beside the box, the version, the IP address and browser it came from). We look at the public profiles and posts of the accounts you give us, to decide on your application and, if we take you on, to check your posts about TRNCH. If we call you, we may keep notes of the call. If we take you on: your link and code, the sign-ups and payments that came through them and the commission each earned, the posts and videos you make for us and what we agreed for each, the payout details your payout service gives us, and the tax form we need before we pay you: a Form W-9 with your taxpayer identification number, which can be your Social Security number, or a Form W-8 if you are outside the United States.

If you make your account through an affiliate’s link or code, we record which affiliate it was, so we can pay them. The affiliate sees only that a sign-up or a payment came through them, its date and amount, and the commission it earned, never your name, your email address or anything else about you.

The waitlist

If you joined the waitlist on trnch.net before 23 October 2026, we hold the email address you gave, the IP address and browser it came from, whether you confirmed it and any referral link you used. We send it no email and use it for nothing else, and we delete the list by 22 November 2026, 30 days after the site replaced the waitlist, as the waitlist’s own page promised. Write to [email protected] to be removed sooner.

Ad tags

If you reached us from an ad in the United States: the tags in that link, such as the campaign, the video and Meta’s click ID, the page you landed on and when, and, if you then make an account, the IP address, browser and Meta cookies of that sign-up (see cookies).

• No card numbers, CVV codes or bank details. Stripe holds those.
• No session recording and no heatmaps. We use Meta’s ad pixel on a few public pages (see cookies), and Cloudflare Web Analytics, which sets no cookie and counts visits without following you.
• No location beyond what an IP address implies, no contacts, no device fingerprinting of our own (Cloudflare’s bot check is under who else sees it).
• No special category data: we never ask for health, biometric, racial, religious, political or sexual information, and you should not send it to us.
• We take no money for personal information. What we send Meta for advertising is the one exception to “no sharing for advertising”, and you can turn it off (see your choices).

Each use below is tied to the reason we are allowed to do it, in the wording EU and UK law asks for.

• To run your account and give you what you paid for: account details, sessions, saved products and filters. Performing our contract with you.
• To take payment and manage your subscription: the Stripe identifiers, plan and status. Performing our contract with you.
• To improve TRNCH: the reason you give if you cancel. Our legitimate interest in knowing why people leave.
• To enforce plan limits and stop abuse: check and download records, session IP addresses. Our legitimate interest in a service that is not resold, shared or automated against.
• To keep the service working and secure: server logs, error reports. Our legitimate interest in a service that stays up and is not attacked.
• To see which pages are used, how fast they load and where people stop on the way to a plan: Cloudflare Web Analytics’ counts (below) and the step record (under cookies). Our legitimate interest in knowing what works on our own site.
• To measure our ads and show them to people: the Meta pixel, what our server sends Meta and the ad tags (under cookies). Our legitimate interest in advertising TRNCH; you can turn it off.
• To answer you: what you send us when you ask for help. Performing our contract, or our legitimate interest in replying.
• To meet legal duties: invoices and tax records, and the record of what you agreed to at checkout, including credit packs you bought. Compliance with a legal obligation.
• To show what you agreed to: the record of your agreement when you signed up. Our legitimate interest in being able to prove which terms applied if there is ever a dispute.
• To run the affiliate program: deciding on an application, looking at the public accounts it names and writing back: steps you asked us to take before a contract, and our legitimate interest in choosing who promotes us. An affiliate’s link, referrals, commission, posts and payouts: performing our contract with the affiliate. Recording which affiliate an account came through: our legitimate interest in paying affiliates correctly and stopping referral fraud. An affiliate’s tax form and taxpayer number: compliance with a legal obligation, and used for nothing else.

The emails we send. There is no mailing list for accounts and no newsletter. TRNCH sends account emails, to the address on your account: a link to confirm your address when you sign up, a welcome once it is confirmed, a link to confirm a new address and a notice to the old one when you change it, a confirmation of your plan’s terms and how to cancel when you start a plan, a receipt when you buy a credit pack, a reminder about 30 days before a yearly plan renews, a password reset link when you ask for one, a notice each time a renewal payment is tried and fails, a notice when a plan with monthly limits has used 80% of the month’s validations, review checks or store builds (at most one a month for each, with a link that stops them), if you switch it on, a daily email about your ads on days with something to do (with a link that stops it), and notice of a price increase before it applies to you. If you apply to be an affiliate, we write to you about your application, and if you are one, about the program. They are sent to carry out your purchase or our agreement and to keep your account working. Stripe, which takes the payments, may also email you about a charge, such as a receipt or a payment that failed. If we need to reach you personally (about your account, something you asked us, or a security problem), we write to the address on your account.

One marketing email. If you make an account and don’t start a plan, we may send you one email, once, reminding you that the free trial is there, which may carry an offer. It says it is marketing, carries our postal address and has an unsubscribe link that works with one click; unsubscribing stops every email like it and never the account emails above. We send it because you made an account with us (our legitimate interest in telling you about the plan you were looking at), and we keep a record that it was sent and whether you unsubscribed, with your account, deleted when it is. If we ever start sending any other kind of email automatically, this section changes before the first one goes out.

Almost everything inside TRNCH is information about products, shops and public videos on TikTok Shop (and, when someone runs a check, about adverts in Meta’s public ad library and listings and reviews on Amazon), read from pages anyone can open without signing in. That is business information, not personal information about our customers, and it is kept separately from your account.

Some of it names people or comes from them: a public shop name, a public creator handle, a public video and its public view count, an advertiser’s name, and the words of public reviews and comments. If you are a seller, a creator, an advertiser or the writer of a review or comment, and you want to know what we hold about your listing, your clip, your advert or your words, or you want it taken down, write to [email protected] with the link and we will answer. Copyright complaints have their own route on the Copyright page.

The Suppliers page lists sourcing and fulfilment companies: each one’s name, website and what it says it does, and for some a contact person’s name and business phone or WhatsApp number. They come from our own dealings with these companies and from their own websites, and we list them so our customers can reach them, which is our legitimate interest and, we believe, theirs. If you are one of them and want your details changed or taken off, write to [email protected] and we will do it within 30 days.

Only the companies that make the service run, and only what each of them needs.

• Stripe: payments and subscriptions. Stripe receives your name, email and payment details directly and is an independent controller of them. It may also email you about a charge. If an ad brought you and advertising is on, we also put that ad’s tags (the source, the campaign, the video and Meta’s click ID) on your Stripe customer record, so we can tell which ad led to a payment. The reason you give if you cancel is kept there too. stripe.com/privacy
• Resend: delivers the account emails described above. It receives your email address and each message we send you. resend.com/legal/privacy-policy
• Hosting, all in the United States. The site runs on a server we rent from DigitalOcean in New York; the videos people have downloaded are kept there. Our database (accounts, sessions, subscriptions, credits, saved products and the other records described above) is kept by Supabase, on Amazon Web Services in the eastern United States. The store builder’s files are kept on our server. Video covers, ad pictures and an encrypted copy of our nightly backup are kept in Cloudflare’s R2 storage, and every request to the site passes through Cloudflare’s worldwide network, usually at a data center near you, on its way to our server, so Cloudflare sees your IP address and the address of the page you asked for; Cloudflare also counts page visits for us (Web Analytics, under cookies). When you press to sign up, to reset a password or to send a confirmation link, Cloudflare Turnstile checks that you are a person: its script loads from Cloudflare, reads your IP address and details of your browser and device, and tells us only whether you passed. Each of them handles the data only to provide its service to us. Backup copies of our records stay in North America: in the United States, with these services or on computers we control, and the encrypted copy in Cloudflare’s eastern North America storage region.
• Meta: if you connect Meta in the ads manager, Meta tells us who you are and which ad accounts, Pages and pixels you chose, and we send it the campaigns, ads, videos, pictures and changes you ask for (see above). Meta is an independent controller of your Facebook and ad account data, under your agreement with Meta. facebook.com/privacy/policy
• Shopify: if you connect a Shopify store, Shopify tells us which store it is and gives the app its keys, and we send your store the product, photos, policies and shipping rates you put on it (see above). Shopify knows you installed the app. Your store’s own data is governed by your agreement with Shopify. shopify.com/legal/privacy
• Google sign-in: if you choose to sign in with Google, Google tells us who you are (see above) and knows that you used it to sign in to TRNCH. policies.google.com/privacy
• Google: a product page’s search-interest chart is drawn from Google Trends figures that our server asks Google for (or, when Google doesn’t answer, that Oxylabs asks for us). The phrase is sent; nothing about you is, and your browser does not contact Google for it.
• The data services that run searches for us: when you run a check, the search phrase or the product’s public link is sent to the services that read Meta’s ad library, Amazon and public reviews and comments for us: ScrapeCreators (Meta’s ad library, TikTok Shop reviews and video comments), and SerpApi, Oxylabs or Traject Data’s Rainforest API (Amazon listings and reviews). Nothing about you is.
• Google (Gemini) and Anthropic (Claude), the AI services: when the store builder writes words for a photo or a store’s words, it sends the product’s photograph and details and the choices you make to Google’s Gemini; a store’s words may be written by Anthropic’s Claude instead. When you run the review checker on a product, the public reviews and comments we read about it are sent to Gemini to write it. Your account details are sent to neither, and each processes what it receives under its terms for its paid API.
• Other companies’ servers, in your browser: product photographs load from TikTok’s image servers (video covers and Meta ad pictures are copies we serve ourselves); if you signed in with Google, your profile picture loads from Google’s; on a product page, Meta ad videos load from Meta’s servers, Amazon listing photos from Amazon’s, and small logos from Google’s logo service; a store preview loads its typefaces from Google Fonts or Shopify. Each sees your IP address and may set or read its own cookies. The cookie notice lists them. Clip playback is proxied through us, so your browser does not talk to TikTok for it.
• If you apply to be an affiliate, or are one: your application is kept with our records and emailed, through Resend, to our team’s inbox, which Google hosts. The payout service named in your offer receives what it needs to pay you, and the payments we make you are reported to the IRS on the tax form the law requires.
• Our accountant and our lawyers, bound to confidence, where they need it.
• A court, a regulator or the police, where the law makes us. We will tell you unless we are forbidden to.
• A buyer, if the business is ever sold or merged. This policy follows the data, and you would be told first.

Meta also gets what the pixel and our server send it for advertising (under cookies), for visitors in the United States who have not turned it off. Meta uses it under its own terms and policy, for its own purposes too. Nobody else. We do not hand your data to data brokers or to any other advertising network.

A cookie keeps you signed in, a second lives for a few minutes while you sign in with Google, a third remembers metric units if you choose them, a fourth remembers which affiliate’s link brought you, if one did, and a fifth keeps a store preview’s offer deadline if your browser blocks local storage (the cookie notice lists them all). In the United States, the ad cookies below too. A few small values in your own browser remember your settings: your theme, contrast, motion and units, the feed filter rail, your feed and email choices in Settings, the feed and the place on a page you were on, your store builder choices, a store preview’s basket, the suppliers you starred. Every page also runs Cloudflare’s Web Analytics script, which sets no cookie and stores nothing in your browser: when a page loads, it sends Cloudflare the page’s address (without anything after a “?”), the site that sent you, how long the page took to load, and your browser, operating system, type of device and country, which Cloudflare works out from your IP address. We see only totals, Cloudflare keeps the details for 7 days and the totals for about six months, and it is not used to follow you from site to site. Every one of them is listed, with what it does and how long it lasts, in the cookie and storage notice.

The Meta pixel and ad tags

On our home, features, how-it-works, pricing and sign-up pages, visitors in the United States load Meta’s pixel, a small script from Meta. It tells Meta the page you opened, that you made an account or started a checkout, your IP address and browser, and sets two cookies (_fbp, _fbc). Meta may also read its own cookies if you use Facebook or Instagram. Meta and other third parties can use cookies and similar tools to collect information from this and other sites, and use it to measure ads and show you ads elsewhere. The pixel itself sends no name or email address. It never runs on sign-in, password, settings or app pages, or for visitors outside the United States.

For the same visitors, if you make an account, our server also tells Meta directly: that you made it, that a free trial started, and each payment that goes through and its amount, renewals and credit packs included. With that it sends a scrambled (hashed) copy of your email address and of our ID for your account, your IP address and browser, the Meta cookies and click ID, and which ad video brought you. Once we have deleted the IP address, browser, Meta cookies and click ID (see how long we keep it), later payments go with the rest. Meta can match a hashed email to a Facebook or Instagram account, so hashing does not make it anonymous. If you sign up with Google, your email is left out. We send your name to no one for this, and nothing about what you do in the tool.

The same visitors also get our own cookie, trnch_visit: a random code and the furthest step it reached on the way to a plan (the site, pricing, the sign-up form, checking your email, confirming it, Stripe’s checkout). We record that step and when, whether you came from Instagram, Facebook or neither, and whether you are on a phone or a computer, to see where people stop. We keep no IP address, browser, email address or list of pages with it, and it goes to no one else. If you make an account in that browser, the record joins your account. Turn off ad tracking removes the cookie and stops new steps; signed in, it deletes the record too.

The same visitors also get our own cookie, trnch_src, which keeps the ad tags in the link that brought you (such as the campaign, the video and Meta’s click ID), so we can tell which ad worked. If you make an account it is saved with it. You can opt out of interest-based ads at optout.aboutads.info, and turn all of this off here under your choices.

Tracking across websites, and Do Not Track

Apart from the pixel above, we do not follow you across other websites. The other companies whose servers load in your browser while you use TRNCH (TikTok, Meta, Amazon, Google and Shopify, listed under who else sees it) may set or read their own cookies as they would on their own sites, and so may collect information about your activity over time and across websites under their own policies. Do Not Track has no agreed meaning and changes nothing here. Global Privacy Control does: see your choices.

• Account, saved products, saved filters and your time zone: while your account is open. Delete account in Settings › Your data deletes them at once; a request by email, within 30 days of it. Copies in our backups are gone within 45 days.
• Sessions: a session ends 30 days after you last used TRNCH, when you sign out, or when you sign in somewhere else. Its record (the IP address and browser) goes with the next sign-in or with the account.
• Ad cookies and tags: _fbp, _fbc, trnch_src and trnch_visit 90 days on your device. The record of the furthest step: 90 days after its last step, or, once it has joined an account, until the account is deleted or you turn ad tracking off. With an account: the IP address, browser, Meta cookies and click ID of the sign-up until your first payment or 90 days after sign-up, whichever comes first; the campaign and video tags while the account is open. All of it goes with the account, except the copy of the ad tags on your Stripe customer record, click ID included, which stays with that record. What Meta receives, Meta keeps under its own policy.
• Check and download records: while your account is open, because plan limits are counted from them. They are deleted with the account.
• The cost of each paid check: which product and words it ran with, the provider that answered, what it cost and the account’s internal number (not your name or email): at least three years, even when the account is closed, because our spending limits and costs are counted from it.
• Downloaded video files: the copy we make of a clip is kept on our server, filed under the clip, not under you, so the next person who asks for the same clip gets the same file. We delete it 90 days after anyone last asked for it; a later request fetches it from TikTok again. It goes sooner if the clip’s owner asks us to remove it (see the Copyright page). The record that you asked for it lives with your other usage records above.
• Invoices, receipts and tax records: seven years, because tax law requires it. These sit mostly in Stripe.
• The reason you give if you cancel: on your subscription at Stripe for as long as Stripe keeps that record, unless you press Keep on a paid plan before it ends.
• Sign-up agreement record: while your account is open and for at least three years after it closes, because it is the proof of what you agreed to.
• Checkout records: at least three years, or one year after the subscription ends if that is later, even when the account is closed, because they are the proof of what was agreed.
• Credit and store-build records (credits added and used, packs bought, store builds used): at least three years, even when the account is closed: they are the proof of what was bought and agreed, and while the account is open your balance and your remaining store builds are counted from them.
• Which early access code an account used: while the account is open. When the account is deleted, the account and its email are taken off the record; only that one of the code’s places was used, and when, stays.
• Affiliate records: an application we turn down or don’t take further, our notes on it and the record of its agreement, 12 months from when it was sent. For an affiliate we take on: the agreement record, referrals, commissions, payouts, posts and the tax form, seven years after the last payment to them, because tax law requires it. Which affiliate an account came through: while the account is open, and with those commission records after.
• Store builder confirmations, reminders and your answers to them, video upload confirmations and downloads: at least three years, even when the store or the account is deleted, because they are the proof of what each store’s owner confirmed and was shown.
• A Meta connection: the key, the connection and the record of changes you made: until you press Disconnect, remove TRNCH in your Facebook settings or delete your account, then deleted at once; a request by email, within 30 days. What we read from Meta to show you is held only in our server’s memory, for up to ten minutes (an hour for lifetime totals).
• A connected Shopify store: until you disconnect it in the builder, uninstall the app in Shopify, or delete your account; the store’s keys and the record of the connection go then. When Shopify asks us to erase a store’s or a customer’s data, we do it within 30 days; when it asks what we hold about one of your customers, we answer the store within 30 days (today: nothing). Sales figures, if we add them, are read from Shopify when you look, the last 60 days at most, and not kept after.
• Server logs: 90 days.
• What you send us asking for help: 24 months.

Wherever you live in the United States, you can ask us to do the things below. Several states’ consumer privacy laws give these rights (California’s, Virginia’s, Colorado’s, Connecticut’s, Texas’s, Oregon’s, New Jersey’s, Minnesota’s, Maryland’s and others), and we answer every such request in the same way, whether or not a particular state’s law applies to us:

• tell you what personal information we hold about you, where it came from and who has had it;
• give you a copy in a portable form;
• correct anything that is wrong;
• delete it;
• stop selling or sharing it, and limit the use of sensitive information;
• and not be treated worse for asking.

In the categories California law uses

In the last twelve months we have collected:

• Identifiers: name, email address, account and Stripe identifiers, IP address, and a Google account identifier if you sign in with Google;
• Customer records and commercial information: your plan, its status and price, credit packs bought, your credit history, and the reason you give if you cancel;
• Internet or other electronic network activity: sessions, browser user-agent, checks run, videos downloaded, products and filters saved, server logs, the page visits Cloudflare Web Analytics counts, and the pixel’s page and event data and ad tags, and the furthest step a browser reached on the way to a plan;
• Professional or business information: the business details you put on a store, and, for an affiliate or someone applying to be one, the accounts, follower range and niche they give us and what they tell us about their work;
• Audio or visual information: the photos and videos you upload to a store;
• Sensitive personal information: your account log-in with its password, and, for an affiliate, a taxpayer identification number.

They come from you, from your browser, from Google if you sign in with it, and from Stripe about your payments. Identifiers (IP address, cookie IDs, a hashed email address and account ID), commercial information (a trial started, payments and their amounts) and internet activity from the pixel are shared with Meta for advertising, which is the only sharing below. We use them for the purposes under why we use it, and we disclose them, for those business purposes only, to the service providers named under who else sees it: our hosting (DigitalOcean, Supabase, Cloudflare), payments (Stripe), email (Resend), Google (sign-in, and Google Workspace, which hosts our support and affiliate inbox), the AI services (Google’s Gemini and Anthropic’s Claude, which get no account details), Shopify and Meta if you connect them, our accountant and lawyers, a buyer if the business is sold, and, for an affiliate, the payout service and the IRS. We keep each for the time set out under how long we keep it. We collect no precise location, no biometric data and no inferences or profiles about you.

Your privacy choices: Do Not Sell or Share My Personal Information

We take no money for personal information. But what the pixel and our server send Meta counts as “sharing” for cross-context behavioural advertising under California’s law, may count as a “sale”, and counts as targeted advertising under other states’ laws. The categories are identifiers, commercial information and internet activity, as above, and Meta is the only party. You can turn it off here, without an account:

It stops the pixel and removes the ad cookies on this browser, and we remember your choice for a year. If you are signed in, or were opted out when you signed up, our server sends Meta nothing about your account either. A Global Privacy Control signal from your browser does the same, by itself, each time. Telling us through the same route as the requests below works too, as does a request not to sell under Nevada law (NRS 603A.345). We do not treat you worse for choosing this.

The only sensitive personal information we hold is your account log-in with its password, and, for an affiliate, a taxpayer identification number. We do not use or disclose either for any purpose beyond running the service and, for the number, reporting payments as tax law requires, and we do not knowingly sell or share the personal information of anyone under sixteen.

How to ask

Two of them are buttons in Settings › Your data: Download gives you a copy, as one file, of everything your account holds in our database, and Delete account deletes the account (what stays is under how long we keep it). For anything else, including a copy of what is kept apart from the account (your sign-up, checkout and store builder records, server logs, what you sent us), write to [email protected] from the address on your account and say which of the things above you want. We do these by hand, and we answer within 45 days. A hard request can take one further 45 days, and we will tell you if it does. We will ask you to confirm control of the account email before acting; that is the whole of our verification. An authorised agent may act for you with written permission we can check. If we turn a request down you can appeal by replying to our answer with the word “appeal”, and we will respond within 45 days with reasons.

The same list, plus the right to object to processing we do on the basis of legitimate interests, the right to ask us to restrict processing while a dispute is open, and the right to withdraw consent at any time where consent is what we relied on. The route is the same: write to [email protected].

We make no decision about you based only on automated processing that has legal or similarly significant effects, and we do not profile you. The checks that refuse a free trial (a card or email address that has had one, a prepaid card, a throwaway email address, an internet address that has just started many) run by themselves; if you think one got it wrong, write to [email protected] and a person will look.

Our servers are in the United States (an encrypted backup copy is in Cloudflare’s eastern North America region), and so are the providers named above, so using TRNCH from Europe means you send your data to the United States. We protect it there as this policy describes.

You can complain to your own supervisory authority: in the UK the Information Commissioner’s Office, in the EU the authority for the country you live in. We would rather you told us first.

TRNCH is a business tool for adults and is not directed to children. You must be eighteen to hold an account or to join the affiliate program, and we do not knowingly collect personal information from anyone under eighteen, nor from a child under thirteen in any way the Children’s Online Privacy Protection Act covers. If we learn that an account belongs to someone under eighteen, we close it and delete its data. If you believe a child has given us information, write to [email protected] and we will.

Passwords are stored as one-way hashes. The site is served over HTTPS. Session tokens are random, expiring and set as HTTP-only cookies your scripts cannot read. Access to the database is limited to the people who run the service. Payment details never touch our systems.

No system is perfect and we will not pretend otherwise. If personal data of yours is ever exposed we will tell you, by writing to you at the address on your account and by a notice on this site, and we will tell the relevant regulator, as soon as we can and within the deadline of every law that applies (for example 72 hours to a regulator in the EU or the UK, 30 days in Colorado, Florida and Washington, and 45 days in Arizona, A.R.S. § 18-552), with what happened and what to do.

The version number at the top of this page and the date in the banner change whenever the document does. A change that describes what we do takes effect when it is posted; it never gives us a right over your data that this policy did not, which needs your agreement (below). If a change materially affects you, we also email the address on your account about it. No change lets us use data we already hold in a materially different way from what this policy said when we collected it, unless you agree.

Privacy questions and requests, and everything else: [email protected]. For a formal data request by post: TRNCH LLC, an Arizona limited liability company, 10115 E Bell Rd, Ste 107 PMB 821, Scottsdale, AZ 85260-2189, USA. By phone: 480-378-9708.