LDOO Privacy Policy

LDOO Limited ("LDOO", "we", "us", or "our") respects your privacy and is committed to protecting your personal data. This Privacy Policy explains how we collect, use, share, retain, and protect your data when you use the LDOO application, website, and connected integrations.

This policy applies to information you provide directly to LDOO, information generated through your use of the Service, and data you authorize LDOO to access from connected third-party platforms such as analytics, advertising, CRM, commerce, video, spreadsheet, and behavioral analytics services, including Google, Meta, LinkedIn, X, HubSpot, Shopify, Microsoft, and other integrations we support now or in the future.

1.1 Account Information: your name, email address, password or authentication credentials, company details, billing details, and team account information you provide when registering or subscribing.

1.2 Connected Platform Data: data from marketing and analytics platforms you choose to connect. Current integrations include Google Analytics 4, Google Search Console, YouTube Analytics, Google Ads, Google Sheets, Meta Ads, LinkedIn Ads, X Ads, TikTok Ads, Microsoft Advertising, HubSpot CRM, Klaviyo, Shopify, WooCommerce, and Microsoft Clarity, and may expand as we add more integrations. This data may include account and property identifiers, campaign and traffic metrics, search performance data, video analytics, spreadsheet metadata and cell values you link, e-commerce order and revenue fields where applicable, and other reporting data exposed by the connected service.

1.3 Connected Account Access Data: account identifiers needed to maintain a connection, granted scopes or permissions, encrypted OAuth tokens or other credentials, sync timestamps, selected properties/accounts, and integration configuration data.

1.4 Usage Data: device information, IP address, browser type, login activity, audit logs, feature usage, and support interactions.

1.5 AI-Generated Data: answers, reports, portals, summaries, recommendations, and other analytics generated by LDOO from your connected data, prompts, and uploaded files.

1.6People You Share With: when you share a client portal or report, or schedule report delivery, you give us the email addresses of the people who receive it. For them we store their email address; on a portal limited to named people, whether they may open it, have asked to, or were declined, and when they opened it; and whether they stopped a portal's weekly email. One-time sign-in codes sent to them are stored hashed and deleted within a day, and a verified visitor stays signed in on their device for 30 days. We process this data on your behalf, and you are responsible for having the right to share your data with the people you add. Recipients can stop a portal's weekly email from the link in each email, and can ask you or us to remove their address.

1.7 Uploaded Files: reports and other documents you upload to LDOO, such as a past client report you use to set up a report. These files can contain personal information about your clients or the people who work with them, such as a name in a sign-off.

We use your data to:

• Provide, secure, and operate LDOO.
• Authenticate, maintain, and troubleshoot connected integrations.
• Sync, store, organize, and display connected platform data inside your LDOO workspace.
• Generate answers, reports, portals, alerts, and other user-facing analytics features you request.
• Manage subscriptions, billing, payments, and customer support.
• Monitor usage, prevent abuse, investigate incidents, and improve platform functionality.
• Comply with legal obligations and enforce our terms.

We may aggregate de-identified usage data, such as feature usage, response times, and error rates, across customers for service reliability and product improvement. Aggregated data does not identify you, your end users, or any connected account. We do not combine or compare connected platform data across customer accounts.

For users in applicable jurisdictions, we process personal data under the following legal bases:

• Performance of contract.
• Legitimate interests.
• Compliance with legal obligations.
• Consent where applicable.

5.1 We do not sell personal data, connected platform data, or Google user data.

5.2 We share data with the following subprocessors, acting on our behalf and only as needed to provide LDOO:

• Supabase — database, file storage, authentication, and server functions (data stored in Singapore).
• Vercel — application hosting and server functions (United States).
• Anthropic — AI processing for answers, reports, and summaries, and reading files you upload (United States).
• Stripe — subscription billing and payments.
• Resend — email delivery.
• Upstash — short-lived caching and rate limiting.
• Sentry — error monitoring.
• Cloudflare — bot protection on sign-up and contact forms.
• Google Analytics — website and app usage analytics.

We will update this list before adding or replacing a subprocessor that processes customer data.

5.3 Connected platform data, including Google user data, is shared or transferred only as necessary to provide or improve the user-facing features you request in LDOO, and not for targeted advertising, data brokerage, resale, credit-worthiness decisions, or lending purposes.

5.4 We may disclose data where legally required or where necessary to protect rights, safety, security, and property.

5.5 In the event of a merger, acquisition, or business transfer, your data may be transferred subject to continued privacy protections consistent with this policy.

5.6 Uploaded files: when you upload a report or other document, for example to set up a report from one you already send, LDOO sends the file to Anthropic, PBC, in the United States, to read it. Anthropic is the only AI provider that processes uploaded files. LDOO does not write the file to its database or file storage: it is held only while it is read and then discarded. LDOO keeps only what you choose to save from the reading, such as the metric names, definitions, targets, and sign-off of the report templates you accept. Anthropic processes the file only under our instructions and may not use it to train its models. Anthropic may keep it for a limited period under its commercial terms, for safety and abuse monitoring, before deleting it.

