adslink.io · Trust center
Privacy Policy
How adslink.io collects, uses, stores, shares and deletes data from connected advertising, analytics, ecommerce and messaging platforms.
Last updated 17 October 2026
Effective date: 17 October 2026 · Policy version: 2026-10-17
adslink.io is a private reporting and client-services application operated by adslink.io. This Privacy Policy explains how we handle account information and data from the optional services you choose to connect.
Data we collect
- Account and workspace data: name, email, verification state, profile image where supplied, password hashes, sessions, workspace membership, permissions, security/activity records and Terms acceptance version and time.
- Connection data: provider account identifiers, selected resources, encrypted access or refresh tokens and API credentials, granted scopes, connection status, sync history and provider error codes.
- Advertising data: accessible account, campaign, ad group and ad identifiers and names, currency, timezone, spend, impressions, clicks, conversions, conversion value and other supported reporting fields.
- Analytics and search data: selected GA4 property and Google Search Console site identifiers and supported aggregate traffic, engagement, ecommerce and organic-search dimensions and metrics. Google may anonymize some search queries.
- Commerce data: authorized store, seller, order, product, variation, customer, coupon, refund, source, status and transaction information supplied by WooCommerce, Shopify or supported Amazon services. Customer records can contain names, contact details and address fields.
- Delivery and billing data: configured email/WhatsApp recipients, schedules, delivery history, SMTP or linked-session details, and Stripe customer, subscription, invoice and payment-status references. adslink.io does not store full card numbers or card security codes.
Connected platforms and purpose
We request access only for the feature shown when you connect a platform. Application sign-in is separate from reporting authorization. Current connection coverage is:
| Platform or service | Current adslink.io use |
|---|---|
| Google Ads, Google Analytics 4, Google Search Console and YouTube paid campaigns | Authorized reporting for selected advertising accounts, GA4 properties and Google Search Console sites. YouTube paid-campaign results are read through Google Ads. |
| Meta Ads, Facebook and Instagram | Authorized paid-ad account and campaign reporting through Meta Ads. |
| TikTok Ads | Authorized advertising account and campaign reporting. |
| WooCommerce and Shopify | Authorized store reporting for selected stores, including supported order, product, customer, refund and sales records. |
| Amazon Seller and Amazon Ads | Limited seller and Sponsored Products reporting where enabled for the connected account. |
| Snapchat Ads, Microsoft Ads, X Ads, LinkedIn Ads, Reddit Ads, Pinterest Ads, Quora Ads, Apple Search Ads, Outbrain Ads and Taboola Ads | Connection and accessible advertiser-account discovery. Campaign or performance synchronization is used only when the relevant integration page expressly says it is available. |
| WhatsApp and email | Delivery of reports and alerts to recipients configured by an authorized workspace user. |
| POS, read-only API and Stripe | Optional private POS/API reporting and adslink.io subscription administration. Stripe handles payment details. |
How we use data
We use information to authenticate users, enforce workspace permissions, discover resources the user can access, synchronize selected reporting data, display dashboards, generate exports and client portals, send configured reports or alerts, provide support, protect the service and administer adslink.io subscriptions. adslink.io does not create ads, change campaign budgets, modify store transactions or use connected data to target ads.
Platform rules and Google Limited Use
- Google API data is handled under the Google API Services User Data Policy, including its Limited Use requirements.
- Meta and TikTok connections remain subject to the Meta Platform Terms and TikTok Developer Terms.
- Commerce connections remain subject to the Shopify API License and Terms of Use, WooCommerce REST API documentation and applicable Amazon developer agreements.
- Other advertising connections remain subject to the applicable developer/API rules of Microsoft, Snap, X, LinkedIn, Reddit, Pinterest, Quora, Apple, Outbrain and Taboola.
Information received from Google APIs is used and transferred in accordance with the Google API Services User Data Policy, including the Limited Use requirements. Connected-provider data is not sold, used for surveillance or credit decisions, or used to train general-purpose AI models. We do not combine provider data with unrelated personal data for advertising.
Sharing and optional analysis
Authorized workspace members and invited, verified clients receive only their assigned reporting access. Hosting, database, email, WhatsApp and payment providers process the information needed to operate those features. Reports and exports may contain business or customer data, so workspace owners must select recipients and permissions carefully. Optional external AI analysis requires separate workspace configuration and an explicit request; only the reporting summary needed for that request is sent to the configured provider.
Storage, security and international processing
Data is stored in the operator's database and protected backups. Retained provider tokens, API secrets and SMTP passwords are encrypted server-side with keys kept separately from the database. Essential cookies support sign-in; local browser storage may remember theme and report preferences. Service providers may process data in other countries under their own safeguards and applicable law.
Retention and deletion
We retain connected data while needed for the authorized reporting service, security, subscription administration or legal recordkeeping. Disconnecting removes locally retained credentials and stops new collection for that connection, while saved reporting history remains until an authorized cleanup or deletion request. Protected backups expire through scheduled rotation. See Data Deletion Instructions for provider revocation, account deletion and request details.
Your choices and contact
You can select or deselect resources, disable schedules, remove recipients, disconnect a provider, revoke the provider-side grant, request access or correction, and request deletion where applicable. Contact adslink.io at [email protected] or WhatsApp +971 56 900 4820. Do not send passwords, tokens, recovery codes or card details.
YouTube channel reporting
If you choose to connect YouTube, adslink.io uses YouTube API Services to read the channels you authorize, their video metadata, viewing and engagement reports, and estimated earnings only when you grant monetary access. Reports are used for your workspace dashboards and exports. YouTube access is separate from app sign-in and advertising connections.
OAuth tokens are encrypted on the server. Only authorized workspace users can access saved reports. Historical Analytics reports are retained while authorization remains valid; authorization and retained metadata are checked within YouTube’s required 30-day period. This check does not automatically refresh your selected historical reports.
You can disconnect and delete a YouTube connection and its authorized local data from Connections → YouTube Channels. Token revocation is queued through the reporting worker. You can also revoke access from Google security settings. If authorization is revoked or cannot be revalidated, privately authorized YouTube data is removed.
See the Google Privacy Policy and YouTube Terms of Service. Earnings are estimated Analytics values, not finalized AdSense payments.
Optional API data sharing
You can create a read-only API key to share explicitly selected saved reporting data with your named app or approved recipient. You choose the accounts, data permissions and expiry. Revenue and earnings require separate permission. Keys never disclose provider credentials or customer contact details.
Anyone holding a key can use its granted access until it expires or is revoked; keep it on a trusted server. We retain its hash and masked preview, access grants, named recipient, consent and bounded request history. We do not retain full keys in the key list or logs. Revocation blocks future requests but cannot recall copies already obtained by a recipient. You and your recipient must honor applicable source-platform restrictions and deletion requests.
YouTube API sharing additionally requires the current authorizing channel owner’s express consent for the named recipient. Private channel data is only for that owner or the expressly approved agent. Channel data is reported separately; combined channel totals are not provided by this API.