SLATE

Slate Terms of Service

Terms governing access to Slate at slatedata.app and my.slatedata.app and use of connected marketing-data services

Effective date: July 21, 2026
Last updated: July 21, 2026
Version: 1.0

Contents

1. Agreement, service operator, and order of precedence

2. Eligibility, business use, and authority

3. Accounts, authentication, organizations, and roles

4. The Service

5. Third-party integrations and platform accounts

6. Google APIs and Google Limited Use obligations

7. Customer Data, Connected Data, and Customer responsibilities

8. Privacy and data processing

9. Security responsibilities

10. Acceptable use and prohibited data

11. Fees, subscriptions, trials, renewal, taxes, and refunds

12. Free, beta, preview, and evaluation features

13. Customer systems, dependencies, and exports

14. Support, availability, changes, and service levels

15. Ownership, licenses, and feedback

16. Confidentiality

17. Third-party services and platform terms

18. Marketing-data and reporting disclaimers

19. Suspension and termination

20. Warranties and disclaimers

21. Indemnification

22. Limitation of liability

23. Export controls, sanctions, and anti-corruption

24. Notices and changes to these Terms

25. General provisions

26. Legal operator, governing law, venue, and publication condition

Appendix A. Current integrations and scopes

Appendix B. Platform-specific obligations

Appendix C. Official platform terms reviewed

1. Agreement, service operator, and order of precedence

1.1 Agreement

These Terms of Service (the "Terms") are a binding agreement between the Customer and the person or legal entity that owns and operates Slate at slatedata.app and my.slatedata.app ("Slate," "we," "us," or "our"). "Customer" means the organization, business, agency, or other entity that creates, purchases, controls, or is identified with a Slate workspace. "User" means an individual who accesses or uses the Service for a Customer or who visits a Slate-controlled site.

By accessing or using Slate, creating an account, accepting an invitation, clicking an acceptance control, connecting a platform, placing an order, or using a paid, free, beta, preview, or evaluation feature, the Customer and User agree to these Terms and the Slate Privacy Policy.

1.2 Incorporated terms

The agreement may also include an order form, checkout page, plan description, statement of work, data-processing addendum, service-level agreement, security addendum, business associate agreement, or other written document signed or expressly accepted by Slate and Customer (each, an "Order Document"). A third-party platform's terms apply separately to that platform and its data.

1.3 Order of precedence

If documents conflict, the following order applies unless a signed Order Document states otherwise: (1) a signed Order Document; (2) a signed data-processing or security addendum for its subject matter; (3) these Terms; (4) the Slate Privacy Policy; and (5) online documentation. Third-party platform terms control the use of that platform, its APIs, and its data, even if a Slate document would otherwise permit broader use.

1.4 No implied commitments

Sales discussions, demonstrations, roadmaps, mockups, public statements, issue trackers, and feature descriptions do not create a contractual commitment unless included in an Order Document. A feature marked planned, coming soon, beta, preview, evaluation, inactive, or configuration required is not an available production commitment.

2. Eligibility, business use, and authority

•   Age and capacity: each User must be at least 18 and legally capable of entering a binding agreement.
•   Business use: the Service is offered for legitimate business, professional, and organizational use, not for personal, family, household, or consumer use.
•   Authority: a User accepting these Terms for a Customer represents that the User has authority to bind that Customer and administer its workspace and connected accounts.
•   Platform authority: a User may connect or select only a platform account that the User is lawfully authorized to access and may not use Slate to bypass account controls, agency-client permissions, or platform restrictions.
•   Sanctions and restrictions: a User and Customer must not use the Service if prohibited by applicable export controls, sanctions, law, or a platform decision that restricts access.

3. Accounts, authentication, organizations, and roles

3.1 Registration and accurate information

A User must provide accurate, current, and complete account and organization information and keep it current. Slate may rely on the email domain, organization assignment, invitation, and administrator instructions shown in the Service. A User must not impersonate another person, create an account for an unauthorized organization, or provide a misleading business identity.

3.2 Authentication and Google Sign-In

Slate uses Clerk for authentication and organization management and may offer Google Sign-In. Google Sign-In authenticates the User; it does not by itself authorize access to Google Ads, Google Analytics, Google Sheets, Google Docs, Google Slides, or Google Drive. Data-source and export integrations require separate, contextual OAuth authorization.

3.3 Account security

•   Users must maintain the confidentiality and security of devices, email accounts, Google accounts, authentication factors, recovery methods, and sessions.
•   Users must use multi-factor authentication where available and must not share accounts or authentication factors.
•   Customer must promptly remove departed Users, review roles, and disconnect integrations that are no longer needed.
•   Customer must promptly notify Slate through the published security or support channel of suspected compromise, unauthorized access, credential exposure, or misuse.
•   Customer is responsible for activity under its accounts except to the extent directly caused by Slate's breach of these Terms or applicable law.

3.4 Organizations and roles

A Slate workspace is organized by Customer. The current role model includes Admin, Editor, and Viewer permissions. Admins manage workspace configuration, integrations, members, billing, and other privileged actions. Editors can create, import, edit, correct, or govern records according to product permissions. Viewers generally inspect records and reports without mutation rights. The feature-level permission model controls in case a role description differs from the interface.

