Privacy Policy

1. Our Core Privacy Invariant

At

Traditional ad-tech networks force developers to inject tracking SDKs directly into utility applications—harvesting location data, device identifiers, and background telemetry.

2. The Three-Tier Architecture

To understand our privacy posture, it is important to distinguish the three layers of the

3. Information Collected via the Developer Portal

When you interact with the developer portal at adxiety.com, we may collect:

• Account Identification: When the new server flow is activated, Google issuer and subject identify the account; verified email is a mutable display label. The server validates a nonce-bound ID token and stores a minimal owner workspace and revocable session. Display name and contact preference are supplied by the developer. An authenticated account can view its own nonsecret issuer, subject and workspace reference for private operator reconciliation; this is not a public identity receipt.
• Application Configuration: Android package claims, app names/descriptions, profile information, private icons/screenshots normalized from PNG or JPEG and separate environment settings are stored as unverified drafts. No ownership or runtime trust is established. No Play access is requested by this draft flow; future website-code verification must establish app-to-website association before production activation.
• Private draft assets and historical records: Prepared storage uses a private object bucket with authenticated workspace-scoped reads. Your browser prepares PNG/JPEG images with orientation and color conversion. The server validates and re-encodes PNG pixels and removes metadata; unsupported formats and animation are rejected. Browser decoding is not a server security boundary. Replaced assets remain private and count against quota until removed. Unknown uploads retain quota until recovery fences the attempt and confirms a storage marker. Recovery permits a new slot attempt without trusting a timeout. Permanent zero-byte markers prevent late writes; up to 128 recovery records are retained per workspace, with no automatic purge. Legacy unconditional uploads and exhausted recovery capacity require scoped review. Historical registration evidence/audit records remain intact; this new flow cannot promote them or publish drafts.
• Website Requests: Cloudflare Pages and Functions handle requests to this website. Hosting providers may process request metadata, such as IP addresses, requested URLs and response status codes. This does not establish which logs Adxiety collects or retains, or that request data is anonymized. We do not represent anonymized telemetry or rate limiting as verified features of this website.

4. Cookies, Local Storage & Do Not Track Signals

The new workspace uses a Secure, HttpOnly, host-only session cookie and a short-lived login-binding cookie. Its profile, app and draft authority is server-side, not browser roles or local storage. The offline implementation uses a proposed isolated D1 namespace; deployment and live operation have not been qualified here. Legacy portal versions stored developer profiles/preferences (including email, organization and payout fields), app portfolios/configuration and local deletion-request records in browser storage. Those records may contain personal information, remain untouched and are not imported into the new workspace. Signing out does not erase legacy browser records; closing a tab does not expire them. A browser deletion marker is not proof of remote erasure. No new analytics or ad tracking is enabled by this change.

C14 qualification diagnostics: The prepared sign-in flow keeps a bounded trial summary in page memory across client-side navigation: operation labels, response status, success flags and a start time. It contains no account identifiers, tokens, cookies, profile or draft contents and sends no additional diagnostic requests. Session storage holds only a nonpassing marker with the start time, never a passing summary or resumable history. Same-origin scripts can read this nonsecret marker. It prevents reuse after observation failure, reload or sign-out, is rejected after 45 minutes and is discarded on the next access. Reloading or losing the module makes the measurement incomplete; storage recovery does not restore it. A completion summary remains only in page memory until page loss or expiry for explicit owner reporting; no automatic upload is added. Browser suspension or session restoration does not guarantee physical erasure at a deadline. Existing legacy storage remains untouched. Hosting and Google may process their own request metadata; this is not a no-logging guarantee.

CalOPPA & GPC Signals: Because our website does not engage in cross-site tracking or third-party behavioral profiling, our web services do not alter their operation upon receipt of browser "Do Not Track" (DNT) or Global Privacy Control (GPC) signals.

5. Third-Party Processors & Infrastructure

The website uses Cloudflare hosting and Google sign-in; the companion includes separate advertising libraries. Their roles are described below:

