Privacy Policy
TLNT Connect Privacy Policy
Our collection, use, disclosure, retention, security, international-transfer, and privacy-rights practices.
Last updated September 25, 2026
Scope And Company Information
Tlnt Connect LLC, operating as TLNT Connect ("TLNT Connect," "we," "us," or "our"), is organized in Delaware. Our business mailing address is 611 South Dupont Highway, Dover, DE 19901. This policy applies to tlntconnect.com, the TLNT Connect application, workspaces, portals, public share links, provider integrations, and related support.
For account, security, product-improvement, marketing, and direct customer-relationship data, TLNT Connect generally acts as a controller or business. For creator, campaign, mailbox, brand-contact, and similar Customer Data submitted under an agency's instructions, TLNT Connect generally acts as a processor or service provider and the agency remains responsible for its own notices and lawful instructions.
Notice at Collection
At or before collection, we collect the categories described below for account administration, workspace and portal operation, creator and campaign management, communications, provider connections, security, support, legal compliance, and—when enabled—billing and accounting. We do not sell personal information, share it for cross-context behavioral advertising, or process it for targeted advertising. We do not use sensitive personal information to infer characteristics about individuals.
Providing account and workspace information is necessary to create and administer an account. Provider permissions, optional profile fields, AI prompts, and integration data are optional, but the related feature may not work without them.
Information We Collect
- Identifiers and account data: name, email, postal addresses, including a creator's mailing address and gift shipping name and address (see Shopify Merchant Data), account and workspace identifiers, agency or brand name, role, invitations, authentication and legal-acceptance records, and support communications.
- Agency and commercial operations: creator rosters, public social profiles, contacts, rates, notes, campaigns, deliverables, files, tasks, approvals, brand contacts, messages, reports, contracts, invoices, payout records, and accounting configuration, and, for a brand that connects Shopify, the store's order, line-item, payment-transaction, refund, discount-code, product-catalog, and gift-order records, and, for a brand that pays through Shopify, its Shopify app subscription and usage-charge records (see Shopify Merchant Data).
- Internet and technical activity: IP-derived security signals, device/browser and user-agent data, authentication cookies, local-storage preferences, request and audit logs, webhook and provider-sync events, errors, and feature activity.
- Professional, demographic, and inference data: creator category, audience location/age/gender aggregates, performance metrics, niche, engagement, and suitability or match signals supplied by customers, public sources, or data providers.
- Communications and connected-provider data: Gmail content and metadata, social-platform analytics, and OAuth identifiers and token metadata when an authorized user enables those features.
- AI feature data: prompts, instructions, selected workspace context, tool results, responses, approvals, and safety/usage metadata processed to provide Atlas AI and related assistance.
Sources of Personal Information
We collect information directly from users; from the agency, brand, creator, or other organization that supplies or authorizes it; from connected services such as Clerk, Google/Nylas, Shopify (for stores a brand connects), and payment providers; from publicly available social profiles and websites; and from creator-data providers such as Modash and ScrapeCreators.
If we receive information about you indirectly, the customer that supplied it is responsible for having authority to do so. Where GDPR Article 14 or similar law requires TLNT Connect to provide an indirect-collection notice, this policy describes the categories, sources, purposes, recipients, and rights that apply.
How And Why We Use Information
- Perform a contract and provide requested features, accounts, workspaces, portals, collaboration, provider connections, support, and communications.
- Pursue legitimate interests in securing, debugging, measuring, and improving the service; preventing fraud and abuse; maintaining auditability; and operating the business, balanced against individual rights.
- Comply with legal, tax, accounting, security, sanctions, and law-enforcement obligations and establish or defend legal claims.
- Use consent where required for optional provider access, sensitive information, marketing, or other processing that cannot rely on another legal basis. Consent may be withdrawn prospectively.
Legal Bases For EEA And UK Processing
Where the GDPR or UK GDPR applies, our Legal Bases are performance of a contract, legitimate interests described above, compliance with legal obligations, and consent where required. We do not rely on consent when it is not freely given or where another basis is more appropriate.
Connected Providers, Google, And AI
For Gmail features, Google user data may include mailbox identifiers, messages, body text, snippets, headers, participants, provider message and thread identifiers, attachment metadata, raw provider metadata, send state, and provider events. Requested Gmail permissions may include gmail.modify and gmail.send. YouTube connections may request youtube.readonly and yt-analytics.readonly. Our use and transfer of Google user data is limited to user-requested features consistent with the Google API Services User Data Policy and Google Limited Use requirements.
Atlas AI may send prompts, selected workspace context, and tool results to OpenAI or another disclosed AI subprocessor to generate responses. We do not permit an AI provider to use Customer Data to train generalized models unless a customer expressly opts into a separately disclosed program. AI output can be incomplete or inaccurate and should be reviewed before consequential use.
Connected Social Accounts
A creator may authorize TLNT Connect to read data from the creator's Instagram, TikTok, or YouTube account. Instagram data may include profile identifiers and profile fields, follower and media counts, recent-media captions, links, thumbnails, timestamps, likes and comments, media and account insights such as views, reach, interactions, shares, saves, replies, follows, and profile-link taps, and aggregate follower demographics when Meta makes those reports available. TikTok data may include account identifiers, profile, username, and avatar fields, account type, follower, following, like, and video counts, authorized recent-video metadata and engagement statistics such as views, likes, comments, and shares, per-video performance insights such as reach, average watch time, and completion rate, account-level statistics reported by TikTok such as engagement rate, average views, likes, comments, and shares per video, follower growth rate, engaged audience, and unique video views, and aggregate follower demographics such as age ranges, gender, countries, and cities when TikTok makes those reports available. YouTube data may include channel identity and profile fields, subscriber, channel-view, and video counts, recent-video titles, links, thumbnails, publication times, views, likes, and comments, and YouTube Analytics reports such as views, likes, comments, shares, watch time, average view duration, subscriber gains and losses, and aggregate audience age, gender, and country percentages when Google makes those reports available.
We use connected-social data to verify the creator's platform identity; create, populate, and refresh the creator's TLNT Connect profile; calculate and display performance and engagement metrics; and provide creator-authorized analytics to the creator and the creator's authorized agency workspace. Authorized workspace users may include selected metrics in customer-directed portals, media kits, reports, or tokenized share links. The current connected-social feature uses read-only permissions and does not publish, edit, or delete social-platform content on the creator's behalf.
We store provider account and channel identifiers, granted scopes and expiration metadata, synchronized profile and performance metrics, and selected recent-content metadata used by the visible product features. We store OAuth access and refresh tokens, where the provider issues them, in encrypted form on the server and do not expose them to agency users, creators, public links, or client-side application code. We do not collect a creator's Instagram, TikTok, YouTube, or Google password.
Disconnecting a social account clears its stored OAuth access and refresh tokens from the active connection and stops future first-party API synchronization. Disconnecting a TikTok or YouTube account also asks that platform to revoke TLNT Connect's access. A creator may also revoke TLNT Connect in the connected platform's account settings, which is how Instagram access is revoked at Instagram. Previously synchronized social-account data may remain in the workspace as historical profile, reporting, audit, or customer-directed share data after disconnect. A creator may request deletion of that data through the Privacy Request Center or by emailing privacy@tlntconnect.com, subject to documented legal-hold, security, and backup exceptions.
We do not sell connected-social data, use it for cross-context behavioral advertising or targeted advertising, or disclose it to data brokers. We disclose it only as described in this policy, including to the authorizing creator, authorized workspace users and customer-directed recipients, service providers that operate the requested feature, a connected service at the user's direction, or when required for security or law.
A creator may choose to work with more than one agency on TLNT Connect by accepting each agency's invitation. When a creator does so, the creator's portal profile basics (such as name, photo, date of birth, address, phone, location, and niche), connected social accounts and their synchronized metrics, and payout-account status are made available to each agency workspace the creator has accepted, so the creator does not have to repeat setup. When a creator accepts a brand's invitation, we do not copy the creator's date of birth, address, phone, or connected social accounts from other workspaces into that brand's workspace; of these profile basics, the brand receives only the creator's name, photo, location, and niche. Each agency's campaign, deal, message, and internal workspace data remains separate and is not shared with other agencies. A creator can review the agencies they work with in their portal, and access ends for an agency when the relationship is ended or the portal account is revoked.
Shopify Merchant Data
A brand can connect its Shopify store to TLNT Connect by installing our Shopify app, which asks Shopify for permission to read the store's products and orders, create discount codes, and create draft orders. From Shopify, we receive the store's Shopify identifier and domain, the access credentials Shopify issues to our app, and the product and variant catalog details we show the brand when it picks a program or gift product: each product's title, handle, and status, and each variant's title, price, options, availability, and inventory quantity.
For each store order we read, we receive the order, line-item, transaction, and refund identifiers; when the order was created, updated, or cancelled; whether it is a test order; its currency, totals, and payment status; the discount codes applied; each line item's product, variant, quantity, price, discount, and tax; and its payment transactions and refunds. From Shopify's summary of the visits that led to an order, we receive only the time of each visit and its UTM content value, which tells us whether the visit came from a TLNT Connect creator link. We do not request an order's customer record, and we do not collect the shopper's name, email address, phone number, billing or shipping address, IP address, or browser user agent from store orders.
We also receive the identifiers of new orders and refunds Shopify notifies us about, and the privacy requests Shopify forwards to us (customers/data_request, customers/redact, and shop/redact). Once a day, we check the status of each creator discount code we created in the store, so we can tell the brand when a code has been deleted or has stopped working. For each creator gift order, we receive its fulfillment status, shipping carrier, tracking number and tracking link, shipment and delivery dates, and the store's time zone.
When a brand uses our creator link and gift features, we also log clicks on the brand's creator short links and collect a creator's gift shipping name and address from the creator in the TLNT Connect creator portal.
If a brand installs our app from the Shopify App Store, we record that it did. If it pays for TLNT Connect through Shopify, we also receive from Shopify the status of the brand's app subscription (its plan, prices, trial and billing-cycle dates, usage charges, and any pending plan change) and billing events such as subscription changes, freezes, and uninstalls. We send Shopify a usage event, with the store, the time, and the number of credits, for the data credits the brand uses beyond its plan, so Shopify can bill the brand for them.
We use Shopify data to credit creators for the sales they drive through their links and discount codes, calculate their commission, show the brand's workspace its creator sales, link clicks, creator code status, and gift delivery status, send creator gifts from the brand's store, respond to the privacy requests Shopify forwards, and, for a brand that pays through Shopify, keep its TLNT Connect plan in step with its Shopify subscription and bill its usage. We change the brand's store in only two ways: we create a TLNT-prefixed discount code for each creator enrolled in the brand's program and deactivate it when that enrollment is retired, and we create a gift draft order and complete it into an order with a zero total. We use a store's data only for the brand workspace that connected it.
We store Shopify access credentials only in encrypted form on our servers. When Shopify notifies us of a new order or refund, we keep only the order or refund identifier and a fingerprint (hash) of the notification, and discard the rest of it. We store a creator's gift shipping address only in encrypted form (AES-256-GCM), record each time it is released for a gift order, and decrypt it on our servers only to create that order: a draft order in the brand's Shopify store for the selected product with a 100% discount, so the order total is zero. The brand sees the address in its own Shopify store as part of that order. TLNT Connect does not otherwise show it to the brand. We store each gift order's tracking details and delivery status and show them to the brand's workspace. We log a click only when a creator short link is a tracked link that sends the visitor to the brand's store, and we skip clicks from browsers that identify themselves as bots, crawlers, or link previews. The click log records the link, the time, a hash of the browser's user-agent string (pseudonymous data, never anonymous), and the domain of the website the visitor came from, if any. The click log does not record the visitor's IP address. We do not set a cookie for these clicks. For a privacy request that Shopify forwards, we store the customer details inside it in encrypted form: the Shopify customer and order identifiers, Shopify's identifier for a customer data request, and the shopper's email address or phone number only when Shopify does not supply a customer identifier.
We keep a store's order, refund, discount-code, and attribution records while our app is installed on that store. When a merchant uninstalls the app, Shopify notifies us; once we confirm with Shopify that the stored credentials no longer work, we clear them and stop reading the store's data. An uninstall notification record is deleted 30 days after its last activity.
Within 30 days of the uninstall, our automated redaction, run on the store erasure request (shop/redact) that Shopify sends 48 hours after the app is uninstalled, or on its own if that request has not arrived five days after we confirm the uninstall, deletes that store's order and refund notification records, its order and attribution records that carry no creator commission, its temporary app-install and sign-in records, the brand workspace's link-click records logged before the request, and any store credentials we still hold from that installation, clears the shipping address, Shopify order identifiers, and tracking details from its creator gift records, and pseudonymizes its creator commission records. The store's connection record, without credentials, stays only while a pseudonymized commission record needs it.
When Shopify forwards a customer erasure request (customers/redact), our automated redaction deletes or pseudonymizes the order and attribution records for the listed orders within 30 days, and clears the shipping address, Shopify order identifiers, and tracking details of a creator gift sent as one of those orders.
A pseudonymized commission record keeps the order's merchandise and refunded amounts, currency, commission terms and amount, and dates, the creator, store, and creator discount code, the date of the creator-link visit that led to the order, a keyed hash of the order identifier and a hash of the order data, used only to recognize the same order, or a changed version of it, if Shopify sends it again, but not the Shopify order or refund identifiers. Because someone who holds the original order data could match these records to it, we treat them as pseudonymized personal data. We do not attempt to re-identify the shoppers or orders they relate to.
We keep pseudonymized creator commission records for seven years after the end of the calendar year in which the latest of these happened: the order was paid, the commission became eligible, the record was last updated, or the commission was last adjusted. We do not record creator payout dates on these records, so a later payout does not extend this period. We keep them longer only while a tax audit, dispute, or legal hold requires it, and then delete them, along with the creator discount code records they rely on once no remaining commission record needs those. Creator payout records are not derived from store orders and are not deleted by this process; they follow the retention period for financial and accounting records in Retention And Deletion.
When Shopify forwards a customer data request (customers/data_request), our team reviews it within 30 days and provides the data we hold for the listed orders to the store owner, who responds to its customer, or declines the request. We delete the customer details stored with a privacy request when the request is closed, and delete the request record three years after it is closed.
A link-click record is deleted after 90 days. We delete a creator's gift shipping address 30 days after the gift order is fulfilled or delivered. If the gift's Shopify order is canceled, we delete it 30 days after the cancellation. In any event, we delete the address for a gift whose order has not been fulfilled 90 days after the gift was created, and sooner on the store's erasure request or a customer erasure request naming the order.
We keep our copy of a brand's current Shopify subscription status, the record that it installed our app from the Shopify App Store, and the usage events we send to Shopify as billing records, under the retention period for financial and accounting records in Retention And Deletion. The store erasure request and customer erasure requests do not remove them.
We do not sell Shopify data, use it for cross-context behavioral advertising or targeted advertising, or disclose it to data brokers. We disclose it only to the brand that connected the store and its authorized workspace users, to service providers that operate the requested feature, to the brand's own Shopify store when we create a creator discount code or a gift order, or when required for security or law. A merchant or shopper may contact privacy@tlntconnect.com about Shopify data.
For Shopify store data (orders, refunds, discount codes, product catalog details, visit attribution, link clicks, and gift order fulfillment and tracking), TLNT Connect acts on the brand's behalf and under its instructions as a processor (GDPR and UK GDPR) and service provider (CCPA). The brand is the controller or business for that data and is responsible for notice to its shoppers. TLNT Connect is an independent controller or business for (a) creator account and profile data, including the gift shipping address a creator gives us, which we disclose to the brand's Shopify store at the creator's direction so the brand can send the gift; (b) the creator commission records we derive from store orders, which we keep to calculate, pay, and report creator earnings, meet our tax and accounting obligations, and establish or defend legal claims, and the creator payout records for those earnings, which are not derived from store orders; and (c) brand users' account and billing data, including Shopify subscription and usage records, and data about visitors to our website.
How We Disclose Information
We disclose information to authorized workspace members and recipients of customer-directed portals or tokenized links; to subprocessors that provide hosting, database, authentication, email, provider connectivity, AI, payments, support, and security; to third-party services a user directs us to connect; and when required for legal process, safety, fraud prevention, financing, merger, or acquisition.
Our current named providers and their roles are maintained on the Subprocessors page. Providers must process information under applicable contractual restrictions, although a connected third-party service may act under its own privacy policy for data it receives directly.
Cookies, Local Storage, Do Not Track, And Global Privacy Control
We use authentication and security cookies and local or session storage for sign-in, routing, theme, sidebar, and workflow preferences. We also use first-party-directed product analytics (PostHog) to understand feature usage and error monitoring with session replay (Sentry) to diagnose problems; session replay is configured to mask sensitive content, and both providers process this data for us as subprocessors. We do not currently use third-party advertising cookies or cross-context behavioral advertising trackers.
If you follow a referral link from one of our affiliate partners, that link sets one additional first-party cookie on tlntconnect.com, named tlnt_ref_evidence. We set it only when the link is opened as an ordinary page visit. It holds a random, opaque identifier and an integrity signature; it does not contain your name, email address, account identifier, or the referring partner's identity, and scripts running in your browser cannot read it. It expires 30 days after the visit, and following a different partner's referral link replaces it. Its only purpose is referral credit: if an agency workspace is created from that browser within 30 days, we credit the referring partner, and we clear the cookie once that decision is recorded.
We do not use the referral cookie for advertising, cross-context behavioral advertising, or profiling, and we do not sell it or share it for advertising. A referring partner sees only a pseudonymous entry for a referral we credit to them, showing an opaque reference, the referral's stage, its dates, and the reward amount earned on that referral, which reflects the referred agency's payments to us up to a $500 cap. They never see the customer's name, email address, agency name, workspace contents, invoices, or card or bank details. The visit records behind a referral link contain no IP address and no raw user-agent string, and a visit record that is never linked to a referral is deleted after 90 days. You can delete this cookie at any time in your browser's cookie settings; without it, a referral is simply not credited.
Because there is no uniform industry response to browser Do Not Track signals, TLNT Connect does not respond to DNT. We do not currently sell or share personal information for behavioral advertising, so a Global Privacy Control signal does not change that processing. If those practices change, we will provide required controls and honor supported universal opt-out signals where law requires.
Authentication, hosting, connected-provider, and security vendors may collect request or device information while acting for us. Other parties do not have permission from TLNT Connect to track users across unrelated websites for their own advertising through our service.
Retention And Deletion
Our retention schedule uses the shortest period reasonably necessary for each purpose. Account and workspace data is retained while the account is active and for a limited wind-down period; mailbox and provider content is retained while the connection or feature requires it; security logs are retained for investigation and audit needs; financial, acceptance, and transaction records are retained for applicable legal and accounting periods; privacy-request evidence is retained to demonstrate compliance; and backups expire through normal rotation.
We consider account status, customer instructions, feature need, data sensitivity, contractual commitments, limitation periods, tax/accounting rules, security needs, backup cycles, and legal holds. When a period ends, information is deleted or de-identified. Legal holds and records needed to establish or defend claims override ordinary deletion until released.
Disconnecting a provider stops new API access after revocation where supported. Historical accounting references, audit events, and minimal security records may remain when necessary. When requested, we delete locally stored Gmail message content, including body text, snippets, headers, participants, provider message and thread identifiers, attachment metadata, raw provider metadata, queued provider events, and sync jobs unless a documented legal-hold or security exception applies.
Shopify store data follows the retention periods in the Shopify Merchant Data section: order and attribution records are kept while our app is installed and deleted or pseudonymized by automated redaction within 30 days of the uninstall or of a Shopify erasure request; a link-click record is deleted after 90 days; a creator's gift shipping address is deleted 30 days after the gift order is fulfilled or delivered, 30 days after its Shopify order is canceled, and in any event 90 days after the gift was created if its order has not been fulfilled; pseudonymized creator commission records are deleted seven years after the end of the calendar year of the latest of the order's payment, the commission's eligibility, the record's last update, and its last commission adjustment (creator payout dates are not recorded on these records); and Shopify subscription and usage records are kept as billing records for the period that applies to financial and accounting records.
State Privacy Rights
Depending on residence and legal applicability, individuals may request access, correction, deletion, portability, a list of third-party categories, or confirmation of processing, and may opt out of sale, targeted advertising, or qualifying profiling. We do not discriminate for exercising a privacy right.
Submit a request through our Privacy Request Center or email privacy@tlntconnect.com. We will verify the request proportionately, respond within the legally required period, and explain any denial. If we deny a request, the response will describe how to appeal. Appeals may be submitted through the same center by selecting Appeals.
An Authorized Agent may submit a request where law permits. We may require signed authorization, verification of the individual's identity, and direct confirmation unless a valid power of attorney applies.
EEA, UK, And International Rights
Where applicable, individuals may request access, rectification, erasure, restriction, portability, or objection; withdraw consent; and complain to the supervisory authority in their country. Individuals also have rights concerning solely automated decisions that produce legal or similarly significant effects. TLNT Connect does not currently make such decisions about individuals solely by automated means.
Information may be processed in the United States and other provider locations. Where required, transfers rely on adequacy decisions, the European Commission Standard Contractual Clauses, the UK Addendum, or another lawful mechanism, supplemented by technical and organizational safeguards as appropriate.
Security And Incident Response
We use tenant scoping, role and token checks, encryption or provider-managed secret storage, audit logging, access controls, and incident procedures designed to protect information. No system is perfectly secure. If a qualifying breach occurs, we will notify affected parties and regulators as required by applicable law.
Children And Minor Creators
TLNT Connect accounts are for people at least 18 years old. The service is not directed to children under 13. Agencies may maintain business records about minor creators only when they have lawful authority, give required notices, obtain required parent or guardian consent, and avoid entering unnecessary sensitive information. Contact us if you believe a child's information was submitted without proper authority.
Changes To This Policy
We will post updated versions with a new effective date and retain version history. We will provide additional notice before a material change when required. Material changes apply prospectively unless law permits and we clearly disclose otherwise.
Contact
Tlnt Connect LLC, 611 South Dupont Highway, Dover, DE 19901. Privacy requests: privacy@tlntconnect.com. Security reports: security@tlntconnect.com. General support: support@tlntconnect.com.