3.5 Administrators

Customer administrators can control access to the workspace and may be able to view, export, correct, delete, or restrict Customer Data; manage integrations; change roles; and close accounts. Users acknowledge that Customer, not Slate, controls administrator decisions. Slate may follow an authenticated administrator's instructions unless Slate reasonably believes the instruction is unauthorized, unlawful, insecure, or inconsistent with platform requirements.

4. The Service

4.1 Core functions

Slate is a marketing-data aggregation, normalization, governance, reporting, and export service. Depending on the plan and configuration, Slate may allow Customers to connect marketing platforms, import files, paste or enter records, identify source accounts, store raw data, normalize dimensions and metrics, edit and label records, run rules, maintain audit history, create saved views and reports, receive alerts, and export data to CSV or Google Sheets.

4.2 Scope of current product

The audited product includes code-backed connectors for Google Ads, Google Analytics 4, Meta Ads, LinkedIn Ads, Microsoft Advertising, TikTok Ads, Reddit Ads, and Shopify, and a Google Sheets export destination. Amazon Ads is present as a provider designation but was not established as a live connector. Google Docs, Google Slides, broad Google Drive, and a Customer-facing Klaviyo connector were not active in the audited connector registry as of the effective date.

4.3 Customer configuration

Features depend on Customer configuration, platform approval, OAuth scopes, account permissions, API availability, developer tokens, plan limits, environment variables, selected accounts, report definitions, schedules, and destination permissions. Customer is responsible for reviewing the requested scope and selected accounts before authorizing a connection.

4.4 No professional advice

Slate provides software and data-processing tools. Slate does not provide legal, tax, accounting, financial, investment, employment, privacy, security, advertising-policy, or other regulated professional advice. Reports, alerts, pacing, attribution, calculations, and recommendations are operational information and do not replace professional judgment or source-platform review.

5. Third-party integrations and platform accounts

5.1 Authorization

When a User initiates an integration, Customer instructs Slate to communicate with the selected platform, receive and store authorization credentials, access approved accounts and data, and process that data to provide the Customer-facing feature. Customer represents that it has all rights, authority, contracts, consents, and platform permissions necessary for the connection and processing.

5.2 OAuth tokens and credentials

Slate may store OAuth access and refresh tokens, scopes, expiry information, external account identifiers, and connection metadata. The audited implementation encrypts OAuth tokens at rest using authenticated encryption. Customer must not provide raw passwords or credentials to Slate when an approved OAuth or platform authorization method is available.

5.3 Account selection and agency use

A User may select only accounts the User is authorized to access. An agency or service provider connecting a client account must have documented client authority and must comply with the platform's agency, client, manager-account, and data-use rules. Slate may request evidence of authority and may suspend a connection when authority is disputed.

5.4 Platform changes and access loss

A platform can change APIs, fields, attribution, permissions, review standards, rate limits, pricing, data-retention rules, branding, authentication, or access at any time. Slate is not liable for a platform change, outage, rejection, suspension, revocation, data correction, or account action beyond Slate's reasonable control. Slate may modify, limit, or discontinue an integration to maintain compliance or security.

5.5 Disconnecting

Customer may disconnect an integration using available Slate controls and should also revoke Slate in the platform account when immediate revocation is required. Disconnection stops new access after revocation is processed but does not automatically delete historical data already imported or exported unless the platform terms, law, or a deletion instruction require it.

6. Google APIs and Google Limited Use obligations

6.1 Separate Google authorizations

Google Sign-In and Google data integrations serve different purposes. Google Sign-In is for authentication. Google Ads, Google Analytics, and Google Sheets access requires separate integration authorization. Customer must not treat a sign-in consent as consent for a data integration or use an integration client to obtain permissions unrelated to an active feature.

6.2 Current Google scopes

•   Google Ads: `https://www.googleapis.com/auth/adwords` for authorized Google Ads account access and reporting.
•   Google Analytics 4: `https://www.googleapis.com/auth/analytics.readonly` for read-only property and report access.
•   Google Sheets: `https://www.googleapis.com/auth/spreadsheets` and `https://www.googleapis.com/auth/drive.file` for Customer-directed spreadsheet creation or editing and access to files created, opened, or explicitly shared for the Slate workflow.
•   Google Docs, Google Slides, and broad Drive: no active Docs, Slides, or broad Drive scope was identified in the audited implementation. Slate must not request or represent such access until the feature exists, the minimum scope is implemented, and the required policy update and authorization occur.

6.3 Permitted Google API Data use

Slate will use Google API Data only to provide or improve the user-facing feature for which the Customer and User granted access, including account selection, import, normalization, governance, reconciliation, reporting, and Customer-directed export. Slate may use aggregated operational statistics that do not contain Google API Data to operate the Service.

6.4 Prohibited Google API Data use