• Cloudflare, Inc.: Provides website hosting and request handling through Cloudflare Pages and Functions. The new private API proposes D1 for sessions, workspaces and drafts, plus a private R2-compatible bucket for new draft images, but this offline implementation is not evidence of deployed resources or provider log settings.
• Google Identity Services: Provides secure authentication for developer sign-in without Adxiety ever storing your raw account passwords.
• Third-Party Demand & Mediation Networks: Certified demand partners (including AppLovin MAX, Unity Ads, and Liftoff) are integrated strictly within the optional [ad]mit companion hub for rewarded video delivery. Demand partner data processing is governed by their respective privacy policies and SDK disclosures.

6. European Data Protection Rights (GDPR & UK GDPR)

For developers and users located in the European Economic Area (EEA) and the United Kingdom, we process personal data in accordance with the following framework:

• Lawful Basis for Processing: We process developer account credentials under Contractual Necessity (Art. 6(1)(b) GDPR) to deliver portal services; draft configuration is not a published edge rule. For processing of server request metrics or IP logs to maintain system availability and prevent malicious abuse, our stated basis remains Legitimate Interests (Art. 6(1)(f) GDPR); this does not establish that particular logging or anonymization features are deployed. The optional [ad]mit companion is intended to use contextual-only advertising, not personalized targeting. Applicable vendor privacy and consent configuration must still be established and verified before live companion advertising. This design intention is not proof of effective non-personalization or an exemption from consent requirements. Completing companion onboarding is not vendor consent.
• Deletion Status and Retention: Visiting an account-closure or confirmation page does not confirm that a deletion request was received or completed, that credentials were revoked, or that stored records were purged. The page does not establish a purge deadline. For new portal state, the approved operational policy is eight-hour session inactivity (measured from authenticated mutations), a 24-hour absolute session limit, five-minute login nonces and 60-minute challenges. The maintenance template prunes diagnostic attempts and their request audit 30 days after attempt expiry; confirmed-attempt diagnostics are pruned only when host provenance survives. Disconnected detailed evidence/drafts are pruned 90 days after disconnect. Active registration keeps minimal provenance. Consumed-campaign, package-conflict and unresolved-execution workspace fences survive diagnostic cleanup until separately approved disposition. Cancelling a request or signing in again does not prove remote completion or remove an uncertainty hold. Maintenance is not yet deployed. A configured pilot admission cutoff closes new sign-ins and authoring; valid-session status, cancel, logout and disconnect remain available until full portal disable. A timeout or cancellation does not prove remote work stopped. Disconnect does not revoke a Play grant, erase legacy data or cancel already issued offline benefits. Contact us for requests requiring review; no automated account-erasure or transfer service is promised. These limits do not change statutory rights.
• Your Statutory Rights: You have the right to access, rectify, port, or request erasure of your developer data, or object to specific processing activities.
• Right to Lodge a Complaint: If you believe our data processing violates statutory regulations, you have the right under Art. 77 GDPR to lodge a complaint with your local Data Protection Supervisory Authority (such as the CNIL in France, the BfDI in Germany, or the Information Commissioner's Office in the United Kingdom).

The SDK's lack of networking does not establish that a host application, companion, vendor library or portal holds no personal data. Requests concerning data must be assessed against the relevant implementation and records; an SDK integration or a visit to a preview page is not an erasure result.

7. California Privacy Rights (CCPA & CPRA)

Under the California Consumer Privacy Act as amended by the California Privacy Rights Act:

• No Sale or Sharing of Portal Data: We do not sell, rent, or share personal information collected through this website with third parties for monetary or other valuable consideration, nor do we disclose it for cross-context behavioral advertising.
• No Sensitive Personal Information: We do not collect or process sensitive personal information (such as precise geolocation, financial credentials, racial or ethnic origin, or health data).
• Companion App Ad Controls: In the optional [ad]mit companion application, rewarded video ads are served by third-party ad networks (e.g., AppLovin MAX, Unity Ads, Liftoff), which may use device advertising identifiers (GAID) according to their own privacy disclosures. Users can opt out of personalized ad targeting or reset their device advertising identifier at any time through their Android system settings (Settings > Google > Ads).

8. Children's Privacy (COPPA)

The

We do not knowingly solicit, collect, or process personal information from children under the age of 13 (or under 16 in applicable European jurisdictions). If we become aware that personal information of a child has been inadvertently submitted to our portal, we will take immediate steps to delete such data from our databases.

9. Contact Information

For questions about this Privacy Policy or to submit a data deletion request, please reach out to us at: