Privacy Policy

1. Who is responsible for your information

We determine how information is used to administer accounts, operate this website, secure the Service, and respond to support requests. When an organization uses affiliateOS to process its campaign, website, visitor, or business data, that organization determines the purposes of that processing and we process the data on its behalf, subject to our agreement with it. Contact the organization first about information collected through its websites or campaigns.

2. Information we collect

• Account and organization information: your name, email address, account identifiers, organization membership, role, authentication records, and preferences.
• Information you provide: website content, campaign and business records, files, configuration, and communications you submit to the Service or support.
• Connected-service information: authorization credentials, account and installation identifiers, resource details, and synchronization results received from providers you connect. Google Ads and Vercel are described below.
• Technical and usage information: request timestamps, IP addresses, browser or user-agent information, requested URLs, errors, and records of actions taken in the Service, as collected by the relevant application and hosting services.
• Website tracking information: when an organization uses our tracking features, page views, clicks, attribution parameters, conversion records, and visitor or session identifiers where consent permits them. This is separate from browsing our marketing website.

3. Google Ads data and permissions

Google Ads is an optional connection for importing advertising account status and spend into affiliateOS campaign reporting. After you authorize access with Google, we can discover the Ads customer accounts available to that grant and read their customer IDs, names, currencies, time zones, status, and whether they are manager accounts. For a linked account, we read campaign IDs, names, and status, plus daily costs, clicks, impressions, and conversion totals. These are account and campaign reporting metrics, not individual viewers' Google profiles or browsing histories.

We request Google's https://www.googleapis.com/auth/adwords permission. This permission allows broader Google Ads access, but the current affiliateOS connector only reads data: it does not create ads, change bids or budgets, or modify Google Ads campaigns. It does not request Gmail, Drive, Calendar, Contacts, or other Google Workspace data, and connecting Google Ads does not give us your Google password.

We use access tokens to make Google API requests and store the refresh token encrypted so scheduled and requested synchronizations can continue when you are offline. Stored records include granted scopes, the affiliateOS user initiating the connection, consent timestamps, connection health, discovered account details, campaign references, imported metrics, and synchronization and audit history. Application records are held in our database; reporting data supports account selection, status checks, spend reconciliation, and performance and finance views for your organization.

A consent link can be opened by an account operator outside the workspace. Authorizing it connects the Google Ads account to the affiliateOS organization and campaign for which the link was created. Authorized organization members can then access the imported data according to their roles. Only grant access for an organization entitled to receive it.

4. Google data use and sharing commitments

affiliateOS follows the Google API Services User Data Policy, including Limited Use, when using Google API information or transferring it to another app. These restrictions also cover derived data and override broader provisions elsewhere in this policy.

Google data supports the connected features described above. We do not sell it, use it to target or serve advertisements, provide it to data brokers or surveillance services, or use it for credit or lending decisions. Google data is not used to train generalized AI or machine-learning models. Google Workspace API data is not used to develop, improve, or train non-personalized AI or machine-learning models.

Disclosures are limited to delivering features with your consent, security investigations, legal requirements, or a business transfer with your explicit prior consent. Hosting and database providers process Google data to operate those features. Personnel may access it only with your affirmative permission for specific data, for security or legal needs, or as legally permitted aggregates for internal operations. These restrictions apply to our service providers and successors too.

5. Information accessed through Vercel

Connecting Vercel exchanges an authorization code for an access token. We use that token to identify the connected account or team and carry out authorized hosting operations. We store the token encrypted, along with account or team identifiers and names, installation and configuration identifiers, the affiliateOS user who granted access, connection status, timestamps, and relevant audit records.

The integration requests all-project access so it can create projects for websites you bind to hosting. Within the permissions granted to the installation, it can:

• Read and write project information, including creating and deleting bound projects.
• Upload website files, create deployments, and read deployment URLs, status, and errors.
• Read and write environment variables, including site credentials and content endpoints.
• Add, read, verify, and remove custom domains and inspect their DNS configuration.
• Read user, team, and installation information to identify and manage the connection.
• Configure preview protection and create access secrets for automated preview checks.

Website files, configuration, and credentials required by the deployed site are transmitted to Vercel when you use the relevant hosting features. Project, deployment, and domain records are used to show hosting status and reconcile the state of your websites. Vercel also processes information under its own privacy policy.

6. How we use information

We use information to provide and maintain the Service, authenticate users, enforce organization permissions, connect services, deploy websites, produce requested reports, manage subscriptions, respond to support, and investigate errors or abuse. Operational and audit records help us secure the Service and understand whether requested actions succeeded. Information submitted to optional AI or connected features is processed by the providers involved in performing the requested task. Google data remains subject to the restrictions in section 4, including when used with an optional feature.

Where data protection law requires a legal basis, we rely on performance of a contract, legitimate interests in operating and securing the Service and supporting users, compliance with legal obligations, or consent where required. For data processed on behalf of an organization, that organization is responsible for identifying the applicable legal basis and obtaining required consents.

