Data Processing Agreement

Last updated: November 14, 2026

This agreement supplements the Terms of Service. It takes effect when you accept the Terms or start using the service, whichever is earlier.

1. Parties and scope

This Data Processing Agreement ("DPA") is between the customer ("Business") and Triumph Interactive, Inc. ("Service Provider") for visitor analytics the Business directs us to process. The Service is offered from the United States. Customers anywhere may use it. Each customer is solely and fully responsible for compliance with the laws of that customer's own jurisdiction, including the GDPR and UK GDPR, and for notices, consent, and lawful basis. This DPA is a California Consumer Privacy Act (CCPA/CPRA) service-provider agreement. It is not a GDPR or UK GDPR agreement, it is not a set of Standard Contractual Clauses, and it does not appoint an EU or UK representative. Account, sign-in, and payment information is described in the Privacy Policy.

2. Definitions

  • "Personal information" has the meaning in the CCPA, as amended by the CPRA.
  • "Business" means the customer that decides why visitor analytics are collected.
  • "Service Provider" means Triumph Interactive, Inc., processing that information to provide the service.
  • "Consumer" means a person whose personal information is processed, including a California resident.

3. Our role

We process visitor personal information for the Business, under the Business's instructions, to provide web analytics. We do not sell that information. We do not use it to advertise our own products to the Business's visitors, and we do not combine one customer's visitor data with another's. We do use account and billing information to charge for the service, prevent abuse, and comply with law.

4. What we will and will not do

  • Process personal information only as instructed and as needed to provide the analytics service, keep it secure, and comply with law.
  • Not sell personal information received from the Business.
  • Not retain, use, or disclose visitor personal information for a purpose other than the service, security, and legal duties.
  • Not retain, use, or disclose it outside the direct business relationship, except as the CCPA allows.
  • Not combine it with personal information from other customers, except as the CCPA allows.
  • Tell the Business if we decide we can no longer meet these duties.
  • Let the Business take reasonable steps to stop and fix unauthorized use.

Live tracker, server API, and Measurement Protocol events must be within 72 hours when they are saved at our origin, not merely when they are received or queued. Older events are rejected with event-too-old, never stored as analytics, and never billed. For an event already ACKed by the edge, that age rejection is the documented outage-window SLA exclusion and is one of the four permitted post-ACK refusals named below. Times within five minutes ahead of receipt are accepted as sent, subject to other checks. Times more than five minutes and up to 24 hours ahead are stored at the receive time. Times more than 24 hours ahead are rejected with event-in-future, never stored or billed. The Business must not falsify times or retry ids. Authenticated Google Analytics import is the non-billed historical path, subject to plan access.

Usage counts deduplicate retries that keep the same event id and time. A retry with no stable id can be counted more than once. Per-event billing fingerprints are removed by whole UTC day, during hourly maintenance, after that day's last timestamp expires. That can take longer than 72 hours and does not extend admission. Older disputes use monthly and daily totals and verification digests, not a permanent per-event billing file. Analytics retention and log or backup retention are separate. Imports and supported retroactive settings can still change historical reports.

5. Consumer requests

We will help the Business answer consumer requests we can actually perform:

  • Right to know. Supported access features return available records in their authorized scope and size limits. They do not return every copy in backups, logs, or exports. The Business verifies the consumer and identifies each known visitor id.
  • Right to delete. An account administrator must turn on account-wide API erasure for the site that submits the request. The secret-key API requires deletionScope=tenant and rejects a website-only delete. We process each supplied visitor id across every website in that customer account. Submit each known visitor id separately. A 202 response queues the work. It is not finished erasure. COMPLETED reports a bounded check of request-time events, identities, profiles, affected aggregates, and overlapping async-export revocation, plus an ingestion-watermark check. Ingest retries are limited to 90 minutes, and a short follow-up window rechecks completion. Later collection can create new records. Visitor erasure revokes overlapping async export objects before completion. Backups, noncurrent export versions, operational logs, copies already downloaded by the customer, and billing or audit records are outside this API. We do not claim that every aggregate row is exempt: affected aggregates that carry the identifier are refreshed, or the check finds no materialized data in range. This notice is not a certificate that every copy of personal information is gone.
  • Right to opt out. GPC reduces collection and excludes marked events from conversion forwarding. It does not stop all analytics. The Business provides its own notices. The tracker has no cookie-consent banner and no blanket collection opt-out API.
  • Export. CSV, Excel, JSON, and API export of available analytics data, while the account and data remain accessible, subject to the plan and a 100,000-row cap on each raw JSON request.