•   selling or transferring Google API Data to data brokers, advertising networks, information resellers, credit providers, surveillance providers, or unrelated third parties;
•   using Google API Data to serve, target, personalize, or measure Slate advertising or another Customer's advertising;
•   building cross-customer profiles, audiences, or benchmarks that expose or rely on identifiable Google API Data without a permitted user-facing purpose and required authorization;
•   training general-purpose artificial-intelligence or machine-learning models on Google API Data;
•   allowing humans to read Google API Data except when necessary for a permitted feature, security, abuse investigation, legal compliance, or support requested by the Customer and subject to access controls;
•   requesting speculative or excessive scopes; or
•   using Google API Data for any purpose materially different from the purpose disclosed to and authorized by the User without an updated disclosure and renewed consent or authorization where required.

6.5 Google disclosure and subprocessors

Slate may disclose Google API Data only to Customer-authorized Users and destinations, to service providers that process the data for Slate under confidentiality and data-protection restrictions and only as necessary to provide the permitted feature, or when legally required. Slate remains responsible for ensuring that subprocessors do not use Google API Data for unrelated purposes.

6.6 Google deletion, revocation, and incidents

Slate will support disconnection and will delete or render inaccessible active token material following revocation, subject to operational processing and backup aging. Slate will delete Google API Data when required by Customer instruction, platform rule, account deletion, or law. Customer must separately manage data previously exported to Google Sheets. Slate will investigate and provide required notice for known or suspected unauthorized access involving Google data, including notice to Google where applicable.

6.7 Google Ads API requirements

Customer and Slate must comply with Google Ads API policies, developer-token conditions, attribution and branding rules, account-access requirements, data restrictions, and Required Minimum Functionality applicable to the Slate access level and interface. Slate may restrict a Google Ads integration to reporting-only capabilities and may require Customer action in the native Google Ads interface.

7. Customer Data, Connected Data, and Customer responsibilities

7.1 Customer ownership

As between Slate and Customer, Customer retains all rights it lawfully holds in Customer Content and Connected Data. Slate does not acquire ownership of Customer Data merely because the data is imported, normalized, stored, edited, governed, reported, or exported through the Service.

7.2 License to Slate

Customer grants Slate and its subprocessors a worldwide, non-exclusive, limited license during the agreement to host, copy, transmit, transform, normalize, display, process, and otherwise use Customer Data solely to provide, secure, support, and comply with legal obligations relating to the Service and as otherwise expressly instructed by Customer. This license does not authorize Slate to sell Customer Data, use it for Slate advertising, or train general-purpose models.

7.3 Customer warranties and instructions

•   Customer has the rights and authority to submit, connect, process, correct, export, and instruct Slate concerning Customer Data.
•   Customer has provided all notices and obtained all consents, permissions, and lawful bases required for Users, customers, prospects, employees, client accounts, and other individuals represented in the data.
•   Customer instructions comply with law, contract, platform terms, and the rights of third parties.
•   Customer will not direct Slate to retain data after a required deletion or use data in a manner prohibited by the connected platform.
•   Customer will maintain the accuracy of source-account ownership, labels, settings, time zones, currencies, metric definitions, and permissions needed for its use case.

7.4 Data minimization

Customer must import only information reasonably necessary for the Customer's marketing-data use case. Customer must exclude personal information and free-text that are not needed for aggregation, governance, reporting, or export. Customer must use platform filters, report levels, field selections, protected-customer-data settings, and file preparation to minimize data before transmission to Slate.

7.5 Corrections and audit history

Slate may record the actor, time, source, old value, new value, origin, reason, and related metadata for imports, edits, corrections, overwrites, deletions, rules, settings, and exports. Customer acknowledges that correction history may preserve prior values for governance and dispute purposes, subject to legal deletion obligations. Customer must not use audit history to retain data that must legally or contractually be deleted.

7.6 Deidentified and aggregate operational information

Slate may generate service-level statistics that are aggregated and deidentified so they cannot reasonably identify Customer, a User, or an individual. Slate may use those statistics to operate, secure, capacity-plan, and improve the Service. Slate will not use Google API Data or another platform-restricted data set for an aggregate or deidentified purpose when the platform policy does not permit it, and Slate will not attempt to reidentify deidentified information.

8. Privacy and data processing

8.1 Privacy Policy

The Slate Privacy Policy explains Slate-controlled processing, processor/service-provider roles, connected platforms, cookies, analytics, advertising, marketing, retention, security, and rights. Customer must maintain its own privacy notices and must not rely on the Slate Privacy Policy as Customer's notice to its customers, employees, website visitors, or client-account users.

8.2 Data-processing roles

For Customer Data processed on Customer's documented instructions, Customer is generally the controller or business and Slate is the processor, service provider, or contractor. If Customer is itself a processor, Slate may act as Customer's subprocessor. For Slate account, billing, security, service administration, and Slate marketing data, Slate may act as an independent controller or business.

8.3 Data Processing Addendum

If applicable privacy law requires a data-processing contract, Customer and Slate must enter the then-current Slate Data Processing Addendum before the regulated processing begins. The DPA should address processing instructions, confidentiality, security, subprocessors, transfers, data-subject assistance, impact assessments, audit information, deletion, return, and security-incident notification. No separate Slate DPA was available in the audited materials, so the Legal Readiness Register identifies it as a launch requirement rather than implying that one already exists.

