GOLDEN GATE MEDIA ENTERPRISE

PRIVACY NOTICE FOR APPS

Last Updated: May 25, 2026

This Privacy Notice explains how Golden Gate Media Enterprise, S.L. (“Golden Gate Media Enterprise”, “we”, “us”, or “our”) processes personal data in connection with the mobile applications published under our developer account and the services and features available within those applications.

This Privacy Notice applies when you download, install, access, or use any of our mobile applications, interact with features within the apps, contact us, or otherwise use our services.

Please note that not all of our applications process the same categories of personal data. Certain data processing activities described in this Privacy Notice apply only to specific applications or specific features within the applications. Where this is the case, it is indicated in the relevant sections below.

This Privacy Notice describes:

  • what personal data we collect,
  • how we collect it,
  • for what purposes we use it,
  • the legal bases for processing,
  • how long we retain it,
  • with whom we share it,
  • whether we transfer it internationally,
  • and your rights under applicable data protection laws, including the General Data Protection Regulation (EU) 2016/679 (“GDPR”).

By using our applications, you acknowledge that your personal data may be processed as described in this Privacy Notice.

1) PURPOSES OF PROCESSING PERSONAL DATA

We process personal data for the following specific purposes connected to our mobile location services:

a) Provision and operation of the applications and services

To provide, operate, maintain, and improve our mobile applications and their safety functionalities. This includes mapping real-time locations, calculating coordinates, generating location timelines, managing user connection links, and executing cloud-based circle sharing functions requested by the user.

b) Technical support and user communications

To receive, manage, and respond to support requests, bug reports, technical tracking anomalies, or other direct inquiries submitted by users to our service helpdesk.

c) Maintenance, updates, and security

To maintain, update, troubleshoot, secure, and monitor our location applications. This includes the implementation of anti-fraud controls, protecting telemetry integrity, and resolving raw software crashes or platform abuse events.

d) Analytics and service improvement

To generate aggregated and anonymous statistical insights regarding user distribution, interface activity, network performance patterns, and metric data to improve app user experience.

e) Device features access (such as camera or microphone)

Certain features within our applications may require access to device functionalities such as your precise GPS location services, background location processing, or notifications. Access to these systems is strictly subject to your local operating system device permission parameters, which can be modified at any time.

f) Compliance with legal obligations

To comply with applicable corporate, tax, and legal obligations, preserve necessary records required by law, and respond to binding lawful requests issued by competent public or law enforcement authorities.

g) Advertising, attribution, and campaign measurement

To support commercial monetization models inside designated free versions of our apps. This encompasses delivering relevant ads, monitoring attribution conversions, preventing click fraud, and compiling basic marketing engagement logs in accordance with your explicit consent preferences.

2) CATEGORIES OF PERSONAL DATA WE PROCESS

Depending on the application features, circles, and account tiers you actively utilize, we process the following categories of personal data:

a) Contact and communications data

Information you provide when you initiate support tickets or feedback loops, including your name, email address, connection logs, and the specific text content of your inbound message.

b) User content and files provided through the app

Content you explicitly input, choose to share, or assign within the application workspace, such as custom profile markers, user identifiers, circle naming configurations, and custom destination point tags.

c) Location and geolocation data

To deliver our tracking features, our backend infrastructure dynamically processes precision geographic information derived from your device telemetry.

d) Device and technical data

Information regarding the active terminal equipment used to run the application, including your IP address, device model, operating system version, internal time-zone adjustments, language settings, and system diagnostic crash dumps.

e) Usage data

Information reflecting your operational interactions with the interface, such as activation events, screens viewed, target circle toggles, and feature engagement logs.

f) Advertising and identifiers data

Unique marketing tracking tokens, including Android Advertising IDs (GAID) or Apple Identifiers for Advertisers (IDFA), campaign conversion context indicators, and ad interaction strings handled by authorized monetization SDK builds.

g) Purchase and transaction-related data

Limited metadata sent by the marketplace servers to confirm entry entitlements, including current subscription states (Premium vs. Free status parameters), activation history tokens, and automated renewal confirmations. We do not gather or access payment methods or card metrics.

h) Network and connectivity data

Information relating to your immediate mobile provider environment, such as network type flags (WiFi vs. LTE/5G), data transmission indicators, and connection status details required for constant data sync sync validation.

i) Permissions-based access data

Technical data and location markers captured only when your device platform permission rules explicitly allow foreground or background data tracking blocks to pass execution checks.

2.1) SPECIFIC NOTICE FOR LOCATION, BACKGROUND TRACKING AND TIMELINE DATA

Be Closer: Family location. Our core experience relies inherently on the processing of precise geolocation events to map network connection links and circle timelines.

When you activate location features, the app captures coordinate strings in the foreground (when the application interface is displayed) and explicitly in the background (when the application is closed or not in active use, subject to your device permission configuration). Background location tracking is structurally required to execute automatic safety features, immediate circle check-ins, and ongoing movement tracking.

We do not autonomously share your coordinate history outside your defined user circles. Users invite circle members at their sole discretion, and you retain full structural control over who can view your position or tracking metrics. You can restrict or disable foreground or background coordinate capture instantly via your operating system location privacy panels.

3) DATA WE DO NOT INTENTIONALLY COLLECT DIRECTLY

Our location framework is designed around data minimization. We do not demand structural data targets that are external to the execution of your instant mapping services:

Direct Legal Identity Records

We do not require users to input their full legal name, physical postal address, verified phone numbers, or operational passwords to access standard tracking setups.

Payment information

All digital purchase financial transactions are securely isolated and processed by the authorized platform stores (Apple App Store / Google Play). We do not collect, view, or retain payment cards or banking parameters.

Sensitive personal data

We do not intentionally request or handle special categories of data under Article 9 GDPR, such as medical conditions, religious beliefs, or ethnic markers. Users must refrain from inputting sensitive logs into user configuration fields.

User responsibility regarding third-party data

When you register tracking links or invite circle participants, you are legally responsible for verifying that you possess their explicit authorization to share their coordinate vectors.

4) LEGAL BASES FOR PROCESSING

In accordance with Article 6 GDPR, all data handling blocks inside our systems execute under a confirmed lawful base structure:

a) Performance of a contract (Art. 6(1)(b) GDPR):

We process location points, tracking strings, and transaction confirmations where it is necessary to deliver the application functionality you requested under our terms of service. This applies specifically to:

  • Operating real-time location mapping and circle sync functions.
  • Compiling and presenting historical user movement timelines.
  • Confirming premium subscription tiers and features.
  • Servicing technical support tickets linked to app functionality.

b) Consent (Art. 6(1)(a) GDPR):

We rely on your explicit consent for specialized processing blocks where required under local frameworks. This applies to:

  • Activating high-precision device location and ongoing background location tracking permissions via the native OS prompt windows.
  • Serving personalized in-app advertising tracks and matching tracking identifiers inside ad-supported versions.
  • Initializing optional analytics and marketing package deployments.

c) Legitimate interests (Art. 6(1)(f) GDPR):

We process technical metrics and operational metadata based on our legitimate commercial interests, provided your fundamental freedoms do not override them. This targets:

  • Defending app infrastructure from system abuse, data scraping, and coordinate spoofing.
  • Debugging operational code bottlenecks and capturing crash reports.
  • Restricting visible historical timelines to a rolling 2-day filter window for non-premium accounts to manage data server resources.

d) Compliance with legal obligations (Art. 6(1)(c) GDPR):

We maintain designated system records where local fiscal, statutory, or regulatory compliance mandates necessitate data retention blocks.

5) DATA RETENTION

We enforce strict storage limits under Article 5(1)(e) GDPR, retaining data logs only as long as necessary to fulfill active application purposes:

a) Location and Timeline History Data:

Raw latitude, longitude, and coordinate telemetry points sent to our servers are maintained in our active database architecture for a maximum, strict rolling validation timeline window of up to 60 days (2 months) to populate historical features for authorized premium account users. For users on non-premium tiers, the frontend interface restricts the visible history trace display to a rolling window of 2 days (172,800 seconds) to preserve system data load constraints, while the underlying coordinate blocks expire natively on our servers according to our general 60-day structural rollover parameters.

b) Technical, usage, and analytics data:

Automated device telemetry strings, performance exceptions, and server logging files are rotated regularly and kept for short maintenance cycles up to a maximum period of 30 days before overwrite cycles trigger.

c) Support and communications data:

Communication histories matching helpdesk inquiries are saved for a maximum period necessary to guarantee issue resolution or to defend legal claims, up to statutory limitation caps.

d) Purchase and subscription data:

Enterprise validation records matching in-app entitlements are kept for the lifetime of your operational account run plus necessary periods dictated by tax and corporate accountability laws.

e) Legal and compliance data:

Retained entries managed under compliance protocols are kept for absolute windows defined by applicable legal requirements.

6) WHO WE SHARE PERSONAL DATA WITH

We restrict personal data transfers to verified actors on a strict need-to-know basis:

a) Service providers and processors:

We utilize authorized sub-contractors and cloud platforms to handle processing streams (including database hosting, technical error monitoring, and customer service ticket software) under strict Article 28 GDPR Data Processing Agreements (DPAs).

