Effective Date: 1 June 2026 · Version 2026.1

Privacy Policy

The 2026 Global Compliance Edition. Covers GDPR, UK-GDPR, CCPA/CPRA, VCDPA, LGPD, PIPL, DPDP Act, NDPA, PIPEDA, APPI, EU Digital Services Act, and EU AI Act disclosures — for every primecodevaultlink iOS, iPadOS, Android, and web application.

Table of Contents

  1. 1. Scope & Application
  2. 2. Data Controller & Representatives
  3. 3. Data Collection (Granularity & Purpose)
  4. 4. Third-Party Data Sharing Architecture
  5. 5. Ad Platforms We Integrate (AppLovin MAX, AdMob, etc.)
  6. 6. Ad Formats Implemented (Splash, Rewarded, Interstitial, Banner)
  7. 7. Global Regional Compliance
  8. 8. Auto-Renewal Subscriptions
  9. 9. AI-Generated Content Disclosure
  10. 10. Children & Age-Gating
  11. 11. Security Measures
  12. 12. Your Rights & How to Exercise Them
  13. 13. Data Retention
  14. 14. International Data Transfers
  15. 15. Changes to This Policy
  16. 16. Contact

1. Scope & Application

This Privacy Policy ("Policy") applies to all applications, software, websites, services and products published, operated or distributed by primecodevaultlink ("we", "us", "our", the "Studio") under the brand name "primecodevaultlink" or any product name within the primecodevaultlink matrix (including but not limited to Pet Health Archive, Home Cost Engine, Offline Language Memory, Wardrobe Inventory Planner, Audio Sheet Archive, and Monthly Spending Analytics), collectively the "Apps" or "Services".

This Policy is published in English. Translations may be provided for convenience; in case of conflict, the English version prevails. This version (2026.1) supersedes all prior versions.

By downloading, installing, registering for, or otherwise using our Apps, you confirm that you have read, understood, and agreed to this Policy. If you do not agree, please discontinue use and uninstall the relevant App.

Our guiding principle: data minimisation, purpose limitation, and local-first storage. We collect only what we need to operate the App, and we keep it on your device whenever technically feasible.

2. Data Controller & Regional Representatives

2.1 Data Controller

The data controller responsible for your personal data is primecodevaultlink, registered at St John's Innovation Centre, Cambridge, United Kingdom. You can reach our Data Protection Officer at privacy@primecodevaultlink.com.

2.2 EU & UK GDPR Representative (Article 27 / UK GDPR Article 27)

For users in the European Economic Area and the United Kingdom, our appointed Article 27 representative can be contacted for any data-protection inquiry. Details are provided on request at privacy@primecodevaultlink.com and are answered within 7 business days.

2.3 Other Regional Representatives

3. Data Collection — Specific Granularity & Purpose

We strictly follow the principle of data minimisation. We collect the following categories of information only to the extent necessary to operate IAA (in-app advertising) and IAP (in-app purchase) systems, to optimise user experience, and to prevent fraud. All data handling complies with global privacy regulations.

3.1 Device Fingerprint & Identifiers

3.2 Network Environment Data

3.3 Behavioural Data (IAA & UX)

3.3.1 Advertising Behaviour

3.3.2 App Logic

3.4 Financial Transaction Data (IAP)

Encryption: all data in transit is encrypted via HTTPS / TLS 1.3. All data at rest is encrypted using AES-256. Access to encrypted data is logged and limited to authorised personnel only.

4. Deep Third-Party Sharing Architecture

To operate IAA, IAP, anti-fraud, and payment-processing flows, we share the minimum data necessary with vetted third-party ecosystems. All sharing follows the principles of minimum necessary, encrypted in transit, fully auditable. We never share sensitive personal information. Each partner's privacy policy governs their downstream use; please consult them for detail.

