← Attriloop

Terms of Service

Last updated: July 6, 2026 · Attriloop is an active-development prototype in private beta.

These Terms govern access to Attriloop unless a signed agreement, order form, or data processing addendum says otherwise. If you use Attriloop for an organization, "you" means that organization.

Beta/prototype notice: Attriloop is not a finished general-availability product. Features, SDKs, APIs, schemas, attribution logic, integrations, retention behavior, subprocessors, security controls, limits, and documentation may change, break, be removed, or be replaced while the service is in beta.

1. The service

Attriloop provides mobile attribution and analytics tools for app teams: tracking links, SDK ingest, install attribution, in-app event analytics, exports, and optional postbacks to advertising and revenue platforms. The service is currently a prototype and should be treated as an early-access beta.

Attribution can rely on deterministic signals, privacy-preserving network postbacks, and limited probabilistic matching. We do not guarantee that every install, purchase, or campaign will be attributed, accepted by an ad network, or reported without delay, especially while beta behavior is still changing.

2. Accounts and access

Access is invite-only during beta and may be limited, changed, paused, or revoked as the prototype evolves. You are responsible for your users, account credentials, SDK keys, export keys, and any activity under your organization. Export keys must not be embedded in client apps. Tell us promptly if you believe a credential has been exposed.

3. Customer data and permissions

You control the apps, SDK configuration, tracking links, events, and integration settings you send to Attriloop. You are responsible for having the rights, notices, consents, and platform permissions needed to collect and process that data, including App Tracking Transparency, app store rules, ad network terms, and privacy laws that apply to your users.

Do not send sensitive personal data, children's data, health data, precise location, payment card data, or government identifiers unless we have expressly agreed in writing that the service supports that use case. Do not rely on the beta prototype for production-sensitive or regulated workloads without a signed production agreement and data processing addendum.

4. Acceptable use

You may not use Attriloop to:

• track people without a lawful basis or required consent;
• circumvent App Tracking Transparency, consent choices, platform policies, or opt-out signals;
• send data you are not permitted to share;
• probe, overload, scrape, reverse engineer, or bypass rate limits and access controls;
• ship server-side or export credentials in public client applications; or
• use the service for malware, spam, fraud, or unlawful activity.

5. Integrations and postbacks

If you enable an integration, you authorize Attriloop to send the configured events, attribution fields, and matching signals to that provider on your behalf. You are responsible for the provider's terms, data-use restrictions, and disclosure requirements. Integration behavior and supported fields may change during beta.

6. Billing

Attriloop is currently operated for internal use and is not billed, and no third-party payment processor is integrated. Any future commercial terms, pricing, and payment processing will be set out in a separate order form before they take effect.

7. Ownership

You retain ownership of your apps, links, event data, and customer data. Attriloop retains ownership of the service, software, documentation, aggregated benchmarks, and product improvements. You grant us the limited rights needed to operate, secure, support, and improve the service.

8. Beta prototype changes and availability

During beta, almost any part of the prototype may change, including the dashboard, SDKs, APIs, endpoints, event names, attribution rules, schemas, limits, pricing, retention periods, subprocessors, and availability. We may suspend or limit access if needed to protect the service, comply with law, prevent abuse, address non-payment, or avoid harm to users, customers, or third-party platforms.

9. Privacy and security

Our handling of personal data is described in the Privacy Policy. We use technical and organizational safeguards appropriate for a beta SaaS product, but no system can be made perfectly secure.

10. Disclaimers and liability

The service is provided "as is" as an early prototype during beta. To the maximum extent permitted by law, Attriloop disclaims implied warranties and is not liable for indirect, incidental, special, consequential, or lost-profit damages. Our aggregate liability is limited to the fees paid for the service in the three months before the event giving rise to the claim, unless a signed agreement states a different limit.

11. Termination

Either party may stop using the beta service. After termination, your access may end, but provisions about payment, confidentiality, data, ownership, disclaimers, and liability continue where they reasonably should.

12. Contact

Questions about these Terms: contact your Attriloop account owner or email legal@attriloop.com.