Cop Drop - Privacy Policy

(Last updated on October 24, 2026)

Persoftware SRL, Romania, operates Cop Drop and is the controller of the personal data it processes for the Game and related game services. Contact: persoftware.srl@gmail.com. This notice covers the mobile Game and its Cop Drop legal webpages. Personal data includes account and device identifiers, even when they do not contain your real name. Acknowledging this notice is not consent to optional analytics, personalized advertising, or tracking.

TABLE OF CONTENTS
  1. Age settings and information for families
  2. Accounts, gameplay, and cloud saves
  3. Public player information and Wanted
  4. Photos, permissions, feedback, and notifications
  5. Purchases
  6. Optional analytics
  7. Advertising and privacy controls
  8. Purposes, legal grounds, and recipients
  9. Data access, retention, and account deletion
  10. Your rights and contact
  11. Website, security, and changes

Get your Cop Drop data or delete your account

1. Age settings and information for families

The age screen accepts ages from 1 to 100 and stores an age group on the device: under 13, 13–15, 16–17, or 18 and over. The Game sends this category to our authenticated account service to apply account safeguards. We do not send the exact entered age or a date of birth through this flow. The server also stores Wanted eligibility and any reported under-18 restriction. A recorded under-13 account restriction cannot be removed simply by selecting an older age on the device; contact support for a correction or review.

For players under 16, the Game disables its optional Firebase Analytics and GameAnalytics collection, does not request iOS tracking permission, and signals restricted treatment to advertising services. Players aged 16–17 receive teen ad treatment. For known under-13 accounts, we also disable push registration and delivery, use a generated game alias, and replace email/free-text feedback with predefined bug categories. Authentication, limited cloud progress and online competition remain available. Wanted is separately restricted to eligible adults aged 18 and over; unknown-age and under-18 players cannot use its feed, moments, likes, activity tracking, or social notifications.

The current Game has no flow to verify parental authorization. Entering an age or tapping "Agree and continue" does not establish that authorization. A parent or guardian should review the Game and supervise younger players. Do not provide a real name, contact details, or other private information in public names or posts. Where parental authorization is legally required for a feature or processing, it must be obtained before that use; the age settings alone do not establish legal eligibility.

Parents and guardians can contact us to ask about a child’s data or request its removal. We may need proportionate information to verify the request and locate the account. The safeguards described here are not a claim that all processing involving children is exempt from parental-consent requirements.

2. Accounts, gameplay, and cloud saves

The Game attempts Google Play Games or Apple Game Center sign-in and can use Firebase anonymous authentication for guest play. Optional Google or Apple recovery sign-in can be linked in Account settings. Firebase and the sign-in provider process authentication identifiers and credentials; the Game receives authentication tokens and a game account identifier. Provider profile information, such as a display name and, depending on provider permissions, an email address, may be available through authentication. We do not receive your Google or Apple password.

Our game backend receives a player identifier, account age category, eligible account display name and chosen nickname, avatar selection, scores, ranks, mode and session counts, completed levels, Kingdom activity, selected color, notification settings where available, time offset, and relevant game version information. Known under-13 accounts use a generated alias; provider names are not included in competitive leaderboard or Kingdom player responses. Authentication uses a Firebase account identity; older records may also contain legacy player identifiers.

Cloud saves contain progress, stars, virtual currency, inventory, unlocks, selected skin identifiers, reward and cooldown history, and purchase-fulfillment identifiers. These support save recovery, synchronization, reward delivery, and prevention of duplicate grants. Device audio preferences, the locally stored age group, and consent choices are not copied as part of the game progress snapshot.

Network services receive your IP address when connecting. Hosting, authentication, advertising, and analytics providers may process connection and technical information, including approximate location derived from IP, under their service arrangements. The Game does not request precise GPS location.

3. Public player information and Wanted

Leaderboards, online matches, Kingdom features, and player profiles can reveal your display name, selected avatar, scores, rank, and competitive information to other players. This visibility is separate from optional Wanted sharing and optional analytics. A platform display name may be used when no nickname is set.

