Privacy Policy for Peg Plug
Effective date: 13 October 2026
Previous version. This is the earlier version of the Peg Plug Privacy Policy, effective 13 October 2026, for the adults-only (18+) version of the Game. It is kept for reference. For the planned new game version, see the current Peg Plug Privacy Policy page.
Privacy at a Glance
- Your ordinary game progress is stored locally on your device. There is no account and no cloud synchronization by the Game (Sections 5–7).
- Google AdMob is intended as the advertising platform, and Google's User Messaging Platform (UMP) is intended to manage advertising privacy choices, which you can review and change later within the Game (Sections 8–11).
- Unity Analytics is disabled in the production version of the Game (Section 12).
- Where an earlier Unity Analytics deletion request is still outstanding, the Game may contact Unity services to process it. Unity does not reliably confirm completed deletion; for help, contact play.pegplug@gmail.com (Sections 12 and 23.6).
The full details are set out in the sections below.
1. Introduction
This Privacy Policy explains how personal data is processed in connection with Peg Plug (also referred to as “PegPlug” or the “Game”), a free mobile game developed using the Unity game engine for iOS and Android devices.
This Privacy Policy also covers the associated privacy information website at:
https://bold-global-enterprise.com/pegplug/datenschutz
Peg Plug is intended exclusively for individuals aged 18 or older.
We aim to limit personal data processing, provide appropriate privacy choices, and explain how information may be processed by the Game, the device operating system, and relevant third-party service providers.
Most ordinary gameplay information is stored locally on the player's device. However, certain external providers may process personal data in connection with advertising, privacy preferences, technical service operations, support communications, or website delivery.
The extent of processing depends on the functionality in use, applicable legal requirements, user preferences, device settings, and the relevant service configuration.
2. Data Controller
The controller responsible for the processing described in this Privacy Policy is:
Samuel Bold
Höhenweg 18
77855 Achern
Germany
Privacy and support contact:
play.pegplug@gmail.com
Privacy Policy:
https://bold-global-enterprise.com/pegplug/datenschutz
Peg Plug may be presented under the brand name BOLD GLOBAL ENTERPRISE. This brand designation does not replace the identity of the controller named above.
For questions about this Privacy Policy, the processing of your personal data, or the exercise of your privacy rights, please use the email address provided.
3. Overview of Data Processing
Depending on your use of Peg Plug, the following categories of information may be relevant:
Local gameplay information: Saved progress, completed levels, high scores, in-game credits, settings, locally generated identifiers, and related game-state information.
Age eligibility information: A locally stored status reflecting whether you have declared that you meet the minimum age requirement.
Advertising and consent information: Privacy choices, consent signals, technical identifiers, device information, IP addresses, advertising interactions, and related diagnostic information processed through Google advertising services where applicable.
Unity service information: Technical identifiers and request-related information that may be required to process outstanding deletion requests or previously existing Unity-related service data.
Support information: Your email address, information you voluntarily provide, relevant communication metadata, and any support identifier you choose to include.
Website information: Technical connection data, security information, hosting-related cookies, and information required to deliver the website.
Not all categories apply to every user.
The presence of a software development kit (SDK) or a prepared but disabled feature does not, by itself, mean that every data category described in the provider's documentation is actively collected.
4. Age Restriction
Peg Plug is intended exclusively for adults aged 18 or older.
The Game asks users to declare whether they meet this age requirement.
The age eligibility mechanism is based on self-declaration. It does not involve examination of identification documents, biometric age verification, or official identity checks.
For this purpose, the Game does not request or store a date of birth or exact numerical age.
Instead, a local age eligibility status is stored.
The status is maintained separately from ordinary gameplay progress and is not automatically removed when local game progress is reset.
The purpose of the age eligibility mechanism is to restrict access to the intended adult-only Game.
To the extent the status constitutes personal data, the relevant legal basis under the General Data Protection Regulation (GDPR) is Article 6(1)(f), reflecting our legitimate interest in operating an adult-only service and applying its access restrictions, or Article 6(1)(b) where processing is necessary to provide the requested service under the applicable contractual relationship.
Because age eligibility is not independently verified, we cannot guarantee that every user accessing the Game is actually 18 or older.
Peg Plug is not intentionally directed toward minors.
If you believe that an individual under 18 has used the Game and that personal data has been processed, please contact us using the details provided in Section 2.
5. Local Gameplay Storage
Peg Plug uses Unity PlayerPrefs and related local storage mechanisms to preserve gameplay information on the player's device.
This information may include:
- Saved game progress and current game state.
- Completed and available levels.
- Scores and high scores.
- In-game credits and related gameplay values.
- Game preferences and settings.
- Locally generated identifiers.
- Local backup copies of saved gameplay information.
- Technical information required to restore or continue gameplay.
- Local caches used for gameplay preparation or functionality.
These mechanisms enable the Game to function as intended and allow gameplay progress to be preserved between sessions.
The ordinary gameplay information described above is not automatically uploaded to a developer-operated cloud game-save service in the intended production configuration.
Where the information constitutes personal data, processing necessary to provide the requested gameplay functionality may be based on Article 6(1)(b) GDPR.
Related measures for reliability, integrity, and recovery may be based on Article 6(1)(f) GDPR, reflecting our legitimate interest in providing stable and functional gameplay.
Any separate legal requirements concerning storage of information on a device or access to information already stored on a device also apply.
5.1 No mandatory player registration
Peg Plug does not require players to create or register an account.
Ordinary gameplay does not require players to provide their name, email address, or other direct contact information.
5.2 No active in-app purchases or subscriptions
Peg Plug does not currently offer active in-app purchases or subscriptions.
Previously prepared purchasing components may exist within the software project, but purchasing functionality is disabled in the intended production configuration.
5.3 Security of locally stored information
The Game relies on the operating system's application storage and security mechanisms.
The current local PlayerPrefs implementation does not provide a separate application-specific encryption layer for all stored gameplay information.
Operating-system sandbox protection should not be interpreted as a guarantee that every locally stored value is encrypted or protected against every possible form of unauthorized access or manipulation.
The security of locally stored information also depends on the security and settings of the player's device.
6. Cloud Synchronization and Operating-System Backups
A previously developed custom iCloud synchronization mechanism is disabled in the intended production configuration.
Previously prepared online gameplay synchronization functionality is also disabled.
Accordingly, Peg Plug does not currently provide active developer-operated cloud synchronization for ordinary gameplay progress.
However, device operating systems and platform providers may independently create backups, restore application data, or transfer information between devices.
Depending on the user's settings, this may involve services provided by Apple, Google, or the device manufacturer.
These activities are governed by the relevant platform provider's functionality, settings, and privacy practices.
Disabling Peg Plug's own cloud synchronization does not necessarily prevent operating-system backups.
A local gameplay reset does not automatically erase information contained in existing operating-system or cloud backups.
7. Resetting and Deleting Local Game Data
Peg Plug provides functionality for resetting locally stored gameplay progress.
When the relevant reset function is used, the Game removes the associated active and backup game-save information and creates a new local game state.
A new randomly generated support identifier is created for the new game save.
The reset may remove information including saved progress, high scores, in-game credits, and associated local gameplay records.
However, a local game reset is not equivalent to the deletion of all information associated with the Game.
In particular, a local reset does not automatically:
- Remove the separately stored age eligibility status.
- Erase Google UMP privacy and consent information.
- Delete information previously received or retained by Google or advertising partners.
- Remove existing operating-system backups.
- Delete previously sent support emails.
- Delete information already held by Unity or other external providers.
- Confirm that an external data deletion request has been completed.
Certain information relating to outstanding external deletion requests is stored separately from ordinary gameplay progress and may be preserved across resets and application restarts.
To exercise a broader data protection right, including a request for erasure where applicable, please contact us at play.pegplug@gmail.com.
8. Advertising Through Google AdMob
Peg Plug is designed to support advertising through Google AdMob, Google's mobile advertising service.
Google AdMob is the only advertising platform currently planned for the Game.
Where advertising is enabled, the Game may display:
- Banner advertisements.
- Interstitial advertisements.
- Rewarded advertisements.
Rewarded advertisements are optional. Players may choose to view them in exchange for an in-game benefit.
The availability and type of advertisements depend on the active production configuration, applicable legal requirements, advertising service settings, and user privacy choices.
8.1 Personal data processed in connection with advertising
When Google advertising services are used, Google and participating advertising technology providers may process information such as:
- IP addresses.
- Approximate geographic location derived from technical information.
- Device type and model.
- Operating-system information.
- Application-related information.
- Advertising identifiers, where their use is permitted.
- Other app-, device-, or developer-related identifiers.
- Advertising requests and delivery information.
- Advertising impressions and interactions.
- Clicks, video views, and related activity.
- Technical performance information.
- Crash and diagnostic information.
- Relevant consent and privacy signals.
The exact categories of information processed may differ between iOS and Android.
On Android, relevant identifiers may include the advertising ID, App Set ID, or other identifiers used by Google's mobile advertising services where applicable.
On iOS, Apple's advertising identifier (IDFA) and other device-related identifiers are subject to applicable operating-system requirements.
8.2 Purposes of advertising processing
Advertising-related information may be processed for purposes including:
- Selecting and delivering advertisements.
- Personalizing advertisements where permitted.
- Delivering non-personalized or limited advertisements.
- Measuring advertising impressions and interactions.
- Producing advertising performance reports.
- Managing advertising frequency where permitted.
- Detecting invalid advertising traffic.
- Preventing fraud and abuse.
- Maintaining advertising service security and technical reliability.
8.3 Personalized advertising
Personalized advertising may use information about previous activity or inferred interests to influence the selection of advertisements.
Where consent is required, personalized advertising is permitted only after the applicable consent requirements have been satisfied.
The relevant advertising choices are managed through Google's privacy-management mechanisms.
On iOS, Apple's App Tracking Transparency requirements must also be respected where applicable.
8.4 Non-personalized advertising
Non-personalized advertising does not use previous activity for personalized ad targeting in the same way as personalized advertising.
However, certain non-personalized advertising activities may still involve personal data or technical identifiers.
For example, Google explains that some non-personalized advertising modes may use cookies or mobile identifiers for frequency management and aggregated advertising reporting.
The relevant legal requirements, including any required permission for accessing or storing device information, continue to apply.
8.5 Limited advertising
Google also supports limited advertising modes for certain circumstances where permission to use local identifiers or device storage is unavailable.
The availability of limited advertising depends on Google's advertising systems, the relevant privacy signals, and applicable legal requirements.
Declining personalized advertising therefore does not necessarily mean that no advertisements can be shown or that Google processes no technical information.
8.6 Advertising technology partners
Google AdMob may involve additional advertising technology providers.
Depending on the advertising configuration, participating providers may assist with ad selection, delivery, measurement, fraud prevention, or other advertising-related functions.
The participating providers and the purposes for which they process information may change over time.
Where required by applicable law, information about relevant providers, their purposes, and the available privacy choices is provided through the applicable consent-management interface.
We do not represent the number of participating advertising partners as permanently fixed.
8.7 Legal bases for advertising
Where the GDPR applies, processing that requires consent is based on Article 6(1)(a) GDPR.
Certain processing activities that are legally permitted without consent, including some security or fraud-prevention measures, may rely on Article 6(1)(f) GDPR where the applicable requirements are satisfied.
Some advertising providers may rely on legitimate interests for particular processing purposes and provide corresponding objection rights where permitted.
A legitimate interest does not replace consent where the applicable law requires consent.
Separate rules on accessing or storing information on a user's device also apply, including Section 25 of the German Telecommunications-Digital Services Data Protection Act (TDDDG).
8.8 Further information about Google
Google Privacy Policy:
https://policies.google.com/privacy
How Google uses information from apps using its services:
https://policies.google.com/technologies/partner-sites
Google advertising privacy controls:
9. Advertising Privacy Choices Through Google UMP
Peg Plug integrates Google's User Messaging Platform (UMP) to manage applicable advertising privacy choices.
UMP enables the Game to display privacy messages configured through Google AdMob and to determine whether advertising requests may proceed.
Depending on the user's location and the relevant privacy configuration, the applicable message may offer consent, refusal, or individual choices concerning advertising purposes and providers.
9.1 Consent-information requests
To determine the applicable advertising privacy requirements, UMP may communicate technical, device-related, and consent-related information to Google.
Such communication may occur before the Game requests advertisements.
Consent-management communication must therefore be distinguished from the subsequent collection or processing of information for advertising delivery and personalization.
To the extent processing is necessary for compliance with applicable legal obligations, Article 6(1)(c) GDPR may apply.
Where appropriate, Article 6(1)(f) GDPR may apply to processing necessary to administer privacy choices and maintain a reliable consent-management mechanism, subject to the applicable legal requirements.
Any independent requirements concerning access to information stored on the user's device remain applicable.
9.2 Advertising permission checks
The Game's application-controlled advertising workflow is designed to consider the player's age eligibility and the relevant UMP privacy information before requesting advertisements.
If an essential consent check or required privacy process fails, the application-controlled advertising workflow is designed to prevent further advertising requests.
Google's determination that an advertisement may be requested does not necessarily mean that personalized advertising is permitted.
The type of advertising available depends on the specific consent and privacy signals.
9.3 Changing privacy choices
Your advertising privacy choice is not final. Where these options are available to you, you can reopen the advertising privacy options within the Game at a later time and review, change, or withdraw the choices you made earlier.
Where available, you can review and change your advertising privacy choices from the main menu by tapping the settings gear, then selecting 'Info' → 'Ad privacy'. This opens Google's privacy options interface when advertising is enabled and the relevant privacy options are required and available.
When the privacy options interface is opened, the Game's application-controlled advertising logic invalidates previously prepared advertisements so that outdated advertising requests are not simply reused after a privacy change.
Withdrawal of consent applies to future processing that depends on that consent.
It does not automatically erase information already processed by external providers.
You can also contact us at play.pegplug@gmail.com regarding your privacy rights.
10. Apple App Tracking Transparency
On iOS, certain tracking activities require authorization under Apple's App Tracking Transparency (ATT) framework.
Where Apple's rules require ATT authorization, the relevant operating-system permission must be respected before accessing the IDFA or engaging in tracking covered by the framework.
Consent through Google UMP does not override an ATT refusal.
Likewise, granting ATT permission does not replace any separate consent requirement under applicable data protection law.
Users can manage applicable tracking permissions through their iOS device settings.
11. United States Advertising Privacy Choices
Google UMP supports privacy choices relevant to certain U.S. state privacy laws.
Depending on the applicable legislation and service configuration, users may be offered options concerning the sale or sharing of personal information or the use of information for targeted advertising.
Google's mobile advertising services support privacy signals including the Global Privacy Platform (GPP) and restricted data processing mechanisms.
Peg Plug contains an application-controlled mechanism for opening the relevant advertising privacy options interface. Where these options apply to you, you can reopen them within the Game and change your choices at any time, as described in Section 9.3.
The specific options and legal effects depend on the applicable law, Google's configuration, and the user's choices.
Where applicable, relevant opt-out preferences must be respected in subsequent processing.
Users may also contact play.pegplug@gmail.com regarding applicable privacy requests.
12. Unity Analytics
Peg Plug includes a Unity Analytics SDK integration.
Unity Analytics is disabled in the intended production configuration.
While this configuration remains in effect, Peg Plug does not intend to collect or submit ordinary gameplay analytics through Unity Analytics.
The software project contains prepared analytics events relating to gameplay activities, including:
- Level starts.
- Level completions.
- Active gameplay duration.
- Certain menu or gameplay exits.
- Use of hints.
- Gameplay resets.
- Use of boosts.
The presence of prepared event definitions does not mean that they are actively transmitted in the disabled production configuration.
A separate Analytics consent mechanism has also been prepared.
Consent to Google advertising is independent of any consent relating to Unity Analytics.
12.1 Previously collected Unity information
Some installations may contain information from earlier development, testing, or previously enabled functionality.
Where such information exists, limited communication with Unity services may still be necessary to process an outstanding data deletion request or information relating to a previously existing Unity account.
Disabling ordinary gameplay analytics does not necessarily disable all possible Unity service operations.
12.2 Unity Analytics deletion requests
Peg Plug contains functionality intended to request deletion of relevant previously processed Unity Analytics data.
Such requests may involve technical identifiers required to identify the relevant records.
The Game maintains information relating to outstanding deletion requests separately from ordinary saved gameplay progress.
This allows the application to attempt to continue or repeat relevant SDK deletion operations following a gameplay reset or a later application start.
The implementation is designed to support these operations without enabling ordinary Unity Analytics data collection.
However, the available Unity Analytics SDK interface does not provide a reliable confirmation that every relevant record has been deleted from Unity's servers.
Submission of a deletion request to the SDK must therefore not be confused with confirmed server-side erasure.
Local deletion-request information may remain stored while the relevant operation cannot be conclusively resolved.
If you need assistance with an unresolved deletion request, please contact play.pegplug@gmail.com.
12.3 Unity Analytics retention
Unity's published Analytics documentation distinguishes between different categories of information.
According to Unity:
- Raw Analytics event data is generally retained for 13 months.
- Certain metrics and player-profile data may be retained until an applicable deletion process is completed.
- Unity provides mechanisms for requesting deletion of player-related Analytics information.
These retention descriptions relate to Unity's provider systems and do not mean that Peg Plug currently collects ordinary production gameplay analytics.
Further information:
https://docs.unity.com/en-us/analytics/faq
https://docs.unity.com/en-us/analytics/privacy-and-consent/privacy-overview
https://unity.com/legal/game-player-and-app-user-privacy-policy
13. Other Unity Services and Inactive Integrations
The Game's software project includes components relating to Unity Gaming Services and previously prepared online functionality.
These include components associated with authentication and multiplayer services.
The intended production configuration does not require players to register a Unity account for ordinary gameplay.
Previously prepared online gameplay functionality is disabled.
Where relevant existing account information or outstanding deletion requests remain, the Game may need to communicate with Unity services to handle the associated operation.
Such processing may involve existing player identifiers, authentication-related information, or request information.
The presence of an installed SDK does not, by itself, mean that the associated service actively collects personal data during ordinary gameplay.
14. Technical Diagnostics and Error Handling
Technical errors may occur during gameplay, interaction with the operating system, or communication with integrated SDKs.
The application-controlled production error-handling implementation is designed to use sanitized error descriptions rather than unnecessarily recording raw SDK exception objects.
This measure is intended to reduce the risk of unnecessary information being included in application-controlled diagnostic output.
Unity's Engine and Cloud Diagnostics functionality is disabled in the reviewed project configuration.
However, Google, operating-system providers, and other technology providers may independently process technical, performance, security, or diagnostic information through their own services.
Depending on the provider, this may include information concerning the device, application performance, SDK operation, or technical errors.
Where applicable, legally permitted processing necessary for security or service reliability may rely on Article 6(1)(f) GDPR.
This does not override any independent consent requirement.
15. Support Communications
Players may contact Peg Plug support at:
play.pegplug@gmail.com
If you send a support request, we may process:
- Your email address.
- Your name, if voluntarily provided.
- The contents of your message.
- A support identifier, where voluntarily included.
- Any additional information or attachments you choose to provide.
- Technical communication metadata associated with the email.
The purpose of processing is to receive, investigate, and respond to support requests.
Depending on the circumstances, the applicable legal basis under the GDPR is Article 6(1)(b), where processing is necessary within the relevant service relationship, or Article 6(1)(f), based on our legitimate interest in providing support and resolving problems.
Where processing is necessary to comply with legal obligations, Article 6(1)(c) GDPR may apply.
The support mailbox is operated through Google's email services.
Your selected email provider may independently process your outgoing communications.
15.1 Support retention
Support correspondence is deleted without unnecessary delay after a matter has been conclusively resolved, unless continued retention is justified or required by law.
Exceptions may include statutory obligations or the establishment, exercise, or defense of legal claims.
We delete the correspondence ourselves; the email service does not delete it automatically. Copies held outside our control, for example in your own mailbox or with your email provider, are not covered by this deletion.
Please avoid sending unnecessary sensitive personal information or unrelated confidential information.
16. Local Support Identifier, Clipboard, and Email Drafts
Peg Plug generates a random support identifier locally as part of the saved game state.
The identifier is associated with the corresponding local game save.
It is not automatically transmitted to the support mailbox during ordinary gameplay.
Players may voluntarily copy the identifier to the system clipboard or include it in a prepared support email draft.
The support function does not automatically send the email or attach diagnostic files.
The selected email application may store or synchronize draft messages according to its own functionality and privacy practices.
The device clipboard is controlled by the operating system and may be accessible to other software in accordance with the platform's security rules.
When a local game save is reset and a new save is created, a new support identifier is generated.
17. Privacy Information Website
The Peg Plug Privacy Policy is provided through:
https://bold-global-enterprise.com/pegplug/datenschutz
The website uses hosting infrastructure provided through Lovable and associated technology providers.
When you access the website, technical information is transmitted to the infrastructure delivering the requested pages and resources.
Depending on the relevant systems, this may include:
- IP address.
- Date and time of access.
- Requested URL or resource.
- Browser type and operating system.
- User-Agent and related HTTP request information.
- Technical response information.
- Security-related connection information.
- Information associated with technical errors.
This information is relevant to providing the requested website, maintaining availability, troubleshooting technical problems, and protecting against abuse.
Where personal data is processed for these purposes, the applicable GDPR legal basis is Article 6(1)(f), reflecting our legitimate interest in operating a reliable and secure website, subject to the applicable legal requirements.
Lovable and relevant infrastructure providers may maintain operational, access, security, or error logs.
The corresponding retention periods depend on the data category, relevant purpose, and applicable provider arrangements.
Further information about Lovable:
18. Website Visitor Analytics
Lovable Visitor Analytics was previously enabled on the website.
The functionality was disabled on 12 October 2026.
Following this change, a technical inspection of the published Peg Plug privacy information website found that the previously identified visitor analytics, browser performance measurement, and session replay scripts were no longer loaded.
No corresponding analytics-event or session-replay requests were observed during the tested visit.
We do not intend to operate Lovable Visitor Analytics while the functionality remains disabled.
Information collected before the deactivation may remain subject to the provider's applicable retention and deletion arrangements.
Disabling future collection does not automatically establish that historical provider records have already been erased.
19. Locally Hosted Website Fonts
The website uses the DM Sans and Cormorant Garamond font families.
The relevant font resources are delivered from the website's own domain.
The reviewed published website configuration does not load these fonts directly from Google's external Google Fonts servers.
Accordingly, a separate connection to Google Fonts servers is not required solely to display these typefaces.
20. Website Cookies and Security Technologies
The website uses technical hosting and security infrastructure that may store information in the visitor's browser or access previously stored information.
The following cookies were identified in the reviewed website configuration.
20.1 Cloudflare security cookie: __cf_bm
Provider: Cloudflare
Purpose: Bot management and protection against certain automated or potentially abusive requests.
Validity: According to Cloudflare, the cookie expires after 30 minutes of continuous inactivity.
The cookie may contain information associated with Cloudflare's bot-scoring mechanisms and, where applicable, a security-related session identifier.
Cloudflare states that this cookie supports the operation of its bot-protection services.
The related processing may involve technical request and security information.
Where personal data is processed, the legal basis is Article 6(1)(f) GDPR, reflecting the legitimate interest in securing the website and its infrastructure, subject to the applicable requirements.
Further information:
https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/
20.2 Website deployment cookie: __dpl
Provider: Website hosting infrastructure
Observed function: According to technical tests, the cookie serves the assignment of requests to a website version.
Observed validity: 24 hours.
The value recorded during technical tests contained a deployment identifier, a timestamp, and a signature.
The complete value of the cookie can vary between requests.
An individual assignment of the cookie to a visitor is not verified. Any additional server-side use of the cookie is likewise not verified.
It is not verified that the cookie is used for tracking purposes.
Its exact provider-side implementation and any associated server-side retention arrangements are not fully documented.
20.3 Legal requirements for device storage
Storage of information on a user's device or access to information already stored there is subject to the applicable legal requirements.
In Germany, Section 25 TDDDG generally requires consent for such activities unless a statutory exception applies.
An exception may apply where the relevant storage or access is strictly necessary to provide the digital service expressly requested by the user.
Technical cookies used for website delivery or security must be assessed according to their actual functions.
The fact that a cookie belongs to the website's own domain does not automatically exempt it from applicable consent requirements.
The descriptions above are based on provider documentation and technical observation. They are not a final confirmation that either cookie is exempt from consent, and they do not exclude provider-side functions that are not publicly documented.
21. Recipients and Service Providers
Depending on the processing activity, personal data may be processed by or disclosed to the following providers or categories of recipients:
Google and advertising technology providers: Advertising privacy management, advertising delivery, measurement, fraud prevention, and associated technical services where advertising is enabled.
Google email services: Handling support correspondence sent to the designated support email address.
Unity: Processing relevant requests involving previously existing Unity service information, existing online account information, or outstanding deletion operations.
Lovable: Hosting and operating the privacy information website and related infrastructure functions.
Cloudflare: Website security, bot protection, and relevant infrastructure operations.
Apple and Google platform services: Independent app distribution, operating-system permissions, device functions, backups, restoration, and related platform services.
Email providers selected by users: Handling communications that users voluntarily send using their preferred email applications or services.
External service providers may act as processors for certain operations or as independent controllers for other activities, depending on the relevant processing and legal arrangements.
The listing of a provider does not mean that every user transmits personal data to that provider in every situation.
Information may also be disclosed where legally required or where necessary for the establishment, exercise, or defense of legal claims.
22. International Data Transfers
Peg Plug is intended for international availability.
Certain providers and their service partners operate in multiple countries.
Depending on the processing activity, personal data may be transferred to, stored in, or accessed from countries outside Germany or the European Economic Area.
These countries may include the United States and other locations involved in the relevant advertising, hosting, or technology services.
Unity's published Analytics documentation identifies infrastructure in Belgium and the Netherlands and replication of certain Analytics data in the United States.
Google's advertising services may involve technology providers operating internationally.
Lovable and its relevant infrastructure providers may also process technical information internationally.
Where the GDPR's international transfer restrictions apply, the relevant transfer must be supported by a lawful transfer mechanism.
Depending on the recipient and circumstances, such mechanisms may include:
- An applicable adequacy decision under Article 45 GDPR.
- Appropriate safeguards, including the European Commission's standard contractual clauses under Article 46 GDPR.
- Another mechanism permitted by applicable data protection law.
The applicable mechanism depends on the actual recipient, destination, processing activity, and contractual arrangements.
This list describes the mechanisms that the GDPR permits. It is not a statement that any particular mechanism has been confirmed for every recipient. Where a provider publishes information about its transfer mechanisms, that provider's own documentation applies.
Further information about applicable transfers and available safeguards may be requested through the contact details in Section 2.
23. Data Retention
Personal data is retained for the period necessary for the relevant processing purpose, subject to applicable legal obligations and relevant provider arrangements.
The retention conditions differ according to the category of information.
23.1 Local gameplay information
Ordinary local gameplay information generally remains in active device storage until it is reset, deleted, or otherwise removed through the relevant Game or device mechanisms.
Existing operating-system backups may remain independently.
23.2 Age eligibility status
The locally stored age eligibility status remains separate from ordinary gameplay progress and is not automatically deleted by a gameplay reset.
23.3 Advertising privacy information
Relevant consent preferences and advertising privacy information may remain stored through the applicable Google UMP mechanisms to administer and apply the user's privacy choices.
Provider-side retention depends on the applicable Google service arrangements and legal requirements.
23.4 Advertising-related information
Google and participating advertising technology providers retain relevant information according to their respective purposes, retention policies, and legal obligations.
No single universal retention period applies to every advertising data category.
23.5 Unity Analytics information
Unity Analytics is disabled in the intended production configuration.
Previously processed information, where present, remains subject to the applicable Unity retention and deletion arrangements.
According to Unity's published Analytics documentation, raw Analytics events are generally retained for 13 months.
Certain metrics and player-profile information may be retained under different conditions.
23.6 Outstanding Unity deletion requests
Relevant local deletion-request information may be retained across application restarts and gameplay resets to support further processing.
Such information is not automatically deleted merely because a deletion request has been submitted to the SDK.
The Game does not treat SDK submission as confirmation of completed server-side erasure.
23.7 Support communications
Support correspondence is deleted without unnecessary delay after the relevant matter has been conclusively resolved, unless continued retention is justified or legally required.
Deletion is carried out by us; it does not occur automatically within the email service. We cannot guarantee the deletion of copies held by your own email provider or other parties outside our control. See Section 15.1.
23.8 Website technical and security information
Website hosting and security providers may retain operational, error, and security information for the periods necessary to provide and secure their services, investigate incidents, or comply with applicable legal obligations.
The precise provider-specific retention periods may differ between data categories.
23.9 Website cookies
The Cloudflare __cf_bm cookie expires after 30 minutes of continuous inactivity according to Cloudflare's documentation.
The observed __dpl cookie has a validity period of approximately 24 hours.
23.10 Historical website analytics
Information collected through Lovable Visitor Analytics before its deactivation may remain subject to the provider's relevant retention and deletion arrangements.
23.11 Legal retention obligations
Where personal data must be retained to comply with statutory obligations or for the establishment, exercise, or defense of legal claims, a longer retention period may apply to the extent permitted or required by law.
24. Provision of Personal Data
Peg Plug does not require general player registration.
The age eligibility declaration is necessary to determine access to the adult-only Game.
Local gameplay storage supports the requested gameplay experience and the preservation of game progress.
Providing personal information in a support request is voluntary.
However, without sufficient information about a support issue, we may be unable to investigate or respond effectively.
Advertising privacy choices are governed by the applicable consent-management mechanisms and legal requirements.
Refusing optional advertising consent may affect the availability or type of advertisements.
Ordinary production gameplay does not require players to consent to Unity Analytics collection while that service remains disabled.
25. Data Security
We aim to apply technical and organizational measures appropriate to the relevant processing activities and risks.
Ordinary gameplay information is maintained locally rather than requiring a general player account.
The application's production error-handling implementation is designed to reduce unnecessary exposure of raw SDK exception information.
The application-controlled advertising workflow incorporates relevant privacy and permission checks.
However, no electronic storage or communication system can be guaranteed to provide absolute security.
The protection of locally stored information also depends on the device's operating system, security settings, and backup configuration.
External providers maintain security measures for their own systems and processing activities.
26. Your Rights Under the GDPR
Where the GDPR applies, you may have the following rights, subject to the applicable legal requirements.
Right of access – Article 15 GDPR: You may request information about personal data processed concerning you.
Right to rectification – Article 16 GDPR: You may request correction of inaccurate personal data.
Right to erasure – Article 17 GDPR: You may request deletion of personal data where the applicable conditions are satisfied.
Right to restriction – Article 18 GDPR: You may request restriction of processing under the relevant circumstances.
Right to data portability – Article 20 GDPR: Where the legal requirements apply, you may request relevant personal data in a structured, commonly used, machine-readable format.
Right to object – Article 21 GDPR: You may object to certain processing based on legitimate interests. Where the statutory conditions apply, you may object to processing of personal data for direct marketing.
Right to withdraw consent – Article 7(3) GDPR: You may withdraw consent at any time with effect for the future. Withdrawal does not affect the lawfulness of processing performed before the withdrawal.
Rights concerning automated decisions – Article 22 GDPR: Applicable protections are available in relation to certain decisions based solely on automated processing that produce legal or similarly significant effects.
To exercise your rights, please contact:
Because Peg Plug does not require player registration, we may not always be able to identify a particular record held by an external provider using only an email address or local support identifier.
We may request the information reasonably necessary to identify and assess a relevant request, without seeking unnecessary additional personal information.
We will assess and respond to applicable requests within the time limits required by law.
26.1 Right to lodge a complaint
You may lodge a complaint with a competent data protection supervisory authority if you believe the processing of your personal data infringes applicable data protection law.
The supervisory authority associated with the controller's German location is:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg
Heilbronner Straße 35
70191 Stuttgart
Germany
Website:
https://www.baden-wuerttemberg.datenschutz.de/
You may also contact another competent supervisory authority where applicable.
27. Additional Privacy Rights in the United States
Residents of certain U.S. states may have additional privacy rights where the relevant law applies to the processing activity and to the responsible business.
Depending on the applicable legislation, these rights may include:
- Accessing certain personal information.
- Correcting inaccurate personal information.
- Requesting deletion, subject to legal exceptions.
- Obtaining a copy of relevant personal information.
- Opting out of certain sales or sharing of personal information.
- Opting out of processing for targeted advertising.
- Opting out of certain forms of profiling.
- Appealing particular privacy request decisions where required by law.
Some U.S. state privacy laws define advertising-related sales, sharing, or targeted advertising broadly.
Depending on the applicable law and processing arrangements, disclosure of device identifiers or activity information for advertising purposes may fall within these definitions even where no direct monetary sale takes place.
Where the relevant legal requirements apply, the corresponding rights and privacy choices must be respected.
Peg Plug uses Google's UMP integration to support applicable advertising privacy choices, subject to the relevant configuration and legal requirements.
You may also submit a privacy request by contacting:
We will evaluate requests under the applicable legislation and will not unlawfully discriminate against individuals for exercising statutory privacy rights.
28. Other International Privacy Rights
Individuals in jurisdictions outside the European Union and United States may have additional rights under applicable local privacy laws.
Depending on the jurisdiction, these rights may include access, correction, deletion, restriction, objection, withdrawal of consent, or data portability.
Where such legislation applies to Peg Plug's processing activities, requests will be assessed under the relevant legal requirements.
You may contact play.pegplug@gmail.com with a request concerning your personal data.
29. Children's Privacy
Peg Plug is intended only for individuals aged 18 or older.
The Game uses an age self-declaration mechanism and does not perform formal age or identity-document verification.
We do not intentionally direct the Game toward children or solicit children's personal information.
If we become aware that personal data has been processed in connection with an underage user, we will assess the circumstances and take appropriate steps as required by applicable law.
Parents or legal guardians may contact:
30. Automated Decision-Making and Profiling
Peg Plug does not use ordinary locally stored gameplay progress to make decisions intended to produce legal or similarly significant effects on players.
Where advertising is enabled and legally permitted, advertising technology providers may use automated systems and profiling to select advertisements.
This processing depends on the applicable advertising mode, privacy choices, legal requirements, and the providers' privacy practices.
Ordinary automated advertisement selection does not, by itself, establish that Peg Plug performs automated individual decision-making within the meaning of Article 22 GDPR.
31. Changes to This Privacy Policy
We may update this Privacy Policy to reflect changes to the Game, advertising systems, service providers, data processing practices, or applicable legal requirements.
The current version will be made available at:
https://bold-global-enterprise.com/pegplug/datenschutz
Where applicable law requires additional notification or renewed consent because of a change, we will take the necessary steps.
The effective date will be updated when a revised version becomes applicable.
32. Contact Information
For questions about this Privacy Policy or requests concerning your personal data:
Samuel Bold
Höhenweg 18
77855 Achern
Germany
Email: play.pegplug@gmail.com
Privacy Policy:
https://bold-global-enterprise.com/pegplug/datenschutz
Back to home