Category Partner Purpose Data Shared (minimum)
Ad Mediation AppLovin (MAX) RTB bidding, fill optimisation, mediation De-identified device info, ad display / click data
Google AdMobRTB bidding, fill optimisationDe-identified device info, ad display / click data
Unity LevelPlay (ironSource)Mediation, waterfallDe-identified device info, ad display / click data
Meta Audience NetworkAudience match (with consent)De-identified device info, hashed email (if provided)
Pangle (ByteDance)China-region fill & global fillOAID, de-identified device info
InMobiRTB biddingDe-identified device info
Attribution / Anti-Fraud AppsFlyerInstall attribution, fraud detectionDe-identified device info, install attribution data
AdjustInstall attribution, fraud detectionDe-identified device info, install attribution data
SingularInstall attribution, fraud detectionDe-identified device info, install attribution data
Kochava / Branch (optional)Install attributionDe-identified device info, install attribution data
Payment Processors Apple Inc.IAP processing, order validationOrder-related data (no sensitive payment data)
Google LLCIAP processing, order validationOrder-related data (no sensitive payment data)
Consent Management UsercentricsCMP, GDPR / DSA consentConsent state hash, region
OneTrustCMP, consent recordsConsent state hash, region
IAB Europe TCF v2.2TC StringTC String

Each third-party partner has signed a Data Processing Agreement (DPA) and a confidentiality agreement with us, defining the scope, duration, and security responsibilities of data processing. We conduct regular compliance audits; if a partner is found to be non-compliant, we terminate the partnership immediately and pursue any contractual remedies.

Users can view the active third-party sharing list in the App's "Privacy & Data" settings and may opt out of non-essential sharing at any time. Opt-out may reduce ad relevance and certain functionality.

5. Advertising Platforms We Integrate

The following advertising and monetisation platforms are integrated across the primecodevaultlink app matrix. Each is bound by a signed DPA. The list below includes the official privacy-policy URL for each platform; please consult it for downstream use of bid signals.

5.1 Ad Mediation & Header Bidding

5.2 Attribution & Mobile Measurement Partners (MMP)

5.3 Consent Management Platforms (CMP)

For users in the European Economic Area, the United Kingdom, and Switzerland, the IAB Europe Transparency & Consent Framework (TCF) v2.2 standard applies. Our CMP produces a TC String that is propagated through every bid request.

6. Ad Formats Implemented

Below is the complete set of in-app advertising (IAA) formats implemented across the primecodevaultlink app matrix, the disclosure / consent requirements for each, and the frequency / behavioural guardrails we apply.

Ad Format Description Disclosure & Consent Frequency / Behavioural Guardrail
App Open / Splash Ad Full-screen ad served on cold start or foreground resume. Disclosure label "Ad" visible; consent required for personalised variants. Maximum 1 per session; 5-second dismissible skip button (DSA-aligned).
Rewarded Video Ad User-elected full video view in exchange for an in-app reward. "Watch full ad to earn reward" copy mandatory; consent required for personalised variants. Skip button after 5 s (DSA-aligned); server-side reward validation; anti-emulator fingerprinting.
Interstitial Ad Full-screen ad served at natural app transition points (e.g. level end, between screens). Disclosure label "Ad" visible; consent required for personalised variants. Minimum 30-second gap between impressions; never shown on first-launch flow or during checkout.
Banner / Adaptive Banner Ad Inline anchored banner placed within app chrome. Disclosure label "Ad" visible; consent required for personalised variants. Refresh interval capped at 60 s; collapsible on scroll; GDPR / CCPA consent string honoured before bid request.
Native & Native Video Ad Customisable template blending with app chrome — headlines, images, CTAs. Disclosure label "Ad" or "Sponsored" always visible; consent required for personalised variants. Visual style must not mimic in-app UI elements; explicit "Ad" badge at all times.
Offerwall Tapjoy / Fyber style list of partner offers the user can complete in exchange for in-app rewards. Each offer is labelled as sponsored; consent required. Per-country compliance review; anti-fraud throttling; restricted in jurisdictions that prohibit the format (e.g. certain EU member states).
Playable Ad Interactive mini-game preview, often used as a rewarded or interstitial format. "Ad" disclosure visible; consent required. Optional "skip" after 5 s; data-use limited to engagement analytics, not behavioural profiling.

For all formats: where ATT (iOS) or the relevant Android consent (e.g. Privacy Sandbox Topics) is denied, the ad request is sent with allow_tracking = false (iOS) or non-personalised (Android) signals. Personalised ads are never shown to users who have refused consent.

7. Global Regional Compliance

We adapt our data-handling practices to the laws of every region we operate in. Below is the region-specific overview.

7.1 European Union (GDPR) & United Kingdom (UK-GDPR)

7.1.1 Legal Basis

We process your personal data under one or more of the following legal bases, as set out in Article 6 GDPR / UK-GDPR:

7.1.2 EU/UK Representative

See Section 2.2.

7.1.3 DSA Transparency

As required by the EU Digital Services Act (DSA):

