0/2000 characters

This Usage Agreement ("Agreement") governs Kubian's disclosure of the project-scoped permanent device identifier (user_account_id) to you, the requesting developer, on behalf of the project identified in this request.

1. Scope of grant. Access is read-only and limited to the approved purposes declared in your request. The identifier is scoped to this project only and is not correlated across other applications on the platform.

2. Your responsibilities. You are responsible for your own collection of, access to, use of, disclosure of, retention of, and protection of data derived from the identifier, in compliance with this Agreement and all applicable laws and regulations. Kubian remains responsible for its own security obligations with respect to the systems it operates.

3. Prohibited use. Advertising, ad tracking, marketing, profiling, sale of data, cross-app correlation, or any purpose not expressly approved is prohibited and constitutes grounds for warning, restriction, revocation of access, or termination of the project.

4. Audit trail. An ACCESS GRANT record is created for this disclosure, capturing the project, developer account, approved purposes, agreement version, approval date and expiry. Access expires one (1) year after approval and must be renewed.

5. Revocation. Kubian may issue warnings, restrict, revoke access, or terminate the project at any time for violation of this Agreement, with or without prior notice where required by law or to protect users.

By accepting, you acknowledge that the identifier permanently identifies a specific device, never rotates, and that loss of access may affect features in your application that rely on it.

Because the identifier is permanent and device-bound:

a) You must disclose its existence, your approved purposes, and your stated retention period in your application's own privacy policy before shipping the integration.
b) You may not attempt to correlate the identifier across different applications, or with data obtained outside this project.
c) Upon a user erasure/deletion request concerning your service, you must disassociate all data derived from the identifier from that user within your stated retention commitments; management of the identifier itself remains with Kubian.
d) You must apply reasonable technical and organizational measures to protect data derived from the identifier, consistent with your stated retention period.

Acceptance of both agreements is recorded in the audit trail together with your account, the project, and the agreement version.