For eligible adults, achievements are stored on our servers in My Moments before you choose to publish them. Publishing a moment makes its achievement text, player identifier, display name, avatar, creation/publication dates, likes, and view totals available through Wanted. You can unshare or delete your own moments using the available controls. Automatic Wanted moment creation is disabled for restricted accounts. Existing moments are retained for applicable account/data handling, but are excluded from the public feed when eligibility is unknown or restricted; reported under-18 accounts also have their existing posts unpublished when the restriction is synchronized. Core gameplay progress is separate from Wanted.

For eligible adult accounts, we store likes and viewed-moment records linked to player identifiers to operate the feed, count interactions, avoid repeatedly showing viewed posts, and deliver activity notifications. Liking a moment can make your display name and avatar visible in the likes list. Removing a public post cannot remove screenshots or independent copies made by others. These Wanted interactions are blocked for restricted accounts by the app and backend. Changing the local age setting to adult does not automatically lift a recorded under-18 account restriction; contact persoftware.srl@gmail.com for an eligibility correction or review. The age declaration is self-reported and is not verified proof of adulthood.

4. Photos, permissions, feedback, and notifications

If you choose a camera or gallery image for a custom skin, the Game requests the applicable device access and processes and stores the cropped skin image locally in app storage. The current implementation does not upload the photo or skin image to the game backend or publish it in Wanted. Skin selection and unlock identifiers can be synchronized. Device or operating-system backups may separately include local app files. Camera/gallery access can be changed in device settings. If a local custom-skin image is present, it is included as encoded image data in the personal-data export you choose to save or share. This export does not upload that image to our game backend.

For players aged 13 and over, in-game Feedback sends your message and optional email together with player ID, operating system, device model, screen resolution, memory size, CPU core count, game version, and connection type. Known under-13 accounts instead submit only a predefined bug category, account identifier and game version; their report does not include an email address, free text or device diagnostics. Parents can contact email support for detailed help. Email support processes the address and information sent. Do not send passwords or full payment-card details.

For age-approved accounts aged 13 and over, Firebase Cloud Messaging processes a push token linked to the player account. We store notification preferences and time offset to deliver relevant game notifications, and active-hour counts to choose when to send some notifications. This operational history is separate from optional analytics. Known under-13 accounts do not register for push messaging; stored game push-token links and active-hour counts are cleared when the account restriction is recorded. Notification delivery is also checked by the server. Other players can change notification categories in Game Settings and disable visible notifications through device settings. Turning off visible notifications alone does not delete an account or previously stored messaging data.

5. Purchases

Google Play or Apple processes payment through Unity In-App Purchasing. The current catalog offers consumable Bucks packs and a Kiss Cop item, without an auto-renewing or ad-free subscription. The Game processes product, order/transaction, receipt, price/currency, and fulfillment information returned by the store as needed to deliver purchases and recover pending orders. Fulfillment history is associated with the game save to prevent duplicate rewards.

We do not receive full payment-card numbers from the stores. Store transaction records may remain subject to the store’s retention and refund rules independently of deleting a game account.

6. Optional analytics

GameAnalytics receives the Game’s custom telemetry only when the applicable choices permit it and the player is at least 16. This includes sessions, screens and controls used, game attempts, progression, scores, rewards, virtual economy and purchase events, ad interactions/revenue, performance, and diagnostic events. It uses a randomly generated installation reference stored locally, rather than the game account ID as its custom analytics identity. That reference is pseudonymous, not a guarantee of anonymity. The integration disables GameAnalytics advertising-ID tracking.

Firebase Analytics handles automatic Google/AdMob measurement when separately permitted. The current Game does not send its custom gameplay telemetry stream to Firebase Analytics. The Firebase integration denies ad-storage, ad-user-data, and ad-personalization consent and gates analytics storage and collection on the applicable analytics choice. Firebase authentication and messaging remain separate services.

Optional collection starts only after the relevant consent state resolves with permission. Declining optional analytics does not block gameplay. Missing or failed consent configuration leaves this collection disabled. Withdrawing permission stops future game-controlled collection; resetting local SDK data does not by itself erase records already held on provider systems. Contact us for data-rights requests.

7. Advertising and privacy controls

Google AdMob mediation serves banner, interstitial, and optional rewarded ads. Unity Ads, AppLovin, and ironSource adapters are integrated; actual providers depend on platform and mediation configuration. These providers may process IP address, approximate location, device and app details, advertising identifiers where allowed, and ad requests, interactions, and measurement data. Those data can be personal data and may be combined with other information where the provider’s terms and your permissions allow.

Google’s User Messaging Platform displays applicable regional privacy messages. Ad-serving permission is separate from analytics permission. Under-16 users are marked as under the age of consent and receive child/restricted ad treatment; 16–17 users receive teen treatment. Adapter-specific settings are applied where implemented. Restricted ads can still involve technical data needed to serve and secure ads.

Where the regional privacy-options control is available in Game Settings, use it to review or withdraw the choices presented. You can separately manage iOS tracking permission in device settings and use your operating system’s advertising privacy controls. Refusing tracking or personalization does not necessarily remove ads. iOS tracking authorization alone does not grant optional analytics permission.

8. Purposes, legal grounds, and recipients

We use account, save, competition, and fulfillment data to provide requested game features. Where applicable, the legal ground is performance of the service contract. Security, abuse prevention, reliable operation, and support may rely on legitimate interests where those interests are not overridden by your rights, with particular care for children. Accounting, regulatory records, and valid authority requests may require processing under a legal obligation. Optional analytics and personalized advertising rely on the applicable permissions and consent where required. A contract or legitimate interest does not replace consent when the law specifically requires it.

Recipients include our hosting and database services, Firebase authentication and messaging, analytics providers where enabled, store/payment and sign-in providers, advertising partners, and personnel who need access to operate and support the service. Information may also be disclosed where required by a valid legal request or necessary to protect legal rights. Public game information is available to other players as described above.

Provider information: Google/Firebase: https://firebase.google.com/support/privacy and https://policies.google.com/privacy; Apple: https://www.apple.com/legal/privacy/; Unity, Unity Ads and ironSource: https://unity.com/legal/privacy-policy; AppLovin: https://www.applovin.com/privacy/; GameAnalytics: https://www.gameanalytics.com/trust/privacy-notice. Providers may act as processors or independent controllers depending on the service; their notices describe their own processing.

Providers may process information outside your country, including outside the EEA/UK. Applicable transfers require an appropriate legal mechanism, such as an adequacy decision or contractual safeguards where needed. Contact us for information about the arrangements relevant to your data. This notice does not promise that all data stays in the EU.

9. Data access, retention, and account deletion

We retain account and save data while needed to provide the account and requested features. Support, security, purchase, and transaction records may need different retention periods for their purpose or legal obligations. Deletion can be subject to limited lawful retention, and backups may persist until their normal rotation. We do not promise a fixed automatic inactivity-deletion period.

You can retrieve your data in Settings > Account > My data > Get my data. Linked accounts must complete a fresh provider sign-in; guest accounts use the current authenticated guest session. The JSON export contains your available authentication/profile details, cloud saves and history, your Wanted moments and interactions, feedback, your leaderboard and Kingdom records, and your own active multiplayer-session information. The app adds current-device progress, preferences, age group, available analytics references, and any local custom-skin image. Authentication tokens, passwords, and other players' private records are excluded.

On Android, choose a destination in the system document picker. On iOS, use the system share sheet to save a file or choose a recipient. The backend generates the export on request without keeping an export file. A temporary copy is kept in this app's cache; copies over 24 hours old are cleaned on a later app launch, and app-cached exports are removed during account deletion. Copies you save or share yourself remain under your control. Protect the file because it contains personal information.

To request account deletion, use Delete my data in the in-game account settings, read the consequences, and confirm. Linked accounts complete fresh provider authentication. Apple-linked deletion also uses the platform authorization-revocation process where supported. Your Google or Apple account itself is not deleted. The request covers the game profile, cloud saves/history, Wanted moments and related likes/views, feedback records, leaderboard entries, Kingdom ownership/attack references, active multiplayer-room references, push-token links, and the game's Firebase authentication identity. This can permanently remove progress, virtual currency, and items. Store records and applicable consumer remedies remain subject to store rules and law.

An accepted deletion request is scheduled for 10 minutes later. Account gameplay and ordinary saves are paused. The app retains the sign-in session, local progress and recovery copies during this window so the game can be restored if deletion is cancelled. After scheduling, the app offers Quit. During the 10-minute window, return to the app and choose Cancel deletion to cancel the request and restore the game. Opening the app does not cancel deletion automatically. The app checks server status before restoration; if that status cannot be verified online, it offers Retry or Quit. Once the cancellation window ends, the request can no longer be cancelled and background cleanup may begin.

Deletion runs as a persistent server job, and server failures are retried. The account is reported deleted only after its game-data cleanup succeeds. When the app confirms completion, it signs out and clears the current account's local progress/backups, pending moments, custom-skin files, cached exports, and local analytics references. Device age/privacy choices and audio preferences are retained; backups belonging to other game accounts on the device are not deleted. The app then follows the normal new-player flow. Until completion, keep the app's data and account session so status and any available restoration can be checked on return.

A scheduled or processing deletion job retains the account identifier and information needed to finish cleanup. If deletion is cancelled, an acknowledgement, account reference, and processing timestamps are retained for 30 days to recover interrupted responses and prevent replay of the cancelled request. After completed deletion, the status receipt, hashed account reference, and processing timestamps are retained for 30 days for status and replay protection. These records are then removed by the cleanup job. Previously created infrastructure backups and independently held store/provider records are handled separately; contact us about their applicable retention and any legal exceptions. The in-app flow does not promise to erase copies saved by other people or data retained by independent providers.

Historical GameAnalytics and Firebase Analytics records use installation-based references rather than the game account identifier. When those references are available on this device, the deletion flow retains them for a separate provider-processing request submitted when account cleanup starts. Completion of game-account deletion does not mean those provider-held records have already been erased. Optional analytics collection is paused while deletion is scheduled or processing. If deletion is cancelled, collection may resume according to the existing privacy choices. After confirmed deletion, local SDK data is cleared and collection remains disabled for the rest of that app session. For other installations, provider-held data access, missing references, support emails, or other data outside the game-account export, contact persoftware.srl@gmail.com so the request can be located and handled separately.

If you cannot use the app, email persoftware.srl@gmail.com with the subject "Cop Drop account deletion" or "Cop Drop data request". Include the player/account identifier if available, your nickname, and enough information to locate the account or request. We may need proportionate verification. Do not send passwords or full payment-card details. You may request particular data without deleting the entire account. Uninstalling, clearing local data, signing out, or unlinking a provider alone does not delete server records. We will explain any retained data and respond within the applicable legal deadlines.

10. Your rights and contact

Depending on your location and the applicable law, you may request access, correction, deletion, a copy or portability, restriction, and objection to certain processing, and withdraw consent without affecting earlier lawful processing. You may complain to your local data-protection authority, including Romania’s ANSPDCP: https://www.dataprotection.ro/. Contact persoftware.srl@gmail.com to exercise rights. We may need proportionate verification.

Where applicable US state privacy laws apply, rights can also include opting out of sale, sharing, or targeted advertising, appealing a denied request, and exercising rights without unlawful discrimination. Advertising disclosures can be treated as sale or sharing under some laws even without a cash payment; the treatment depends on the actual provider arrangements and applicable law. Use the available regional privacy choices and contact us for assistance. We do not claim that choosing non-personalized ads alone resolves every state-law requirement.

11. Website, security, and changes

Opening the Cop Drop legal webpages sends ordinary connection information to the website host and to external asset providers used by the page, such as content-delivery networks and image/font hosts. These Cop Drop legal-page sources do not embed a dedicated analytics or advertising tracker. Other ADP Smart webpages and linked third-party sites may have different features; review their notices.

We use safeguards intended to protect information, but no network or storage system is completely secure. Protect your device and linked sign-in accounts. Contact us if you suspect unauthorized access.

We may update this notice as features or processing change. The updated date identifies this version. Material changes and any new consent requirements will be handled as required by law. Current notice: https://adpsmart.com/cop-drop/privacy.html. Terms: https://adpsmart.com/cop-drop/terms.html. Privacy contact and operator: Persoftware SRL, Romania; persoftware.srl@gmail.com.