7. When information is shared

Information is available to authorized members of your organization according to their permissions. We use service providers for hosting, database storage, analytics, and other functions needed to operate the configured Service. These include Vercel for hosting and deployment, Neon for application data, and Tinybird for website analytics when those features are used. Connected services receive the information needed to carry out your instructions. Content you publish to a public website becomes publicly accessible.

We may disclose information when required by law, to protect users and the Service, or in connection with a business transfer subject to applicable privacy obligations. We do not sell personal information or share Vercel integration data with advertisers for their independent marketing.

8. Cookies and browser storage

The landing website stores your light or dark theme preference in your browser. The workspace uses cookies and related storage for authentication, session security, and preferences. You can clear or restrict this storage through your browser, which may sign you out or reset preferences.

On websites using our tracking SDK, visitor and session identifiers are omitted when consent is not given; page views can still be counted without those identifiers. The organization operating each website is responsible for its consent notices and choices.

9. Retention and deletion

Retention depends on the type of information, the organization's configured policy, the services in use, and legal or security requirements. Current operational defaults include 7 days for website request diagnostics and export download files, 30 days for raw website events and detailed click information, 180 days for unconverted attribution, and 365 days for ordinary operational audit records. Removing click details does not necessarily remove the underlying attribution record.

Financial and security audit evidence has a default retention period of seven years after the relevant financial year, subject to the organization's documented policy and legal holds. Source financial records, including conversions and statements, are not currently deleted automatically. Connection metadata, account records, and support communications may be retained for service administration, security, disputes, and legal obligations; they do not all follow the short operational windows above.

Disconnecting Vercel in affiliateOS removes the stored connection credential and disables the connection. It does not automatically erase connection metadata, audit history, or existing Vercel resources. Removing the installation in Vercel revokes its authorization; affiliateOS detects the change during a subsequent connection check. Contact us or your organization administrator to request deletion of other information. Data held by Vercel is also subject to its own retention and deletion procedures.

10. Disconnecting Google and deleting Google data

An authorized organization member can unlink Google Ads from the campaign's Account tab. This removes the stored refresh credential and discovered-account connection records and stops future scheduled access through that connection. A synchronization already in progress may finish. To revoke the Google authorization itself, remove affiliateOS from your Google Account connections. Revocation may affect other affiliateOS connections authorized by the same Google account. You can use the rest of affiliateOS without connecting Google Ads.

Unlinking or revoking access does not erase previously imported spend and metrics, campaign account references, connection metadata, or audit records, and does not change the source data in Google Ads. Historical imports remain available for your organization's reporting and reconciliation. They are not currently subject to an automatic deletion deadline. We retain them for those purposes and any required legal, security, or dispute retention, and delete them when no longer needed, subject to applicable holds.

To request deletion of Google-derived records, contact us using the details below and identify the organization and connected Ads customer ID. You can request deletion without reconnecting Google. We verify your authority, coordinate with the organization for data it controls, and explain any records that must be retained and why. Unlinking is separate from this deletion request. Copies in backups follow the storage provider's backup lifecycle and are not used for ordinary reporting after deletion from the active service.

11. Security

Google API requests use HTTPS. The Service uses organization-scoped access controls, encrypted storage for integration credentials, and audit records. Credential values are excluded from integration audit summaries. Access is limited according to the permissions needed to operate the Service. No storage or transmission method can guarantee absolute security. Keep your credentials secure and report suspected unauthorized access using the contact details below.

12. International processing

Information may be processed in countries other than your own, depending on the providers and hosting regions used for your organization. Where applicable law requires safeguards for international transfers, those transfers must be covered by an appropriate mechanism, such as an adequacy decision or contractual safeguards. Contact us for information about the providers, locations, and safeguards applicable to your Service.

13. Your choices and rights

Depending on applicable law, you may have rights to access, correct, export, or delete personal information; restrict or object to processing; and withdraw consent for future processing where consent is the legal basis. You may also complain to your local data protection authority. These rights may be subject to legal exceptions, including record retention obligations and the rights of others.

For organization-controlled data, contact the organization that collected it. Authorized administrators can manage supported retention and privacy requests in Settings → Privacy & retention. For your account or information we control, use the contact below. We may need to verify your identity or authority before responding. Do not send passwords or integration tokens with a request.

14. Children

affiliateOS is a business service intended for adults and is not directed to children. If you believe a child has provided personal information to us, contact us so we can investigate and take appropriate action.

15. Updates and contact

We may update this policy as the Service or applicable requirements change. The date above identifies the latest revision. We will provide additional notice of material changes where required by law. Before accessing additional Google data or using Google data for a new purpose, we will update these disclosures, notify affected users, and obtain their consent.

For privacy questions, data access, or deletion requests, contact Choix Media LLC at admin@affiliate-os.com. Identify your organization and the information your request concerns so we can direct it to the appropriate person.