6.1 LDOO accesses data from connected platforms only to provide and improve the user-facing features you request, such as syncing data, organizing workspace records, generating answers and reports, creating portals, surfacing alerts, and maintaining integration health and security.

6.2 Google API data and AI / ML model training

AI/ML model training (Google and Workspace APIs). User data obtained through Google APIs — including data accessed via Google Workspace APIs (for example, the Google Sheets API for spreadsheets you explicitly link) and data accessed via other Google APIs listed below — is not used to train, fine-tune, or improve generalized artificial intelligence, machine learning, or foundation models. It is used solely to operate LDOO for your account: for example, to run read-only syncs, store queryable copies in your workspace, and to generate the specific answers, reports, alerts, and other outputs you request.

Specific Google APIs and categories of data (read-only use). Depending on which integrations you connect, LDOO may access the following Google APIs and categories of information (always subject to the OAuth scopes you approve and this policy): Google Analytics / GA4 (property and reporting metrics); Google Search Console (search performance and property metadata); Google Ads API (advertising account and campaign reporting — read-only use in LDOO; we do not change your campaigns through this integration); YouTube Data API v3 (channel metadata, thumbnails, and video list/search results for channels you select); YouTube Analytics API (aggregated channel metrics such as views and watch time); Google Drive API (the individual Google Sheet you select via the file picker — LDOO reads spreadsheet metadata and cell values only and never writes to the file; the per-file permission Google asks you to approve also covers editing, as described in 6.2.1). We retain this data only as needed to provide the Service and as described in the retention section below.

6.2.1 Exact OAuth scopes requested. The scopes below are the complete set LDOO requests from Google. All are read-only scopes except two. Google Ads offers only one scope, adwords, which grants full access to the Google Ads accounts you connect, including making changes; LDOO uses it only to read reports and never changes your accounts or campaigns. Google Sheets uses the per-file drive.file scope, which also covers editing the file you pick; LDOO only reads that spreadsheet and never writes to or modifies your Drive files.

• https://www.googleapis.com/auth/analytics.readonly — read GA4 property list and reports (sessions, users, engagement, conversions) for the properties you connect.
• https://www.googleapis.com/auth/webmasters.readonly — read Search Console properties and search performance reports (clicks, impressions, position, CTR) for the properties you connect.
• https://www.googleapis.com/auth/youtube.readonly — read channel metadata, video lists, and thumbnails for channels you select.
• https://www.googleapis.com/auth/yt-analytics.readonly — read aggregated channel analytics (views, watch time, average view duration) for channels you select.
• https://www.googleapis.com/auth/adwords — full access to the Google Ads accounts you connect (Google offers no read-only scope). LDOO uses it only to read account structure, campaign performance, and cost metrics.
• https://www.googleapis.com/auth/drive.file — access only the individual Google Sheet you select via the file picker (including when you paste a link, which opens the picker to that file). LDOO reads spreadsheet metadata and cell values for the chosen file only. This scope does not grant access to your broader Drive.

If you disconnect an integration inside LDOO or revoke access from your Google Account permissions page, LDOO can no longer call the corresponding API.

6.2.2 Exact OAuth scopes for non-Google providers. LDOO requests the following OAuth scopes and permissions from non-Google connected platforms. Most are read-only. Where a provider offers only a scope that also allows changes (Microsoft Advertising, TikTok, HubSpot tickets), it is marked below. LDOO does not change your campaigns, contacts, orders, products, or settings in any connected account.

