All policies

Third-Party Integrations and API Data Policy

How we access and use data from Google, Cloudflare, Meta, TikTok, Shopify and other platforms you connect.

Last updated

Tryso lets organizations connect third-party platforms. This policy explains, for each platform, what access we request, what we do with the data, how long we keep it and how to disconnect. It supplements our Privacy Policy and is published to meet the developer and app-review requirements of Google, Cloudflare, Meta, TikTok, Shopify and the other platforms listed.

1. Principles for every integration

  1. You choose. Nothing is connected until an owner or administrator starts the connection and approves the platform's consent screen.
  2. Least privilege. We request only the permissions (scopes) needed for the feature you enable, and use data only to provide that user-facing feature.
  3. No selling, no ad profiling. We never sell data received from a platform, never use it to build advertising profiles or for purposes unrelated to the feature, never use it to determine creditworthiness or for lending, and never transfer it to data brokers or information resellers.
  4. No AI training. We do not use data received from any platform's API to develop, improve or train generalised artificial-intelligence or machine-learning models.
  5. Limited human access. Our staff do not read platform data unless you ask us for support and give permission, it is needed for security or abuse investigation, it is needed to comply with law, or it has been aggregated and anonymised for internal operations.
  6. Security. Access and refresh tokens and API credentials are encrypted at rest and transmitted only over TLS. They are scoped to one organization and stored in that organization's records.
  7. Disconnect any time. Disconnecting from Settings → Integrations (or the relevant screen) stops all access immediately, deletes the stored token and, where the platform supports it, revokes it. You can also revoke access from the platform's own security settings.
  8. Platform terms. Your use of each platform is subject to its own terms and policies. We comply with each platform's developer terms.

2. Google

Features: Sign in with Google; Google Ads management in Ads Manager; Google Analytics 4, Google Tag Manager and Google Ads conversion tracking on storefronts; Google Maps location picker; Merchant and search features where enabled.

Feature Access How we use it
Sign in with Google openid, email, profile Create your account and sign you in. We store your Google account ID, name, email and profile photo.
Google Ads https://www.googleapis.com/auth/adwords List the ad accounts you choose, create and edit campaigns, ads, budgets and audiences you author in Tryso, and show performance reports.
Analytics, Tag Manager, Ads tags Measurement or container IDs you enter (no OAuth) Load the tags on your storefront and send the events you configure.
Google Maps Platform API key (no user data) Show maps and let you pick a store or delivery location.

Limited Use disclosure: Tryso's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide and improve the user-facing features described above, do not transfer it to others except as needed to provide those features, to comply with law, or as part of a merger or acquisition with your consent, and do not allow humans to read it except as described in section 1.5.

Retention: Google account identifiers are kept while your account exists. Google Ads campaign copies and performance snapshots are kept while the connection is active and deleted within 30 days after you disconnect or close the organization. Revoke access at any time at myaccount.google.com/permissions.

3. Cloudflare

Feature: automatic DNS setup when you connect a custom domain to your store.

Access requested Why
account:read, user:read Identify the Cloudflare account you connected and show it to you.
zone:read List your zones so you can pick the domain to connect.
dns_records:read Check existing records and avoid overwriting records you did not ask us to change.
dns_records:edit Create or update only the records needed to point the chosen domain to your store (A or CNAME records, and verification records).
offline_access Keep the connection so we can re-check and repair these records while your domain is connected.

We never change nameservers, delete records we did not create, touch other zones, or read or modify email, security, firewall or billing settings. We store the Cloudflare account ID, the selected zone and encrypted tokens. When you disconnect, we revoke the token through Cloudflare's revocation endpoint and delete it; DNS records we created stay in your zone (so your site keeps working) until you remove them. You can also revoke access in the Cloudflare dashboard.

4. Meta (Facebook and Instagram)

Features: Ads Manager (create and manage Facebook and Instagram ads and read insights), Meta Pixel and Conversions API on storefronts, and product catalog sync where enabled.

We request only the permissions needed for the features you enable, such as ads_management, ads_read and business_management, and read the ad accounts, pages, campaigns, ad sets, ads, creatives and insights you select. We use the data only to show and manage your advertising inside Tryso. Pixel and Conversions API events are sent from your storefront to your own Meta dataset; where enabled, customer information such as email or phone is hashed (SHA-256) before it is sent.

Meta Platform Data is kept while the connection is active and deleted within 30 days after you disconnect, close the organization or ask us to delete it. We delete it sooner if Meta requires. See the Data Deletion Instructions, which also describe how to remove Tryso from your Facebook account under Settings → Business integrations.

5. TikTok

Features: TikTok Ads management in Ads Manager, and TikTok Pixel and Events API on storefronts.

With your authorisation through TikTok for Business, we access the advertiser accounts you select to read and manage campaigns, ad groups, ads, creatives and reports. Events sent to TikTok from your storefront include only what you configure, with personal identifiers hashed. Data is kept while the connection is active and deleted within 30 days after you disconnect. You can revoke access from TikTok for Business settings.

6. Other advertising and analytics tags

Storefronts can load tags for Microsoft Advertising, Microsoft Clarity, LinkedIn, Pinterest, Snap, Hotjar, Mixpanel, Amplitude, PostHog, Segment and server-side Google Tag Manager. These use IDs or keys you enter; Tryso does not receive data back from them. The organization is responsible for consent and disclosures (see the Cookie Policy and Merchant and Storefront Policy).

7. Commerce and accounting sync

Platform Access Use
Shopify Shop, products, inventory, orders and customers, as approved in the Shopify install screen Import and keep catalogue, stock and orders in sync
WooCommerce REST API keys you create in your store Same as above
QuickBooks Accounting scope approved in the Intuit consent screen Sync invoices, customers, items and payments
Odoo URL, database and API key you provide Sync products, partners and orders

Synced records become part of your Customer Data. When you disconnect, syncing stops and credentials are deleted; records already imported stay in your organization until you delete them. When a platform tells us that a customer or shop has asked for their data to be deleted, we delete the matching synced records within 30 days.

8. Payments, couriers and messaging

Organizations can configure PayHere, OnePay, Koko and MintPay for checkout, Fardar and other couriers for delivery, and SMS, WhatsApp and email gateways for notifications. Merchant IDs, keys and secrets are encrypted and used only to create payments, shipments and messages the organization initiates, and to receive their status callbacks. These providers act under the organization's own agreement.

9. Spam protection

Storefront forms may use Cloudflare Turnstile to tell people from bots. Turnstile processes the visitor's IP address and browser signals under Cloudflare's privacy policy.

10. Contact

Questions about a specific integration or a data request from a platform: [email protected].