8.4 Customer requests and assistance

Customer is responsible for responding to privacy requests relating to Customer Data. Slate will provide available self-service tools and reasonable assistance required by applicable law and contract, taking into account the nature of processing. Slate may require verification and may charge reasonable fees for extraordinary assistance when permitted by contract and law.

8.5 Regulated data

Customer must not use Slate to process protected health information, payment-card data subject to PCI DSS storage requirements, government identifiers, children's data, biometric data, precise geolocation, special-category data, or other highly regulated information unless Slate expressly agrees in a signed Order Document and the required contract, security, and product controls are active. No such regulated-data addendum is identified as active as of the effective date.

9. Security responsibilities

9.1 Slate safeguards

Slate will maintain reasonable administrative, technical, and organizational safeguards appropriate to the Service and the information processed. Safeguards include secure transmission, encrypted OAuth tokens, authenticated access, organization scoping, role-based authorization, secret management, audit records, deployment controls, logging, backup, recovery, vendor review, and incident response, as applicable to the production configuration.

9.2 Customer safeguards

•   use strong authentication and multi-factor authentication where available;
•   protect accounts, devices, API credentials, email, and recovery methods;
•   assign the least privilege necessary and review membership and integrations regularly;
•   configure source platforms, OAuth apps, tags, exports, and destinations securely;
•   avoid placing secrets, tokens, passwords, payment data, or sensitive personal information in notes, files, source names, support requests, or free-text;
•   maintain secure backups or exports needed for Customer business continuity;
•   promptly install or accept security-related updates and follow Slate security instructions; and
•   notify Slate promptly of suspected compromise, unauthorized access, or unlawful use.

9.3 Security testing

Customer must not perform penetration testing, vulnerability scanning, load testing, denial-of-service testing, social engineering, or security research against Slate without Slate's prior written authorization and an agreed scope. Good-faith vulnerability reports must use the published security-reporting method and must not access, alter, retain, or disclose other Customers' data.

9.4 Security incidents

Each party will promptly investigate a known or suspected security incident within its control, take reasonable remediation steps, preserve relevant evidence, and provide legally or contractually required notice. Customer is responsible for incidents caused by Customer accounts, devices, personnel, exports, destinations, platform accounts, or instructions except to the extent directly caused by Slate.

10. Acceptable use and prohibited data

Customer and Users must not use the Service to:

•   violate law, regulation, sanctions, court order, platform terms, privacy rights, intellectual-property rights, confidentiality duties, or contractual restrictions;
•   access, connect, retrieve, modify, export, or disclose an account or data without authorization;
•   circumvent OAuth consent, administrator controls, platform review, account boundaries, rate limits, technical restrictions, or deletion requirements;
•   sell, broker, resell, surveil, enrich, or profile individuals using Customer Data or platform data in a manner not expressly permitted;
•   use Google API Data, platform data, or Customer Data for unrelated advertising, cross-customer audience creation, credit, employment, housing, insurance, or eligibility decisions;
•   upload malware, malicious code, destructive payloads, credential-stealing content, or material designed to compromise Slate or a third party;
•   probe, scan, reverse engineer, decompile, discover source code, bypass security, or access non-public APIs except to the extent a restriction is prohibited by law;
•   interfere with performance, overload infrastructure, automate abusive requests, scrape the Service, or use unauthorized bots or agents;
•   share accounts, misrepresent identity or authority, or use another Customer's workspace;
•   submit children's data, protected health information, complete payment-card information, authentication secrets, government identifiers, precise location, biometric templates, or other highly sensitive data without a signed written authorization from Slate;
•   place production data, secrets, or personal information in public issue trackers, source-control repositories, logs, screenshots, or public support channels;
•   remove or obscure proprietary, attribution, legal, privacy, or platform-required notices; or
•   use the Service to build or benchmark a competing product in a manner that violates these Terms, confidentiality, access controls, or law.

Slate may investigate suspected misuse, preserve evidence, restrict access, revoke tokens, remove prohibited data, and cooperate with platforms or authorities as permitted by law. Slate is not required to monitor all Customer Data but may use reasonable automated and manual measures to protect the Service.

11. Fees, subscriptions, trials, renewal, taxes, and refunds

11.1 Plans and fees

Fees, included usage, limits, billing interval, commitment, and plan features are those displayed at checkout or stated in an Order Document when Customer purchases. Slate may measure usage by workspace, User, connection, source account, row, record, sync, export, storage, API call, feature, or another metric identified in the plan.

11.2 Payment through Stripe

Slate uses Stripe for checkout, subscriptions, payment processing, invoicing, fraud prevention, and billing administration. Customer authorizes Slate and Stripe to charge the payment method for fees, taxes, overages, and other amounts due under the selected plan. Customer must keep billing and payment information accurate. Stripe's terms and privacy notice govern Stripe's independent processing.

11.3 Automatic renewal

A paid subscription automatically renews for the same billing interval unless Customer cancels before the renewal date or the Order Document states otherwise. Slate will charge the then-current renewal price and applicable taxes. Slate will provide renewal or price-change notice when required by law or the Order Document.

11.4 Cancellation

Customer may cancel through the available billing controls or published billing-support method. Cancellation stops future renewal and ordinarily takes effect at the end of the paid period unless the interface or Order Document states an earlier date. Customer remains responsible for charges incurred before the effective cancellation date.

11.5 Trials

A trial begins and ends as shown at enrollment. If payment information is collected and the enrollment disclosure states that the trial converts automatically, the subscription begins at the end of the trial unless canceled before conversion. Slate may limit, modify, or end a trial to prevent abuse, comply with law, or maintain platform access.

11.6 Refunds

Except where required by law or expressly stated in an Order Document, fees are non-refundable and non-creditable, including for partial periods, unused features, disconnected integrations, platform outages, or Customer cancellation after a charge. Slate may issue a discretionary credit without creating an obligation to do so again.

11.7 Taxes

Fees exclude sales, use, value-added, goods and services, withholding, and similar taxes unless stated otherwise. Customer is responsible for applicable taxes, except taxes on Slate's net income. If Customer must withhold tax, Customer will provide documentation and, unless prohibited, pay amounts so Slate receives the amount it would have received without withholding.

11.8 Late payment and disputes

Slate may suspend paid features for overdue amounts after reasonable notice. Customer must raise a good-faith billing dispute promptly and pay undisputed amounts. Chargebacks made without first providing a reasonable opportunity to correct a billing error may be treated as nonpayment, subject to applicable law.

12. Free, beta, preview, and evaluation features

Slate may offer free, beta, preview, early-access, experimental, or evaluation features. These features may be incomplete, inaccurate, changed, rate-limited, unsupported, or discontinued and may have separate terms. Customer must not use them for production-critical, regulated, safety-critical, or legally required workflows unless Slate expressly authorizes that use in writing.

Beta and preview data may be deleted or reset. Slate may request feedback and usage information, but may not use Google API Data or other restricted platform data as feedback, training data, or unrelated analytics.

13. Customer systems, dependencies, and exports

13.1 Customer systems

Customer is responsible for internet access, devices, browsers, email, identity systems, platform accounts, Google Workspace configuration, destination files, data preparation, and other systems outside Slate. Customer must maintain licenses and permissions needed for those systems.

13.2 Exports

When Customer exports data to CSV, Google Sheets, or another destination, Customer directs the disclosure and assumes responsibility for destination permissions, sharing, retention, backup, downstream formulas, copies, and recipients. Deleting data in Slate does not delete exported copies. Customer must secure and delete destination copies separately.

13.3 Scheduled jobs

Scheduled imports, exports, reconciliation, alerts, and other jobs depend on valid tokens, platform availability, quotas, destination permissions, hosting execution, and configuration. Customer must review failures and must not rely on a scheduled job without monitoring and reconciliation appropriate to the business impact.

13.4 Data portability

Slate may provide CSV, Google Sheets, API, or other export mechanisms according to the plan. Slate is not required to reproduce every raw provider field, proprietary calculation, platform object, or internal implementation detail. Customer should export needed data before termination and should not treat Slate as the only backup of source-platform data.

14. Support, availability, changes, and service levels

14.1 Support

Support channels, hours, response targets, and included services are those published for the plan or stated in an Order Document. Response targets are goals, not guaranteed resolution times, unless a signed service-level agreement states otherwise. Customer must provide enough non-sensitive information to reproduce the issue and must not send raw secrets or unnecessary personal data.

14.2 Availability and maintenance

Slate may perform scheduled or emergency maintenance and may temporarily limit access for security, reliability, legal, platform, or operational reasons. Slate will use reasonable efforts to provide notice of material planned interruptions when practical. No uptime commitment or service credit applies unless stated in a signed service-level agreement.

14.3 Changes

Slate may change the Service to improve it, address security or law, comply with platform requirements, manage costs, or discontinue features. Slate will use reasonable efforts to provide advance notice of a material reduction to a paid core feature when practical. Immediate changes may be necessary for security, legal, or platform compliance.

14.4 Third-party limits

Slate is not responsible for third-party outages, API latency, rate limits, attribution changes, reporting delays, data corrections, permission changes, app-review decisions, account suspensions, or provider discontinuation. Slate may display a platform error or substitute a product-level explanation but cannot guarantee that the third-party information is complete or current.

15. Ownership, licenses, and feedback

15.1 Slate technology

Slate and its licensors own the Service, software, source code, architecture, user interface, documentation, designs, trademarks, logos, non-Customer content, and related intellectual property. Except for the limited right to use the Service during the subscription, no rights are transferred to Customer.

15.2 Limited access right

Subject to these Terms and payment, Slate grants Customer a limited, non-exclusive, non-transferable, non-sublicensable right during the agreement to permit authorized Users to access and use the Service for Customer's internal business operations and authorized client services. Agency use for clients must comply with client authority and platform terms.

15.3 Documentation and marks