• Meta (Facebook/Instagram Ads): ads_read (list the ad accounts you have access to so you can choose one to connect, and read that account's performance — campaigns, ad sets, insights). No other Meta permission is requested.
• LinkedIn Ads: r_ads (read ad accounts and campaigns), r_ads_reporting (read campaign performance metrics).
• X Ads: tweet.read and users.read (identify the X account you sign in with), offline.access (keep the connection without signing in again). Ad accounts and campaign metrics are read through the X Ads API with that sign-in.
• TikTok Ads:TikTok sets permissions on the app rather than in the sign-in request. LDOO's TikTok app holds the Ad Account Management, Reporting, and Measurement permission groups; Ad Account Management also covers making changes to ad accounts. LDOO uses them only to list the advertiser accounts you authorize and read campaign, ad group, and ad reports.
• Microsoft Advertising: https://ads.microsoft.com/msads.manage (the only scope Microsoft Advertising offers; it grants full access to the accounts you connect, including making changes), offline_access (keep the connection without signing in again). LDOO uses it only to list your ad accounts and download performance reports.
• HubSpot CRM: crm.objects.contacts.read, crm.objects.deals.read, crm.objects.companies.read, crm.objects.line_items.read, crm.schemas.deals.read (read contacts, deals, companies, line items, deal properties, and pipelines), tickets (read tickets and ticket pipelines; HubSpot's tickets scope also covers editing tickets, which LDOO never does).
• Klaviyo: campaigns:read, flows:read, metrics:read, segments:read, profiles:read. LDOO currently reads campaign and flow names and their performance reports only; it does not read individual profiles.
• Shopify: read_orders (read order-level revenue and fulfillment data), read_products (read the product catalog to resolve order line items), read_reports(read store sessions and traffic through Shopify's reports). LDOO never requests write scopes; your store, products, and settings cannot be modified through this integration.
• WooCommerce: read API keys, which WooCommerce creates when you approve the connection in your store (read orders and products). Your store, orders, and products cannot be modified through this integration. Revoking the keys under WooCommerce → Settings → Advanced → REST API ends access.
• Microsoft Clarity: API key only (no OAuth). You generate a project-scoped read key inside Clarity and paste it into LDOO; LDOO reads session-level user-behavior metrics for that project only.

You can revoke any of these connections at any time from the relevant provider's integrations/apps page, or by disconnecting the integration inside LDOO.

6.3 We do not use connected platform data for targeted advertising, personalized advertising, data brokerage, resale, credit-worthiness, lending, or unrelated secondary purposes.

6.4 Where needed to provide requested functionality, we may provide relevant connected platform data to service providers acting on our behalf, including infrastructure providers and Anthropic for requested natural-language answers and reports. Those providers may process the data only under our instructions and may not use it for their own advertising or for training their generalized models on your Google user data.

6.5LDOO's use of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. Google user data is accessed, used, stored, and shared subject to the restrictions in this policy.

6.6You may revoke LDOO's access to any connected account at any time through the relevant provider settings where available, or by disconnecting the integration inside LDOO. If we materially change how LDOO accesses, uses, stores, or shares Google user data, we will update this policy and any relevant in-product notices.

We retain data only for as long as needed to provide the Service and meet legal, accounting, security, and contractual obligations.

• Account and billing records are retained for the period required to operate your subscription and comply with law.
• OAuth tokens and integration configuration are retained until you disconnect the integration, revoke access, or delete your account, subject to limited backup and recovery windows.
• Synced platform data and generated outputs are retained while your workspace is active unless you delete them earlier or request deletion.
• Email addresses of people you share with are retained until you remove the person, the portal, or your account.
• Uploaded files are not stored by LDOO. They are discarded once read; anything you save from them is retained as a generated output.
• Logs, security records, and backups may be retained for a limited period to prevent abuse, investigate incidents, and restore systems.

Deleting your account.An account owner can delete the company account in Settings. Deletion cancels the subscription straight away. For 30 days our support team can restore the account; after that, its data, stored files, and the owner's login are permanently deleted, and the deletion reaches our database backups as they roll over, within 7 days. We keep a minimal record that the account was deleted, with personal details removed after 90 days. A team member can leave a team, or delete their own login, in Settings.

When data is no longer required, we delete, de-identify, or securely destroy it. You may also request deletion of your data at any time by contacting legal@ldoo.com.

We implement industry-standard security measures, including:

• Encryption in transit and encryption at rest for sensitive data, including stored integration secrets and tokens.
• Secure hosting infrastructure, database protections, and environment-level secret management.
• Access controls, authentication, least-privilege permissions, and audit logging.
• Monitoring, incident response, and operational safeguards designed to protect confidentiality, integrity, and availability.

LDOO stores its database and files in Singapore. Data is also processed in the United States, where our application servers and AI provider run; in New Zealand, where LDOO is based; and in the other countries where the subprocessors listed in section 5.2 operate. We implement appropriate safeguards for international transfers.

You may:

• Access your personal data.
• Request correction or deletion.
• Object to certain processing.
• Withdraw consent (where applicable).

Contact legal@ldoo.com to exercise your rights.

LDOO is not intended for children under 16. We do not knowingly collect data from minors.

We may update this Privacy Policy periodically. Material changes will be communicated through the Service, on our website, or by email where appropriate.

13.1LDOO uses cookies and browser storage the Service needs to work: keeping you signed in, keeping a verified portal visitor signed in on their device for 30 days, and remembering your cookie choice. When you arrive from a campaign link, the browser also keeps that link's source (such as UTM tags or the referring site) for the session, and it may be saved with your sign-up so we can see which marketing works.

13.2LDOO also uses Google Analytics and Google Ads conversion measurement on its website and in the app, to understand how people find and use LDOO. Visitors in the European Economic Area, the United Kingdom, and Switzerland are asked first, and these tags load only if they accept. Elsewhere they load by default. You can change your choice at any time from "Cookie settings" in the website footer.

13.3LDOO never loads analytics or advertising tags on client portals, shared reports, client connect links, or an agency's custom domain.

LDOO Limited
legal@ldoo.com