Privacy Policy

1. Who operates Daively

Daively is operated by Sunmait Technologies Ltd, a United States company. Privacy questions and data requests can be sent to privacy@daively.com.

2. Our role

For customer account, access, security and service communication data, we determine why and how the data is used. For mobile measurement data submitted by a customer's applications and connected systems, Daively generally processes that data on the customer's instructions. The customer remains responsible for its end-user disclosures and lawful collection.

3. Data we process

• Account data such as email address, role, sessions and authentication security state.
• Application and integration configuration, including encrypted provider credentials.
• Mobile measurement data such as installation identifiers, event timestamps, app/device context, campaign references and consent metadata supplied by the app.
• Billing and store lifecycle data such as product, transaction, subscription state, value and currency.
• Operational data such as request outcomes, errors, audit records and service health counters.

4. Why we process data

We use data to provide attribution and analytics, reconcile revenue, deliver configured conversions, secure accounts, prevent duplicate or unauthorized processing, diagnose delivery, respond to support requests and maintain the service.

5. Destinations and service providers

Daively sends data to advertising, analytics or messaging destinations only when the customer configures that connection or delivery path. Infrastructure providers may process encrypted storage, network and operational data to host the service. A current subprocessor list is available from the privacy contact before contract execution.

6. Retention and deletion

Retention differs by data class and customer configuration. Sensitive conversion snapshots are scrubbed after final delivery or bounded diagnostic retention. Device-scoped export and erasure operations remove associated measurement data and retain only the minimum revocation evidence needed to prevent later replay from restoring it. Account administrators may request workspace deletion through support.

7. Security

Daively uses encrypted credential storage, signed ingestion paths, role-based access, session revocation, two-factor authentication, request limits and audited administrative operations. No system can guarantee absolute security; suspected incidents should be reported promptly.

8. Changes

We may update this policy as the product, infrastructure or applicable obligations change. Material updates will be reflected on this page with a new effective date.

Effective date: August 12, 2026.