7.1.4 Your Rights

You have the right to:

7.2 United States (CCPA / CPRA / VCDPA / State-by-State)

7.2.1 No Sale of Personal Information

We do not sell your personal information to any third party (including advertisers, data brokers, or attribution partners). However, under California CPRA and Virginia CDPA, the act of sharing device identifiers with mediation partners for personalised advertising may constitute "sharing" (cross-context behavioural advertising). Where this occurs, we provide a clear in-app opt-out.

7.2.2 "Do Not Track" / Global Privacy Control

We honour the device-level Do Not Track signal, the iOS Limit Ad Tracking setting, and the browser-level Global Privacy Control (GPC). When any of these signals is present, we suppress all behavioural tracking and serve only contextual or non-personalised ads.

7.2.3 State-by-State Compliance

7.3 Brazil (LGPD)

We comply with the Lei Geral de Proteção de Dados. We collect personal data only after explicit consent, with clear purpose, scope, and method. Brazilian users retain the rights of access, correction, deletion, portability, and consent withdrawal. Brazilian user data is stored on Brazil-region servers; cross-border transfer requires ANPD authorisation or use of standard contractual clauses.

7.4 China (PIPL / DSL / Cross-Border Data Transfer Rules)

We comply with the Personal Information Protection Law (PIPL), the Data Security Law (DSL), the Cybersecurity Law (CSL), and the Provisions on Promoting and Regulating the Cross-Border Data Flows (2024). For users in mainland China, personal data is stored on China-region servers. Sensitive personal information is collected only with separate explicit consent. Cross-border transfer follows security assessment / standard contract / certification as required.

7.5 India (DPDP Act)

We comply with the Digital Personal Data Protection Act, 2023. We collect personal data only with informed consent for a specific purpose. Users may withdraw consent at any time. We have appointed a Data Protection Officer. Cross-border transfer requires MeitY approval for any restricted data category.

7.6 Saudi Arabia (PDPL)

We comply with the Personal Data Protection Law. Saudi user data is stored on Saudi-region servers; cross-border transfer follows NDPA authorisation procedures.

7.7 Other Jurisdictions

8. Auto-Renewal Subscription Transparency

Where a primecodevaultlink App offers auto-renewable subscriptions, we strictly follow Apple App Store and Google Play rules and global regulations.

8.1 Information We Collect for Subscriptions

We collect only the minimum subscription-related data: subscription period, trial-period time remaining, subscription status (active / expired / paused), next renewal date. This is used for subscription management and service provision only.

8.2 Transparency Requirements

8.3 Regional Variations

9. AI-Generated Content Disclosure

Where an App includes AI-generated content (text, audio, image, interactive scenes), the following commitments apply.

10. Children & Age Gating

Our Apps are not designed for or directed at children under 13 (or the higher age of digital consent in the user's jurisdiction: 14 in Spain/Italy, 16 in some EU member states under GDPR, 13 in the US under COPPA, 18 in Korea for certain processing, etc.). We do not knowingly collect personal data from children.

11. Security Measures

We apply industry-standard technical and organisational measures to protect personal data:

12. Your Rights & How to Exercise Them

You may exercise the rights described in this Policy by emailing privacy@primecodevaultlink.com with the subject line indicating the right (e.g. "GDPR Access Request", "CCPA Opt-Out", "LGPD Erasure").

We respond within:

To verify your identity, we may request a minimum of information (e.g. device-installation hash) and will not retain that verification record once the request is closed.

13. Data Retention

Data CategoryRetention PeriodBasis
Personal app content (e.g. pet records, financial entries)Until you delete the App or request deletionUser's device, user-controlled
Encrypted user opt-in backupUntil user revokes (key in user's iCloud / Drive)User-controlled
Server-side anti-fraud / anti-cheat log180 days (anonymised beyond)Legitimate interest, fraud prevention
IAP transaction receipt7 years (tax / accounting obligations)Legal obligation
Support correspondence3 years from last interactionService continuity, complaint handling
Data-subject-request records6 years (regulatory audit)Legal obligation

14. International Data Transfers

Where data is transferred across borders, we use one of the following safeguards:

15. Changes to This Policy

We will update this Policy as needed to reflect changes in our practices or in applicable law. Material changes will be communicated through in-app notification and (where you have provided an email) by email at least 30 days before the change takes effect. The current version is identified by its effective date at the top of this document.

16. Contact

For any question related to this Policy, please contact: