Privacy notice
What we collect, why we need it, who receives it and your choices.
These documents describe the proposed launch terms. Paid creator products are not yet available. The final terms and working support channel will be published before live sales begin.
On this page
- 1. Who is responsible?
- 2. Information you give us
- 3. Purposes and legal bases
- 4. Visits and device information
- 5. Who can receive information?
- 6. International processing
- 7. Retention and deletion
- 8. Your rights and requests
- 9. Children and sensitive information
- 10. Contact and changes
- 11. Connected accounts, Google and YouTube data, and how we protect it
1. Who is responsible?
FLOWTC LTD is responsible for TN.TC account administration, platform security, service communications and its own transaction records. A creator or business receiving a quote request, customer order or file submission may be separately responsible for how they use that information. Their identity and any additional notice should appear on their page.
Hosting customer content on a business’s instructions can involve a processor role. That role and any data-processing terms must reflect the actual service. This notice does not give creators permission to sell contacts or use them for unrelated marketing.
2. Information you give us
We receive account names, email addresses, profile details, language, time zone and theme preferences; password hashes or sign-in-provider identifiers; the record of your acceptance of the terms (version, language, channel and time); uploaded files and their metadata; published links, pages and menus; messages and attachments; quote requests and form responses; and support or moderation submissions. If you turn on mobile notifications, the device notification token and your notification preferences are stored. Optional profile content is under your control.
When payments are enabled, order, subscription, refund and provider reference data and the payment country you choose in settings are needed; a booking also records the chosen time slot, and a physical order records the delivery address and shipment tracking, visible only to the buyer and the seller. Card entry and payment verification are handled by the payment provider or app store; do not put card numbers into messages or uploaded files. Payout providers may require identity and business information before allowing a seller to receive money.
3. Purposes and legal bases
We use account and service data to provide requested features and take steps towards a contract, including routing messages, delivering files and responding to quote requests. We process security and abuse information for legitimate interests in protecting users and operating a reliable service, subject to your rights. Records required by applicable accounting, tax or legal rules are processed for those obligations.
Optional marketing and consent-based tracking require a separate choice where applicable. Refusing marketing does not prevent use of core features. We will identify a new purpose before using information in a materially different way. We do not treat acceptance of service terms as blanket consent to all processing.
The safety centre may review resource and file access events, upload records, communicating accounts and payment patterns. Phone-like text in creator conversations, repeated Bell purchases and unusual file access may produce review signals. These signals are not findings of misconduct or crime and do not automatically close accounts. The centre is restricted to the designated platform operator. Private message or file inspection requires a recorded reason and an access log, for necessary security and abuse review. Temporary suspensions, resource blocks and access limits are logged. You may request review or correction through [email protected].
4. Visits and device information
The platform receives technical request information to deliver and protect the service. Its link statistics record coarse device, browser and operating-system categories, country information where supplied by infrastructure, referring domain, campaign parameters and visit time. The statistics tables do not store a raw IP address or a cross-site tracking identifier. Infrastructure security logs may separately contain IP addresses.
Resource owners see statistics for their own links and pages. Do not put personal information into campaign tags or public URLs. Cookie-free measurement still requires a lawful purpose and transparent handling; the Cookies Notice explains browser storage separately.
6. International processing
The company is based in the United Kingdom. Users, recipients and providers may be in other countries, so your choices and the configured infrastructure can involve international transfers. Where required, transfers need an applicable adequacy decision, contractual safeguards or another lawful mechanism.
The final launch notice will identify the operating locations and applicable safeguards after provider contracts and deployment regions are verified. We do not currently promise UK-only or Türkiye-only storage. Publicly publishing content can make it accessible worldwide.
7. Retention and deletion
We retain data for the feature you use and for proportionate security, dispute and legal needs. When you close your account, sessions, device and notification registrations, two-step verification secrets and sign-in links are deleted; your name is removed and your email address is replaced by an irreversible placeholder; the text and attachment reference of chat messages you wrote are deleted; your files and their image previews are queued for storage cleanup; delivery addresses are removed and your payment country is cleared. Order and earnings records keep amounts, currency, status and provider references for accounting and disputes, with personal free text removed. The record of your acceptance of the terms is kept as evidence. Copies in backups disappear when the backup retention period ends.
The export in account settings delivers the categories related to your account in one JSON file, including profile, session metadata, workspaces, resources, file metadata, submissions, messages you wrote, orders, bookings, shipments, creator memberships, earnings, contacts, notifications, devices and acceptance records. Security secrets such as passwords, keys and tokens, and the files themselves, are not included; you can download files separately. Image previews are made with location and camera metadata removed. Visit statistics are retained while the account and related resources remain in the service to provide historical reports. Downgrading or subscription expiry does not delete history; your plan limits the accessible date range. Unconfirmed form sign-up addresses are deleted 30 days after their confirmation window, and malware files 30 days after quarantine for security review. Exact retention periods for accounting records and backups will be set before launch.
If a recipient independently saved a file using “Add to my Box”, deleting your original does not delete their copy. The recipient removes their own copy; unlawful content may separately be reported.
8. Your rights and requests
Depending on applicable law, you may request access, correction, erasure, restriction or portability, object to relevant processing, and withdraw consent without affecting earlier lawful processing. We may need proportionate proof that a request concerns your data. Some records must be retained where law requires it; we will explain an applicable exception.
You may complain to the UK Information Commissioner’s Office or the competent authority where you live. For Türkiye, applicable rights under Article 11 of Law No. 6698 include learning about processing, seeking correction or lawful deletion, and objecting to a result arising exclusively from automated analysis. This notice is information, not a request to waive rights.
9. Children and sensitive information
Accounts are for people aged 18 or over. Registration and acceptance of the current terms require an adult declaration; we do not routinely collect birth dates or identity documents for this purpose. We do not offer child accounts, student submission services or paid services directed at children. Public pages can still be visited by children; an account age limit does not technically prevent this access.
If you believe a child’s information has been processed without authority, report the URL and the minimum necessary details to [email protected]. We may restrict access during review; a confirmed underage account is closed and related personal data removed unless retention is legally required. Do not attach a child’s identity document; if more information is needed, we will specify a secure channel.
10. Contact and changes
Use the operator details below for privacy correspondence. The planned email channel will be activated before public launch. We will date material updates and provide additional notice when required. Material changes do not turn previously declined marketing into consent.
11. Connected accounts, Google and YouTube data, and how we protect it
When you connect a social account (YouTube, Instagram, Facebook, Threads or TikTok), you choose to do so and approve it on that platform's own consent screen. For YouTube, TN.TC requests only two Google scopes: youtube.upload, to publish a video you choose to the channel you connected, and youtube.readonly, to show your channel name, your recent videos and their public comments inside your TN.TC panel. We do not request write access to comments, playlists or any other Google data.
What we keep: the channel ID and name, the OAuth refresh token, and, for videos you publish through TN.TC, the video ID and its publishing status. Your video files stay in your own TN.TC Box; when you publish, the file is streamed directly to YouTube's resumable upload and is not copied anywhere else. Comments read from YouTube are stored only so you can see them in your inbox and are removed when you disconnect the channel.
How we protect sensitive data: (a) OAuth access and refresh tokens are encrypted at rest with a server-held key, are never sent to your browser or apps, and are never written to logs; (b) all traffic between you, TN.TC and Google uses HTTPS (TLS 1.2 or later), and the site sends HSTS; (c) access to production systems is limited to authorised staff who use two-factor authentication, and administrative actions are recorded in an audit log; (d) uploaded files are checked by a malware scanner on our own servers before they are published; (e) data of different workspaces is separated, and every request is checked against the signed-in account, its workspace and its permissions; (f) backups, where kept, are stored with the same access restrictions.
Limited use: TN.TC's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features you see in TN.TC. We do not sell it, do not use it for advertising, do not transfer it to others except as needed to provide the feature or as required by law, do not let humans read it unless you ask us for support, it is needed for security or it is required by law, and do not use it to train AI or machine-learning models.
Your control: you can disconnect YouTube at any time in Social > Accounts; we then delete the stored tokens and comments for that channel. You can also revoke TN.TC's access at https://myaccount.google.com/permissions. Deleting your TN.TC account deletes all connected-account data. Questions: [email protected].