Customer may use Slate documentation only to use the Service. Customer may not remove notices or use Slate marks without permission. Nothing permits either party to issue a press release, display the other party's logo, or identify the other as a customer or partner without prior permission, except where legally required.

15.4 Feedback

If Customer voluntarily provides feedback, Customer grants Slate a perpetual, irrevocable, worldwide, royalty-free right to use and incorporate that feedback without restriction, provided Slate does not publicly identify Customer without permission and does not treat Customer Data, Google API Data, or confidential information as feedback.

16. Confidentiality

16.1 Confidential information

"Confidential Information" means non-public information disclosed by one party to the other that is marked confidential or reasonably should be understood as confidential, including Customer Data, security information, product plans, pricing, source code, business plans, and credentials. Confidential Information excludes information that the recipient can document was lawfully known without restriction, becomes public without breach, is received lawfully from a third party, or is independently developed without use of the discloser's information.

16.2 Protection and permitted use

The recipient will use Confidential Information only to perform or exercise rights under the agreement, protect it using at least reasonable care, and disclose it only to personnel, affiliates, advisers, and subprocessors who need access and are bound by confidentiality obligations. The recipient is responsible for their compliance.

16.3 Required disclosure

The recipient may disclose Confidential Information when legally required, but, where permitted, will provide prompt notice, cooperate with a protective-order request at the discloser's expense, and disclose only what is required.

16.4 Equitable relief

Unauthorized use or disclosure may cause irreparable harm for which monetary damages are inadequate. A party may seek injunctive or equitable relief in addition to other remedies, without waiving defenses or applicable procedural requirements.

17. Third-party services and platform terms

Third-party services are not controlled by Slate. Customer's use of Google, Meta, LinkedIn, Microsoft, TikTok, Reddit, Shopify, Amazon, Stripe, Clerk, Google Workspace, or another service is governed by the provider's terms and privacy notice. Customer is responsible for reviewing and complying with them. Slate does not endorse or warrant third-party services.

17.1 Platform-specific hierarchy

If a platform rule requires narrower use, shorter retention, deletion, attribution, notice, consent, access control, or security than these Terms, the platform rule controls for that platform data. Customer must not instruct Slate to violate a platform rule. Slate may reject or modify an instruction that would create noncompliance.

17.2 Credentials and developer approvals

Slate's access can depend on OAuth clients, app review, developer tokens, business verification, platform contracts, protected-data review, rate limits, and ongoing compliance. Customer does not receive ownership of Slate's developer credentials and may not copy, inspect, disclose, or use them outside the Service.

17.3 No pass-through warranty

Slate does not provide a warranty or indemnity for a third-party service beyond any right that the provider expressly permits Slate to pass through. Customer's remedy for third-party service conduct may lie against the provider under its terms.

18. Marketing-data and reporting disclaimers

18.1 Source data can differ

Advertising, analytics, ecommerce, and lifecycle platforms can report different numbers for the same activity because of attribution models, windows, identity resolution, consent, time zones, currencies, exchange rates, sampling, thresholding, modeled conversions, invalid-traffic filtering, privacy limits, late events, refunds, chargebacks, API delays, deleted objects, account settings, and provider corrections. Slate does not guarantee that platforms will agree.

18.2 Normalization and calculated metrics

Slate may normalize fields and calculate ratios from base values. A calculated metric is only as accurate as its inputs, definitions, filters, date boundaries, currency treatment, and denominator. Customer must review definitions before relying on a metric. A label such as revenue, conversion, lead, ROAS, MER, CAC, or similar term may have different source-platform and Customer meanings.

18.3 Customer edits

Slate permits manual entries, corrections, exclusions, labels, and rules. Those actions can change reported results. Audit history supports review but does not prove the business truth of a value. Customer is responsible for approvals, evidence, segregation of duties, and reconciliation appropriate to its organization.

18.4 No source-of-truth warranty

Slate is designed to support a controlled source of record, but does not warrant that data is complete, error-free, auditable under a particular accounting standard, compliant with every Customer policy, or suitable as the sole basis for financial statements, tax filings, securities disclosures, lending, compensation, or legal reporting. Customer must perform independent validation for high-impact decisions.

18.5 Alerts and recommendations

Alerts, anomaly notices, pacing, status, and recommended actions can be delayed, incomplete, or false-positive. Customer must not rely on an alert as a substitute for monitoring platform accounts, budgets, billing, security, or legal obligations.

19. Suspension and termination

19.1 Suspension

Slate may suspend or limit access when reasonably necessary to address security risk, suspected unauthorized access, prohibited use, platform violation, legal request, nonpayment, material breach, excessive resource use, threat to the Service, or harm to another Customer. Slate will use reasonable efforts to provide notice and an opportunity to cure when practical and lawful, but may act immediately for urgent risk.

19.2 Termination by Customer

Customer may cancel or terminate as provided in the billing interface or Order Document. Termination does not relieve Customer of accrued payment obligations. A fixed commitment remains payable unless the Order Document permits early termination.

19.3 Termination by Slate