6. Categories

  • Identifiers. Visitor id (cookie), session id, and an email hash if the Business sends one. The analytics event does not store a raw IP address. It stores location derived from the IP address and, unless GPC or IP anonymization is on, a server fingerprint. A raw IP can remain in rate-limit keys and operational logs.
  • Internet activity. Pages, referrers, on-site search, clicks, and scroll depth.
  • Location and network. Authenticated Cloudflare headers supply country, region, city, postal code, coordinates, timezone, and ASN. Direct requests and Measurement Protocol IP overrides have unknown location and ASN. GPC removes stored coordinates and postal code and keeps coarser location and ASN. We do not collect device GPS and we do not use a local IP-location database.
  • Device. Browser, operating system, screen size, device type, and language. Unless GPC is on, device fingerprint signals include canvas rendering, WebGL vendor, renderer and capabilities, an audio-processing value, detected fonts, timezone, CPU core count, device memory, touch points, display and browser capabilities, media preferences, math-rendering values, storage availability, and network type and connection estimates. Signals from the first site-session pageview are processed into a device fingerprint for visitor matching, separately from the IP-derived fallback.

Processing includes reports, visitor profiles, attribution, conversion measurement, customer-configured cross-domain and identity linking, and optional conversion forwarding. GPC suppresses linking and fingerprinting, stores the session id instead of the persistent visitor id, and limits the visitor cookie to a rolling one-day expiry. The first pageview, later single-page pageviews, and explicit events continue. Enhanced automatic events are suppressed. Custom or ecommerce content the Business sends may still contain personal information.

7. Subprocessors

We use these subprocessors. We will update this page, and email the account address, at least 30 days before a new subprocessor processes customer personal information. An emergency security replacement may start sooner, and we will disclose it as soon as we reasonably can. You may object by cancelling. That notice is a commitment we will carry out. It is not an automated product feature.

Subprocessor Purpose Data categories Location
Amazon Web Services (AWS) Application and database hosting, networking, cache, S3 exports and backups, logs, and monitoring. Amazon SES SMTP for transactional email and scheduled reports. Account information, visitor analytics, operational records, email recipients, and report content United States (us-east-1, Virginia)
Cloudflare, Inc. Edge network and TLS for customer tracking hostnames (Cloudflare for SaaS custom hostnames), script delivery, IP-derived visitor location headers (country, region, city, timezone and ASN), the outage event queue, R2 replay receipts, and Turnstile browser/network security verification on our account and billing access forms Request IP addresses, URLs, referrers, visitor and event identifiers, event payloads while queued, device context, location and network fields, GPC signals, and replay-receipt status US/global edge network; not exclusively US storage
Stax Card and ACH processing and token vault for customer billing. Live hosted card-number and CVV fields use BlockChyp at https://api.blockchyp.com. Not a recipient of visitor analytics. Billing contact details, payment credentials typed into hosted fields, payment tokens, and transaction records United States. Live hosted card-field origin: https://api.blockchyp.com.

If the outage buffer is on and the origin is down, Cloudflare may hold queued event payloads, including URLs, referrers, identifiers, and IP addresses, for up to 14 days in the main queue and up to another 14 days in the dead-letter queue (28 days total). A queued 202 is a positive ACK and the tracker stops retrying. Eligible events are replayed into our database, and queue messages are deleted after confirmed processing. After that ACK, the only permitted terminal refusals are visitor erasure completed before replay, an event that is more than 72 hours old when it reaches our origin, a site that does not exist, and an event that live intake would itself have refused as invalid. The erasure outcome is equivalent to storing and then erasing the event. The event-age outcome is the documented outage-window SLA exclusion. Other replay failures remain retryable. A queued 202 is a positive acceptance ACK, but the event is saved only after origin persistence. The queue's longer retention does not extend the live 72-hour window. GPC-flagged events are queued like other events, and their opt-out is honored on replay. R2 replay receipts (tenant, website, event id, time, and status) are kept for up to 29 days and are not the analytics record.

Meta, Google Ads, and TikTok conversion recipients are integrations the Business configures. For non-GPC visitors, automatic video tracking can load YouTube and Vimeo SDKs and enable player APIs when those embeds are present on the Business's page, without a separate video-tracking opt-in. Those providers receive the resulting browser requests. They are not required hosting providers. The Business may need its own terms with them.

Cloudflare also provides Turnstile abuse protection for public signup and protected account or billing forms where enabled. Associated data includes request IP addresses, browser and device signals, challenge results, and verification tokens, processed on Cloudflare's global network. Application and primary database hosting is US-based; this agreement does not guarantee exclusively US processing or storage at the edge. Stax may use processor-controlled fraud-prevention services, including Google reCAPTCHA in its frames, independently of our plain SDK selection.

8. Security

  • TLS in transit and encrypted storage at AWS
  • Network isolation
  • BCrypt password hashes, emailed magic links, and optional authenticator codes. No Google sign-in
  • API and ingestion rate limits, plan quotas, and query budgets
  • Automated database backups with point-in-time recovery
  • A high-availability database pair with failover
  • Infrastructure monitoring and alarms

9. Breach notice

If we confirm a security incident that materially compromises customer personal information in our possession, we will notify the Business without undue delay and within 72 hours of becoming aware of it, where the law allows. The notice will describe the nature of the incident, the categories and approximate number of records affected if we know them, the likely consequences, and the steps we have taken. This notice is to the Business, not a promise that we will notify every visitor.

10. Deletion when the account ends

Scheduled account cleanup becomes eligible 90 days after cancellation or a non-trial suspension, or 30 days after a trial-expiry suspension. The job checks eligibility again, deletes events, visitor identities, and profiles, refreshes affected aggregates, and marks completion only after the purge succeeds. Eligibility is not a promised finish date, and it is not erasure of account or billing records. While the service is active, event retention is 14 months for Starter, 26 months for Growth, and 38 months for Pro, Business, and Enterprise. The Business may choose shorter. Self-service plans offer one paid 12-month extension. Other finite extensions or unlimited retention require a negotiated Enterprise contract and a persisted purchased entitlement. Removing a paid 12-month extension lowers the ceiling immediately. Older history then becomes eligible for permanent deletion on the next retention run. Export first. Adding the extension again does not restore deleted history.

Exports are subject to plan limits and a 100,000-row cap on each raw JSON request. Asynchronous CSV and Excel files in S3 expire after 30 days by default (configurable from 1 to 365 days), with a one-day expiry for old versions. Download links last 24 hours by default. Seven days is a signing ceiling, not the default. Visitor erasure revokes overlapping async export objects and deletes those accessible objects before completion. Copies already downloaded by the customer are not recalled. Noncurrent versions keep the one-day expiry above. Backups target weekly full, daily differential, and hourly incremental runs, retaining four full backups and fourteen full or differential backups by count. Four weekly full backups normally span about 21-28 days from the oldest backup's start. Backup chains, the 28-day storage lock, and version expiry can keep copies longer; this is not a hard erasure deadline. Logs have their own retention.

On written request after a completed account purge or a completed visitor-deletion job, we will send a completion notice. The notice names the request, the date, the visitor or account scope, the stores that were checked, the result the job observed, and the stores that were not erased: backups, noncurrent export versions, operational logs, copies already downloaded by the customer, and billing or audit records. A completed visitor deletion includes revocation of overlapping async export objects. A completed account purge does not yet provide that export-revocation guarantee. This notice is not a certificate that every copy of personal information is gone. We do not promise a fixed date by which every backup copy disappears. If we restore a backup, deleted data can return and must be deleted again. We do not automatically return export files. The Business should export before the retention or cleanup window closes.

11. Audits

We will make available the information reasonably needed to show compliance with this DPA. The Business may audit that compliance once per year, on 30 days' written notice, during normal business hours, in a way that does not disrupt the service or expose other customers' data. A copy of this page and the current subprocessor list satisfies a routine documentation request.

12. Contact

Questions, or a request for a countersigned copy: our contact form.

13. Disputes and liability

Sections 16, 23, and 24 of the Terms of Service apply to this DPA: no indirect or consequential damages; Triumph's aggregate liability is capped at fees paid in the twelve months before the claim, subject to mandatory law. Disputes require fifteen days of senior-representative negotiation after written notice, then confidential mediation with equally shared mediator fees. Either party may proceed in court forty-five days after notice if unresolved. North Carolina law applies, excluding choice-of-law rules; CISG is excluded. Exclusive venue is in the state courts located in Wake County, North Carolina, and the United States District Court for the Eastern District of North Carolina, Western Division (Raleigh), where it has subject-matter jurisdiction, with an inconvenient-forum waiver. Small claims and injunctive, preliminary, or provisional relief are carved out of the negotiation and mediation requirement. Reasonable prevailing-party attorneys' fees, costs, and expenses are reciprocal, with court apportionment for distinct claims.