b) App store and platform providers:

Marketplace structures (Apple/Google) access diagnostic metrics, account flags, and purchase validation numbers independently under their standalone controller rules.

c) Analytics and advertising partners:

For ad-supported applications, technical device tags (IDFA/GAID) and approximate location strings are sent to ad-exchanges or mediation platforms strictly after you clear tracking validation checks via our consent dashboard.

d) Legal and regulatory authorities:

We disclose specific database records if legally bound under a valid court order or official warrant issued by a judicial authority.

e) Corporate transactions:

In the context of assets sales, mergers, or group reorganizations, user metrics are handled under tight confidentiality agreements.

f) Group companies:

Information can be shared with affiliated branches for backend management pipelines, subject to matching corporate compliance baselines.

7) INTERNATIONAL DATA TRANSFERS

Certain integrated network components or hosting regions exist outside the borders of the European Economic Area (EEA). Where your data leaves the European boundary, we safeguard the international transfer path under Chapter V GDPR requirements via:

  • Formal adequacy rulings issued by the European Commission targeting specific destination nations.
  • E.U. Standard Contractual Clauses (SCCs) executed directly with third-party vendors, combined with a dedicated Transfer Impact Assessment (TIA) to check local protection levels.
  • Verified participant certification states under the EU-U.S. Data Privacy Framework.

8) YOUR DATA PROTECTION RIGHTS

In accordance with Articles 15 through 22 GDPR, you possess enforceable legal rights regarding your personal data profile:

Access: You can demand a structured copy of your logged diagnostic attributes and position points matching your active device signature (Art. 15 GDPR).

Rectification: You can demand that incomplete or erroneous entry fields inside our profiles be adjusted (Art. 16 GDPR).

Erasure: You can request that we clear your data footprints from our systems (Art. 17 GDPR). Upon receipt of an account or data erasure request, we execute structural database wipes within a maximum window of 30 days, subject only to minimal legal holds.

Restriction of processing: You can freeze your processing states under specific statutory conditions (Art. 18 GDPR).

Object: You can object to data processing blocks executing under our legitimate business interests (Art. 21 GDPR).

Data Portability: You can request that your technical inputs be returned in a clear, machine-readable arrangement (Art. 20 GDPR).

Withdraw consent: You can revoke any voluntary approval loop at any time without prejudice (Art. 7(3) GDPR).

Lodge a complaint: You can file a formal complaint with a competent supervisory authority, such as the Spanish Data Protection Authority (Agencia Española de Protección de Datos - AEPD).

9) DEVICE PERMISSIONS, ANALYTICS AND ADVERTISING CHOICES

You retain absolute, localized power over the functional data parameters of the application using device system toggles:

Device permissions

You can completely block precise coordinate streaming, restrict location capture to foreground-only environments, or disable system notifications by modifying your device OS settings. Toggling permissions off will limit features that depend on location parameters.

Analytics and advertising settings

You can reset your device advertisement identifiers (GAID/IDFA) or configure tracking restrictions inside your terminal platform preferences to disrupt cross-app identifier networks.

10) SECURITY OF PERSONAL DATA

We deploy appropriate technical and organizational countermeasures to secure high-risk location and identity metrics. These defensive controls encompass end-to-end data encryption across public transport pathways, automated technical access logs, database firewalls, isolated API call check procedures, and strict internal least-privilege permission profiles. While we implement modern security measures to safeguard data paths, no internet-facing architecture is absolutely immune to exposure risks.

11) MINORS

Our portfolio includes family location tools that process location data belonging to minors. We do not knowingly capture or sync information tracking individuals below the legal age of digital consent in their home jurisdiction without verified authorization from a parent or legal guardian. If we identify that a minor's records have bypassed permission checks without a valid consent loop, we initiate strict technical isolation rules and clear the data blocks from our network servers within our 30-day deletion standard.

12) WHO WE ARE

The independent Data Controller responsible for handling the location records and system processing described in this document is:

Golden Gate Media Enterprise, S.L. Calle Malteses, 2, planta 2º, puerta B, Las Palmas de Gran Canaria, Spain.

Email Inquiries: admin@goldengatemediaenterprise.com

13) CONTACT US

If you have any questions about this privacy policy, please contact us at:

Email: admin@goldengatemediaenterprise.com

14) CHANGES TO THIS PRIVACY NOTICE

We update this Privacy Notice periodically to align with our technical software developments, operational backend adjustments, or evolving legal frameworks under the GDPR. When adjustments occur, we publish the updated notice layout inside our live software listings and rewrite the "Last Updated" date at the top of this page. We encourage you to audit this page regularly to trace our location processing lifecycles.