Slate may terminate for material breach that remains uncured after reasonable notice, repeated or serious prohibited use, legal or platform requirement, insolvency, or discontinuation of the Service. Slate may terminate a free, beta, or evaluation account at any time subject to applicable law.

19.4 Effect and data retrieval

On termination, Customer's access and integrations end. Customer should export needed data before termination. Subject to law, platform rules, and the applicable plan or Order Document, Slate may provide a limited retrieval period and then delete or render inaccessible Customer Data under its retention process. Slate may retain billing, security, dispute, and legal records and deidentified statistics as permitted.

19.5 Survival

Provisions that by their nature should survive termination survive, including payment obligations, ownership, confidentiality, restrictions, disclaimers, indemnification, limitations of liability, dispute provisions, and lawful data-retention obligations.

20. Warranties and disclaimers

20.1 Mutual authority

Each party represents that it has authority to enter the agreement and will comply with laws applicable to its performance.

20.2 Service warranty

Slate warrants that it will provide paid production features in a professional and workmanlike manner consistent with generally accepted industry practices. Customer's exclusive remedy for a verified breach is for Slate to reperform the affected service or, if Slate cannot do so within a reasonable period, terminate the affected paid service and refund prepaid fees for the unused portion of that service.

20.3 Disclaimer

EXCEPT FOR THE EXPRESS WARRANTY ABOVE AND TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE, DOCUMENTATION, DATA, CALCULATIONS, REPORTS, ALERTS, BETA FEATURES, AND THIRD-PARTY INTEGRATIONS ARE PROVIDED "AS IS" AND "AS AVAILABLE." SLATE DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, COMPLETENESS, QUIET ENJOYMENT, AND ANY WARRANTY ARISING FROM COURSE OF DEALING OR USAGE OF TRADE.

Slate does not warrant uninterrupted or error-free operation; that every defect will be corrected; that data will match another source; that an integration will remain available; that reports satisfy a legal, accounting, or platform standard; or that the Service will achieve a business outcome.

21. Indemnification

21.1 Customer indemnity

Customer will defend Slate and its affiliates, officers, directors, employees, and agents from a third-party claim, and indemnify them for finally awarded damages, settlements approved by Customer, and reasonable legal fees, to the extent the claim arises from: (a) Customer Data, Customer instructions, or Customer's use of the Service; (b) Customer's violation of law, privacy rights, platform terms, or these Terms; (c) unauthorized account or platform access by Customer; or (d) a dispute between Customer and its User, client, employee, agency, vendor, or data subject.

21.2 Slate intellectual-property indemnity

For a paid Customer, Slate will defend a third-party claim that the unmodified paid Slate Service directly infringes a United States patent, copyright, or trademark, and will indemnify Customer for finally awarded damages, settlements approved by Slate, and reasonable legal fees. Slate has no obligation for claims arising from Customer Data, third-party services, combinations not supplied by Slate, Customer modifications, continued use after notice, compliance with Customer instructions, or use outside the agreement.

21.3 Remedies for infringement

If an infringement claim is likely, Slate may obtain the right to continue use, modify or replace the affected feature, or terminate it and refund prepaid fees for the unused portion. This Section states Customer's exclusive remedy for covered intellectual-property claims.

21.4 Procedure

The indemnified party must promptly notify the indemnifying party, provide reasonable cooperation at the indemnifying party's expense, and allow control of defense and settlement. A delay reduces obligations only to the extent it materially prejudices the defense. No settlement may admit fault or impose non-monetary obligations on the indemnified party without consent.

22. Limitation of liability

22.1 Excluded damages

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES; LOSS OF PROFITS, REVENUE, GOODWILL, BUSINESS OPPORTUNITY, OR ANTICIPATED SAVINGS; OR LOSS, CORRUPTION, OR COST OF RECONSTRUCTING DATA, EVEN IF ADVISED OF THE POSSIBILITY.

22.2 Liability cap

TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH PARTY'S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THE AGREEMENT WILL NOT EXCEED THE GREATER OF: (A) THE FEES CUSTOMER PAID OR OWED TO SLATE FOR THE SERVICE GIVING RISE TO THE CLAIM DURING THE TWELVE MONTHS BEFORE THE EVENT FIRST GIVING RISE TO LIABILITY; OR (B) ONE HUNDRED U.S. DOLLARS IF CUSTOMER USED ONLY A FREE SERVICE.

22.3 Exceptions

The exclusions and cap do not limit: (a) Customer's payment obligations; (b) a party's fraud, willful misconduct, or gross negligence to the extent liability cannot be limited; (c) Customer's violation of acceptable-use restrictions or misappropriation of Slate intellectual property; (d) indemnification obligations to the extent a limitation is prohibited or an Order Document states a separate cap; or (e) liability that law does not permit to be excluded or limited.

22.4 Allocation of risk

The fees and agreement reflect this allocation of risk. Each limitation applies to the maximum extent permitted, regardless of legal theory and even if a remedy fails of its essential purpose.

23. Export controls, sanctions, and anti-corruption

