This Privacy Policy explains how TBSS Labs, LLC (“Adrails”, “we”, “us”, or “our”) collects, uses, stores and protects personal data when you visit adrails.ai, use the Adrails platform or use related services (the “Service”).
Adrails is a business service for paid media teams. It connects to advertising, commerce and analytics accounts that a customer chooses to authorize. This policy is intended to meet applicable data protection requirements, including the GDPR and UK GDPR where they apply.
1. Our role
Our role depends on the data involved:
- Controller. We decide how to process account, authentication, waitlist, support, security and service usage data.
- Processor or service provider. A customer controls the advertising, commerce and analytics data it connects to Adrails. We process that data on the customer's instructions to provide the Service.
2. Data we collect
2.1 Visitors, waitlist members and newsletter subscribers
If you join a waitlist or subscribe to product news, we store your email address and the form from which you joined. We may also receive ordinary request information such as an IP address, browser type, device information and timestamps in infrastructure and security logs.
2.2 Account and workspace data
We store your name, email address, profile image, authentication method, session information, workspace name, workspace membership, role, team membership and invitations. A session may include an IP address and user agent. If you sign in with Google, we receive the profile details Google makes available for authentication. We do not receive your Google password.
2.3 Meta advertising data
When an authorized workspace member connects Meta, we receive the Meta user identifier and name, granted permissions, access token and token expiry. We also receive information for the ad accounts the person may access, including account identifiers, names, currency, timezone and account status.
To build, monitor and explain campaigns, Adrails may process campaign, ad set, ad and creative identifiers and settings; budgets, targeting, delivery and review information; creative metadata and source URLs; and performance metrics such as impressions, spend, frequency, clicks, results and attributed revenue. Adrails does not permanently store the underlying image or video files fetched from Meta.
Meta access tokens are encrypted before they are stored. The Service requests ads_read to read account structure and performance, and ads_management to create or change advertising objects. A change is prepared in Adrails and sent to Meta when an authorized workspace member approves it, or under a rule a member turned on, such as an automation or auto-approve in a conversation.
2.4 Google Ads and Google Drive data
When an authorized workspace member connects Google Ads, we receive the email address of the Google account used, the permissions granted, an access token, a refresh token and the token expiry. We also receive, for each Google Ads account that login can reach, its customer identifier, name, currency, time zone, status and, where it applies, the manager account it is reached through.
To build, monitor and explain campaigns, Adrails may process campaign, ad group, asset group, ad, asset, keyword and audience identifiers and settings; budgets, bidding, targeting, conversion goals and policy review information; and performance metrics such as impressions, clicks, cost, conversions and conversion value. Keyword research sends the keywords, locations and languages a user enters to Google's Keyword Planner.
The Service requests the https://www.googleapis.com/auth/adwords scope, which Google offers as a single scope for reading and managing Google Ads. A change is prepared in Adrails, checked by Google in validation mode, and sent when an authorized workspace member approves it, or under a rule a member turned on, such as an automation or auto-approve in a conversation.
When a workspace chooses to send its conversions to Google Ads, Adrails also requests https://www.googleapis.com/auth/datamanager. It sends the conversions that workspace's own site recorded: the Google click identifier the visitor arrived with, the time, the value, the currency and a transaction identifier, to the conversion action the workspace chose. No email address, phone number or other personal identifier is sent.
Each workspace has its own Google address, a Google service account, and a user connects Google Drive by sharing a folder with that address as a Viewer. Adrails reads Drive through it with the https://www.googleapis.com/auth/drive.readonly scope, which Google limits to the folders shared with that address, their subfolders and files added to them later. Adrails cannot read any other file in the user's Drive. It reads a file's content only when that file is used in an ad the user builds, to transfer it to the advertising account the user selected. Adrails never changes, moves, deletes or shares a Drive file. It keeps no list of the shared folders: they are read from Google each time they are shown, with who shared them. A folder's Drive identifier and name are kept only where a user uses the folder, in a conversation, an automation or a launch. With the conversation it keeps the identifiers, names and types of the files and a small preview image of each, not copies of the files themselves. Removing the address from a folder's sharing in Drive ends Adrails' access to it.
To send the leads of a Meta instant form to a Google Sheet, a user signs in with Google from the campaign's Leads tab. Adrails asks for the https://www.googleapis.com/auth/drive.file scope, which Google limits to the files Adrails creates with it: Adrails creates one spreadsheet in that account's Drive, writes its header and appends each new lead to it as Meta returns it, and reads, changes or opens no other file. The spreadsheet belongs to the user, who decides who can open it; Adrails never shares it. The leads' answers pass from Meta to the spreadsheet without being stored by Adrails, which keeps only the spreadsheet's identifier and the identifiers and times of the leads already written, so each is written once. Stopping the sync ends the writing; disconnecting the sign-in in Adrails, or removing Adrails from the Google account's permissions, ends that access.
Google access and refresh tokens are encrypted before they are stored.
Adrails' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Adrails uses Google user data only to provide and improve the user-facing features described in this policy. It does not transfer that data to others except as needed to provide those features, such as to the AI provider answering a user's request as described in section 6, to comply with law, or as part of a merger, acquisition or sale of assets with notice to users. It does not use that data for advertising, including retargeting and personalized or interest-based advertising, and does not sell it. No person at Adrails reads it unless the user has agreed to it for specific data, it is necessary for security purposes such as investigating abuse, it is required by law, or the data is aggregated and anonymized for internal operations. Adrails does not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models.
2.5 TikTok advertising data
When an authorized workspace member connects TikTok for Business, we receive an access token for the advertiser accounts that person approved in TikTok, the identifier, display name and email address of their TikTok for Business user, and, for each approved advertiser account, its identifier, name, currency, time zone, status, balance and, where it applies, the Business Center it belongs to. TikTok access tokens are encrypted before they are stored.
To monitor and explain campaigns, Adrails may process campaign, ad group and ad identifiers and settings; budgets, bidding, targeting, optimization events and review information; the identities, pixels and videos of the account; and performance metrics such as impressions, clicks, cost, conversions, video views and conversion value. Changes, such as pausing an ad or changing a budget, are sent to TikTok as for Meta and Google Ads: when an authorized member approves them, or under a rule a member turned on.
2.6 Commerce and analytics integrations
The exact data depends on the services you connect. Current integrations can include:
- Shopify: store identity, products, prices, stock, orders, order lines, refunds, and selected store analytics. Customer records can include a Shopify identifier, name, country, order count and total spent. We do not request payment card details, phone numbers or full postal addresses. Customer email addresses are converted to a one-way fingerprint before storage.
- Klaviyo: aggregated campaign and flow metrics such as sends, opens, clicks, unsubscribes and attributed revenue. The connection uses a read-only private key supplied by the customer.
- Triple Whale: aggregated advertising and commerce metrics such as spend, return on ad spend, acquisition cost and net margin. Adrails does not request customer journeys from Triple Whale.
When a workspace chooses to send its store's purchases to an advertising platform, Adrails records, for each order, what the store's Adrails pixel saw of the visit that led to it: the advertising click identifiers and browser cookies the platforms set (such as Meta's _fbp and _fbc and TikTok's _ttp), the landing page, the browser user agent and the IP address. These records are deleted after 90 days. For each purchase, Adrails then sends Meta's Conversions API or TikTok's Events API the order identifier, time, value and currency, these identifiers, and the buyer's email address, phone number and customer identifier hashed with SHA-256 before they leave Adrails, so the platform can match the purchase to its ad. What is sent to Google Ads is described in section 2.4.
Integration tokens and private keys are encrypted at rest. Adrails keeps references to product and creative media where required, not copies of those media files. Provider webhook payloads are held temporarily for processing and are scheduled for deletion after 30 days.
2.7 Conversations, approvals and agent memory
We store prompts, answers, selected data sources, tool activity and generated artifacts so a workspace can reopen its conversation history. Workspace administrators can manually store agency instructions that apply to future agent conversations. These instructions remain visible, editable and removable in workspace settings. We also keep approval records showing who approved an account change, or which automation or rule made it and who turned that on, what was proposed, whether it was applied and whether it was reverted.
To diagnose errors and improve the agent, we also keep a trace of each agent conversation turn in an observability tool we host ourselves: the message, the answer, and the tools the agent used with their inputs and results. Email addresses, phone numbers, payment card numbers and access credentials are masked before a trace is stored.
2.8 Usage and operational data
We process records needed to operate and secure the Service, including connection status, synchronization timestamps, error codes, security events, audit records and AI usage totals. For signed-in users, we also record selected product events such as onboarding progress, plan choice and whether a connection succeeds, plus aggregate workspace counts such as connected accounts, ads, conversations and agent tasks. Session recording and automatic interaction capture are disabled. We do not put integration credentials, account names, campaign names, prompts or full webhook bodies in product analytics records.
3. Why we use data
We use the data described above to:
- create accounts, authenticate users and manage workspaces;
- connect, synchronize and display authorized advertising data;
- prepare campaigns, findings and account changes for approval;
- answer questions using the workspace data selected by the user;
- maintain conversation history, auditability and service security;
- provide support and send important service or security notices;
- detect abuse, investigate errors and comply with legal obligations;
- manage the public waitlists, notify members when access opens and send product news.
4. Legal bases
Where the GDPR or UK GDPR applies, we rely on:
- Contract, when processing is necessary to provide the Service requested by a customer or user.
- Legitimate interests, for service security, fraud and abuse prevention, support, product reliability and the operation of a business service, balanced against individual rights.
- Consent, where a user joins a waitlist, subscribes to product news or where local law requires consent for a specific activity. Consent can be withdrawn at any time.
- Legal obligation, when we must retain or disclose data to comply with applicable law.
5. Providers and disclosures
We disclose data only as needed to operate the Service, follow customer instructions, comply with law, or protect the Service and its users. The providers involved can include:
- Google for optional account authentication and, where a workspace connects them, authorized Google Ads access and changes and access to the Google Drive folders a user shares with the workspace;
- Meta for authorized advertising account access and changes, and, where a workspace sends them, its store's purchases;
- TikTok for authorized advertising account access and changes, and, where a workspace sends them, its store's purchases;
- Shopify, Klaviyo and Triple Whale for customer-authorized data;
- OpenRouter and the model provider selected through it for AI processing;
- Crisp for support conversations, which receives the name and email address of a signed-in user who opens the chatbox, and whatever they write in it;
- PostHog for audience measurement and product analytics. Before a visitor starts an account or booking flow, or signs in, PostHog counts page views without cookies or any identifier stored on the device: it receives the request, hashes the IP address and browser signature into an identifier that changes every day, and discards the IP address. The requests travel through adrails.ai;
- DataFast for website and product analytics, enabled by default for new visitors. It receives public page paths, broad application sections, campaign codes, referring domains, IP addresses, browser and device information, and cookie identifiers to measure visits and acquisition sources. When analytics is enabled, it also receives selected product events, such as signup, account connection, task starts, audit completion and checkout opening, with predefined categories such as plan, platform or sample-versus-upload mode. For signed-in users we retain a private link to the visitor identifier until the analytics preference expires, so MCP tool outcomes and completed automation runs can be attributed even when the browser is closed. DataFast receives only predefined outcome, trigger and source categories, not your Adrails user or workspace identifiers. Prompts, imported files, account names and customer data are excluded. When analytics is enabled, its visitor and session identifiers are also attached to new Stripe Checkout sessions, so DataFast can link confirmed purchases and subscription revenue to acquisition sources. Requests pass through Adrails to remove URL credentials, private path identifiers and unapproved event properties before forwarding;
- hosting, database, cache, email delivery and security providers needed to run Adrails.
We may also disclose information in response to a valid legal request, during a corporate transaction subject to appropriate safeguards, or when necessary to protect rights, safety and service integrity. We do not sell personal data and do not share it for cross-context behavioral advertising.
6. Artificial intelligence
Adrails sends a user's prompt, relevant conversation history, workspace instructions and the tool results needed to answer the request to an AI provider. This can include advertising and aggregated commerce metrics selected for the conversation. Integration tokens, private keys and passwords are not sent to the model.
AI answers and proposed actions can be incomplete or inaccurate. They must be reviewed before use. Adrails does not treat an AI response as an approval to change an advertising account.
7. Cookies
Adrails uses first-party cookies and similar storage that are necessary for authentication, session security and request protection. PostHog measures public page views without its own cookies until analytics is enabled, as described in section 5. Before analytics is enabled, the browser can retain the public pages visited, campaign parameters, tool interactions and selected call-to-action for up to 30 days. This local journey is sent to PostHog when the visitor starts an account or booking flow, or signs in, so the resulting account or booking can be attributed to its source; from that point PostHog uses first-party storage to recognise the browser. Adrails does not use this information for advertising retargeting. Where local law requires prior consent, collection remains subject to that consent.
Separately, the first public page visit is kept in a first-party attribution cookie for up to 90 days. It contains the public page path, external referring domain, short campaign codes, whether Google or Meta click parameters were present, and the visit time. It does not contain the click identifiers, full referring URL, search text or account details. This source is attached to account and workspace creation so a sign-in provider does not replace the original source. The cookie does not enable PostHog storage or advertising retargeting. Do Not Track and Global Privacy Control prevent this attribution cookie from being used.
8. Retention
We keep personal data only for as long as needed to provide the Service, meet contractual and legal obligations, resolve disputes and protect the Service. In particular:
- account, workspace and connected data are generally kept while the account or workspace remains active;
- disconnecting a supported integration stops future synchronization and removes the stored credential for that connection;
- temporary webhook payloads are scheduled for deletion after 30 days;
- agent conversation traces are deleted after 30 days;
- waitlist and newsletter data is kept until you unsubscribe or ask us to delete it;
- security and audit records may be retained longer where necessary to prevent abuse, establish what happened or meet a legal obligation.
When data is deleted from active systems, residual copies may remain in protected backups until those backups expire under the normal backup cycle.
9. Meta, Google and TikTok data, and deletion
You can revoke Adrails' access at any time from your Facebook or Meta business settings. Revocation prevents future access, but it does not by itself tell us to delete data already imported into a workspace.
To request deletion of Meta data held by Adrails:
- Email [email protected] with the subject “Meta data deletion”.
- Include the email address used for Adrails and, if available, the name or identifier of the relevant workspace or ad account. Do not send an access token, password or private key.
- We may ask for information needed to verify identity and authority over the workspace before deleting data.
- Once verified, we will delete the applicable Meta token, Meta profile details, ad account metadata, snapshots, drafts, archived account objects and related conversation content from active systems, except for limited records we must retain by law or need to establish that the request was completed.
You can revoke Adrails' access to Google Ads at any time from your Google Account permissions page, at myaccount.google.com/permissions, or by disconnecting it in Adrails, which also removes the stored token. Access to a Google Drive folder ends when it is no longer shared with the workspace's Google address. To request deletion of Google data held by Adrails, follow the same steps with the subject “Google data deletion”. Once verified, we will delete the applicable Google tokens, Google account details, Google Ads account metadata, snapshots, drafts, Drive file references and related conversation content from active systems, with the same exceptions.
You can revoke Adrails' access to TikTok at any time from your TikTok for Business account settings, or by disconnecting it in Adrails, which also removes the stored token. To request deletion of TikTok data held by Adrails, follow the same steps with the subject “TikTok data deletion”. Once verified, we will delete the applicable TikTok token, advertiser account metadata, snapshots, drafts and related conversation content from active systems, with the same exceptions.
We will confirm receipt and respond within 30 days. For a full Adrails account or workspace deletion, use the same email address and state that broader scope in the request. The same instructions are available at our Data Deletion page.
10. Security
We use technical and organizational measures designed to protect data, including encryption in transit, encryption of Meta, Google and integration credentials at rest, workspace-level access controls, server-side authorization, provider signature checks, rate limits and audit records. No system is completely secure, so users should protect their account and promptly report suspected unauthorized access.
11. International transfers
Adrails and its providers may process data in countries other than the country where a user or customer is located. Where required, we use recognized safeguards for international transfers, such as contractual protections, and assess provider security and confidentiality terms.
12. Your rights
Depending on where you live, you may have the right to access, correct, delete, restrict or receive a copy of personal data; object to certain processing; withdraw consent; and complain to a data protection authority. These rights may be subject to legal exceptions.
If Adrails processes data for one of our customers, please contact that customer first. We will support the customer in responding. For data we control, email [email protected]. We may need to verify your identity before completing a request.
13. Children
The Service is intended for business users and is not directed to anyone under 18. We do not knowingly collect personal data from children. If you believe a child has provided data to Adrails, contact us so we can investigate and delete it where required.
14. Changes to this policy
We may update this policy as the Service, integrations or legal requirements change. The date at the top shows the latest revision. We will provide additional notice before a material change takes effect where required.
15. Contact
Privacy questions and requests can be sent to [email protected].
Service: Adrails
Operator: TBSS Labs, LLC
The contractual terms for using Adrails are available in our Terms of Service.