Customer and Users will comply with U.S. and other applicable export-control, sanctions, import, and anti-boycott laws. They will not use, export, re-export, transfer, or provide the Service or technical information to a prohibited person, entity, country, territory, or end use. Customer represents that it is not restricted by applicable sanctions and will not use the Service for prohibited weapons, military-intelligence, or other restricted activities.

Each party will comply with applicable anti-bribery and anti-corruption laws and will not offer or accept an improper payment, gift, or benefit in connection with the agreement.

24. Notices and changes to these Terms

24.1 Operational notices

Slate may send service, security, integration, billing, legal, and account notices by email to the account address, through the Service, or by another reasonable electronic method. Customer must keep administrator and billing contacts current. Email notice is effective when sent unless a mandatory law requires another method.

24.2 Changes to Terms

Slate may update these Terms for legal, security, platform, product, or operational changes. Slate will post the updated version and effective date and will provide advance notice of a material adverse change to a paid subscription when reasonably practical. A material change does not authorize a new use of Google API Data or other data when renewed consent or authorization is required.

24.3 Acceptance of updates

Continued use after the effective date constitutes acceptance to the extent permitted by law. If Customer does not agree, Customer must stop use and cancel before the effective date. A signed Order Document may state that its terms cannot be changed online during the committed term.

25. General provisions

25.1 Independent contractors

The parties are independent contractors. These Terms do not create a partnership, joint venture, agency, franchise, fiduciary, or employment relationship. Neither party can bind the other except as expressly stated.

25.2 Assignment

Customer may not assign or transfer the agreement without Slate's prior written consent, except to a successor in a merger, reorganization, or sale of substantially all relevant assets that is not a direct competitor and agrees in writing to the agreement. Slate may assign the agreement in connection with a merger, reorganization, financing, or sale of substantially all relevant assets, subject to applicable privacy and platform obligations. An invalid assignment is void.

25.3 Subcontracting

Slate may use affiliates and subcontractors to provide the Service but remains responsible for their performance to the extent required by the agreement. Data-processing subcontractors are subject to the applicable DPA and subprocessor process.

25.4 Force majeure

Neither party is liable for delay or failure caused by events beyond reasonable control, including internet or cloud failure, platform outage, labor dispute, natural disaster, epidemic, war, terrorism, civil unrest, governmental action, utility failure, or cyberattack not caused by the party's failure to maintain reasonable safeguards. Payment obligations for services already provided are not excused.

25.5 Waiver and severability

A waiver must be in writing and applies only to the stated instance. If a provision is unenforceable, it will be modified to the minimum extent necessary or severed, and the remaining provisions remain effective.

25.6 No third-party beneficiaries

Except for indemnified parties and as expressly stated, the agreement creates no third-party beneficiary rights.

25.7 Entire agreement

The agreement is the complete agreement about the Service and supersedes prior or contemporaneous proposals, statements, and understandings on that subject. A purchase order is for administrative convenience only; additional or conflicting terms in it do not apply unless Slate signs them.

25.8 Interpretation

Headings are for convenience. "Including" means "including without limitation." A reference to law or platform terms includes amendments. Electronic records and signatures are effective. No ambiguity is construed against a party solely because that party drafted the language.

26. Legal operator, governing law, venue, and publication condition

Until those items are resolved, these Terms are a complete substantive draft but should not be presented as the final public clickwrap agreement. The contracting party must be the actual person or legal entity receiving fees, controlling the Service, entering vendor agreements, and bearing legal obligations.

The selected governing law and venue should match the operator's legal structure, location, customer strategy, insurance, tax posture, and dispute plan. The final legal-notice method must accept formal notices, privacy requests, security reports, and platform communications and must be monitored.

Appendix A. Current integrations and scopes

Appendix B. Platform-specific obligations

Appendix C. Official platform terms reviewed

•   Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy
•   Google Workspace API User Data and Developer Policy: https://developers.google.com/workspace/workspace-api-user-data-developer-policy
•   Google Ads API Required Minimum Functionality: https://developers.google.com/google-ads/api/docs/api-policy/rmf
•   Google Ads API Terms: https://developers.google.com/google-ads/api/terms
•   Meta Platform Terms and Developer Policies: https://developers.facebook.com/terms/
•   LinkedIn Marketing Developer Terms: https://www.linkedin.com/legal/l/marketing-api-terms
•   Microsoft Advertising Policies: https://about.ads.microsoft.com/en-us/resources/policies
•   TikTok Business Products Data Terms: https://ads.tiktok.com/i18n/official/policy/controller-to-controller/privacy
•   Reddit Data API Terms: https://redditinc.com/policies/data-api-terms
•   Shopify API Terms and Protected Customer Data requirements: https://www.shopify.com/legal/api-terms
•   Amazon Ads API documentation: https://advertising.amazon.com/API/docs/en-us/info/api-overview
•   Klaviyo Terms and Privacy Center: https://www.klaviyo.com/legal/terms-of-service
•   Clerk legal resources: https://clerk.com/legal/dpa
•   Vercel DPA: https://vercel.com/legal/dpa
•   Neon DPA: https://neon.com/dpa
•   Stripe Privacy Center: https://stripe.com/legal/privacy-center