Download

Privacy policy

Effective date: 3 September 2026
Last updated: 3 September 2026
Policy version: nearzu-privacy-2026-09-03

This Privacy Policy explains how Nearzu d.o.o., with its registered office at, Slovenia (“Nearzu,” “we,” “us,” or “our”), collects, uses, stores, shares, and protects personal data when you use:

  • the Nearzu mobile application;
  • Nearzu websites, including https://nearzu.com/; and
  • related features, content, customer support, subscriptions, and services.

Nearzu is the controller of the personal data described in this Privacy Policy unless stated otherwise.

Privacy contact: [INSERT WORKING PRIVACY EMAIL ADDRESS]
Support: https://nearzu.com/support/
Account deletion information: https://nearzu.com/account-deletion/

1. Important privacy summary

Nearzu is a social discovery and community application for users who meet the applicable minimum age requirement.

  • Nearzu does not allow users under 13 to create or use a social account.
  • Users aged 13–17 and users aged 18 or older are separated into different safety cohorts for people discovery and applicable social or messaging features.
  • Additional verified parent or guardian authorization may be required where local law requires it.
  • Location permission is optional and foreground-only. Nearzu does not use background location.
  • Nearzu does not display another user’s current GPS position, approximate GPS position, movement, route, location timestamp, or user-location pin on the Explore map.
  • Nearzu does not provide public manual check-ins or automatic check-ins.
  • “People in your area” uses a broad area selected or confirmed by the user, not live GPS-to-GPS proximity matching.
  • Profile discoverability is a separate control and is disabled by default when a discovery area is first saved.
  • Usage analytics and diagnostics are optional and disabled until the user provides the relevant consent.
  • Nearzu does not sell personal data and does not use personal data for third-party behavioural advertising or cross-app tracking in the current version of the Service.
  • Users can block and report other users, withdraw optional consent, clear their broad discovery area, disable discoverability, and delete their account.

2. Scope of this Privacy Policy

This Privacy Policy applies to personal data processed through the Nearzu app, Nearzu websites, and related services.

It does not govern independent third-party services that you access outside Nearzu. Third parties such as Apple, Google, and app stores process some data under their own privacy policies when you use their accounts, devices, maps, operating systems, payment services, or stores.

3. Personal data we collect

The data we collect depends on the features you use, your device permissions, your age, your settings, and whether you provide optional consent.

3.1 Account and authentication data

When you create or access an account, we may receive or process:

  • your name;
  • email address, including an Apple private relay address where applicable;
  • account or authentication identifier;
  • authentication provider, such as Apple or Google;
  • profile image supplied by an authentication provider, where available;
  • sign-in, session, token, and account-status information; and
  • records needed to prevent unauthorized access, fraud, or abuse.

Nearzu does not receive your Apple ID or Google account password.

3.2 Age, age-assurance, and guardian-authorization data

We process age-related data to enforce eligibility and safety controls. This may include:

  • date of birth;
  • a platform-provided age range or age signal, where available;
  • an internally derived age band, such as under 13, 13–17, or 18+;
  • whether age assurance has been completed;
  • whether parent or guardian authorization is legally required;
  • guardian-authorization status, such as required, pending, approved, denied, or revoked; and
  • limited verification records needed to demonstrate that authorization was obtained.

Your exact date of birth is not displayed in public profile or people-discovery results.

3.3 Profile and social-account data

Depending on what you choose to add, we may process:

  • display name and username;
  • profile biography;
  • profile city or other broad place label;
  • interests;
  • status;
  • car model;
  • relationship status;
  • avatar and profile photographs;
  • other photographs you upload;
  • profile-completion status;
  • friends, follows, friend requests, blocks, and related social connections; and
  • your discoverability and privacy preferences.

A city or place label that you voluntarily publish as profile content is separate from the private broad-area record used by “People in your area.”

3.4 User-generated content and communications

When you use social features, we may process:

  • posts, comments, reviews, reactions, and wall content;
  • events, event participation, event descriptions, and event media;
  • groups, group membership, group invitations, and group media;
  • places or waypoints you create, save, review, or interact with;
  • direct and group messages;
  • message delivery and read-status information;
  • photographs, video, audio, voice messages, stickers, and other media;
  • replies, reactions, and content metadata; and
  • records of edits, reports, removals, and moderation actions.

Messages and other user content are processed to deliver the requested feature, maintain conversations, protect users, investigate reports, and enforce our Terms and Community Standards.

Do not include highly sensitive personal data in public profile fields, posts, events, groups, reviews, or messages unless it is necessary and you understand who can see it.

3.5 Location and broad-area data

Nearzu may process location-related data only as described in Section 7.

Depending on your choices, this may include:

  • temporary foreground device coordinates used to centre your own map;
  • temporary foreground coordinates used to find public places or events;
  • temporary foreground coordinates used once to suggest a broad city, municipality, region, or sufficiently broad district;
  • the broad discovery area you manually choose or confirm;
  • your country code and broad region associated with that area;
  • location-permission status; and
  • the time when a discovery-area preference was changed.

Nearzu does not use a saved broad discovery area as proof that you are currently physically present there.

3.6 Camera, photo-library, and microphone data

With your device permission, Nearzu may access:

  • a photo or video you select;
  • a photo or video you capture in the app; and
  • microphone audio you intentionally record for a voice-message or other audio feature.

Nearzu does not access your entire photo library merely because you select an individual item. The precise scope of access depends on the permission option provided by your operating system.

Uploaded media is processed, re-encoded, and assigned a generated filename where supported to reduce unnecessary metadata and exposure of original filenames.

3.7 AI-avatar data

AI-avatar generation is optional and requires a separate, explicit consent before the source selfie is provided to the AI service.

When you request an AI avatar, we may process:

  • the selfie you select or capture;
  • visible facial appearance and other visual features needed to create the requested stylized avatar;
  • your selected outfit or style option;
  • the version and time of your AI-processing consent;
  • a temporary signed link to the source selfie;
  • an AI-generation request or prediction identifier;
  • processing status and technical error information; and
  • the generated avatar image.

Nearzu uses the selfie for avatar generation, not for facial recognition, biometric authentication, or uniquely identifying you.

The temporary source selfie stored by Nearzu for this feature is scheduled for removal after the avatar request completes or fails. The generated avatar remains in your account until you replace it, remove it, or delete your account, subject to backup and legal-retention limits.

3.8 Device, network, and security data

We and our service providers may process technical data needed to operate and secure the Service, including:

  • IP address;
  • device type, operating system, language, and app version;
  • session identifiers;
  • request timestamps and network information;
  • authentication and security events;
  • rate-limit and abuse-prevention records;
  • app configuration and feature availability;
  • push-notification token after notification opt-in; and
  • server and application logs.

3.9 Optional usage analytics

If you enable Usage Analytics, we may collect limited information such as:

  • screens or features used;
  • feature area;
  • app version and operating platform;
  • session identifier;
  • interaction type;
  • limited allow-listed metadata, such as content type, media type, surface, or whether a feature was used; and
  • aggregated product-performance information.

Usage Analytics is not intended to include message text, message media, photographs, exact age, date of birth, raw coordinates, discovery-area values, authentication tokens, original filenames, or server-response bodies.

Usage Analytics is disabled until you consent and can be disabled later in Privacy & Data settings.

3.10 Optional diagnostics

If you enable Diagnostics, we may collect crash and error information such as:

  • crash reports;
  • stack traces;
  • error type;
  • app version;
  • device or operating-system information;
  • affected feature area; and
  • limited technical context needed to investigate reliability issues.

Diagnostics is not intended to include message content, uploaded photographs, raw coordinates, date of birth, or authentication credentials.

Diagnostics is disabled until you consent and can be disabled later in Privacy & Data settings.

3.11 Notifications data

If you enable notifications, we may process:

  • notification permission status;
  • device push token;
  • notification preferences;
  • event-alert preference;
  • delivery status; and
  • information necessary to generate the requested notification.

You can disable notifications in Nearzu or in your operating-system settings.

3.12 Subscription and purchase data

If you purchase or restore a subscription, we may receive:

  • app-store account or transaction identifier;
  • product and subscription identifier;
  • purchase date;
  • renewal, expiration, cancellation, refund, or billing-status information;
  • receipt or validation data;
  • entitlement status; and
  • limited technical information needed to restore purchases and prevent fraud.

Payments are processed by Apple or Google and subscription entitlements are managed with RevenueCat. Nearzu does not receive or store your full payment-card number.

3.13 Reports, moderation, and safety data

When you report or block a user or content, or when we investigate potential abuse, we may process:

  • the reporting and reported account identifiers;
  • report category and explanation;
  • relevant content, message, event, group, or conversation identifier;
  • evidence or attachments you submit;
  • block relationships;
  • moderation notes;
  • account warnings, restrictions, or suspension information;
  • appeal and support communications; and
  • audit information needed to protect users and demonstrate enforcement.

When you contact us, we may process your contact details, account information, message, attachments, and any other information needed to respond, verify your identity, resolve the request, or comply with law.

3.15 Website data

When you visit a Nearzu website, the website and hosting provider may process basic server-log information, including IP address, browser type, requested page, time, and security information.

The website may use strictly necessary cookies for security, preferences, session management, and basic operation. Non-essential analytics or similar technologies must not be activated unless the required consent has been obtained.

4. How we collect personal data

We collect personal data:

  • directly from you when you create an account, complete a profile, choose a broad discovery area, upload content, communicate, purchase a subscription, report content, or contact support;
  • from your device when you grant a permission or use a feature;
  • from Apple or Google when you choose their authentication, operating-system, map, geocoding, notification, age-range, payment, or store services;
  • from RevenueCat when it validates and manages subscription entitlements;
  • from Firebase when optional analytics, diagnostics, or push-notification services are used;
  • from WaveSpeed AI when an AI-avatar request is processed;
  • automatically through necessary server, security, and app-operation logs; and
  • from other users when they send you a request, include you in a communication, or report an interaction involving your account.

Where the GDPR or similar law applies, we rely on one or more of the following legal bases.

5.1 Performance of a contract

We process data necessary to:

  • create and manage your account;
  • provide profiles, friends, groups, events, places, messages, and other requested features;
  • provide broad-area people discovery;
  • deliver and restore subscriptions;
  • provide customer support;
  • enforce user-requested privacy controls; and
  • delete your account at your request.

We rely on consent where required for optional processing, including:

  • device location access;
  • saving or using an optional broad discovery area where consent is the applicable basis;
  • Usage Analytics;
  • Diagnostics;
  • push notifications;
  • camera, photo-library, or microphone access;
  • sending a selfie to a third-party AI provider for avatar generation;
  • optional processing of data that local law requires to be based on consent; and
  • non-essential website cookies or similar technologies.

You may withdraw consent at any time. Withdrawal does not affect processing that was lawful before withdrawal.

5.3 Legitimate interests

Where permitted, we process data for legitimate interests such as:

  • protecting users and the integrity of the Service;
  • preventing fraud, spam, unauthorized access, and abuse;
  • operating secure infrastructure;
  • enforcing rate limits;
  • moderating content;
  • investigating reports;
  • maintaining reliable service;
  • defending legal claims; and
  • improving the Service using data that does not require consent.

We assess these interests against the rights and reasonable expectations of users, with particular care for minors.

We may process data when necessary to comply with legal, regulatory, accounting, tax, law-enforcement, consumer-protection, child-safety, or data-protection obligations.

5.5 Vital interests and public-interest grounds

In limited circumstances, we may process or disclose information to protect a person from serious harm or where another legal public-interest ground applies.

6. Age eligibility and protection of minors

6.1 Minimum age

You must be at least 13 years old to create or use a Nearzu social account. A user identified as under 13 cannot complete the social onboarding process.

6.2 Age assurance

Nearzu may use a server-validated date of birth and, where available, a platform-provided declared age range or comparable age signal. We use this information to determine eligibility and apply age-based safety controls.

6.3 Separation of minors and adults

Nearzu uses server-side age bands to separate users aged 13–17 from users aged 18 or older in applicable discovery, public-social, messaging, and group features. Exact age and date of birth are not included in public discovery results.

Age controls are safety measures and do not guarantee that every user has supplied accurate information. Misrepresenting age violates the Terms and may result in restriction or deletion.

6.4 Parent or guardian authorization

The age at which a minor may independently consent to online data processing varies by country.

Where local law requires parent or guardian authorization, Nearzu may require verified authorization before enabling affected social, messaging, upload, discovery, analytics, diagnostics, AI, or other consent-based features.

For users in Slovenia, consent-based processing connected with an information-society service generally requires parent or guardian authorization where the user is under 15, unless another valid legal basis applies.

If required authorization cannot be verified, the affected feature will remain unavailable, the account may remain in a limited mode, or account creation may be refused.

Parent or guardian authorization does not enable:

  • public user-location sharing;
  • user-location pins on a map;
  • live GPS proximity matching;
  • adult-minor people discovery;
  • adult-minor direct messaging; or
  • automatic location collection.

A parent or guardian who believes a child has supplied personal data contrary to this section should contact us using the details in Section 22.

7. Location and “People in your area”

This section describes the intended location behaviour of the current privacy-focused version of Nearzu.

7.1 Location permission is optional

Nearzu requests foreground location permission only when you choose a feature that needs it. You may decline. Core account, settings, legal, and other non-location features remain available, although map centring or local place/event suggestions may be less convenient.

Nearzu does not request or use background location permission.

7.2 Your own map and public places or events

When you choose to use location features, Nearzu may temporarily use your current position to:

  • centre the map for you;
  • display relevant public places or events; or
  • suggest a broad discovery area.

Using location for your own map does not make you visible to other users.

Public place and event markers are not user-location markers.

7.3 One-time broad-area suggestion

When you select “Use My Location Once,” Nearzu may temporarily process your coordinates through device, Apple, Google, map, or geocoding services to suggest a broad city, municipality, region, or sufficiently broad district.

You must review and confirm the suggested area before Nearzu stores it as your discovery-area preference.

The raw coordinates used for the suggestion are discarded after the broad-area resolution and are not stored as your people-discovery location.

7.4 Manual area selection

You can choose a broad discovery area manually without giving Nearzu access to GPS location.

A broad area is a user-selected preference. It does not prove that you currently live in, visit, or are physically present in that area.

7.5 Discoverability is separate and disabled by default

Saving a discovery area does not automatically make your profile discoverable. When an area is first saved, discoverability is disabled by default. You must separately enable visibility in “People in your area.”

You can later disable discoverability or clear the saved area.

7.6 Information not shown to other users

Nearzu does not show or return through people-discovery results:

  • raw coordinates;
  • current or approximate GPS position;
  • a user-location map pin;
  • route or movement history;
  • location timestamp or freshness;
  • distance from another user;
  • nearest-user ordering;
  • the internal discovery-area identifier; or
  • another candidate’s private discovery-area city or region.

A city that a user separately chooses to publish in their profile may be visible as ordinary profile content.

7.7 No public check-ins or live-user map

Nearzu does not provide:

  • a public map showing users’ locations;
  • public manual location check-ins;
  • automatic check-ins;
  • background location updates;
  • live-location snapshots;
  • location sharing in chat;
  • GPS-to-GPS people matching; or
  • distance labels for users.

8. Who can see your information

Depending on your settings and use of the Service:

  • age-compatible users may see your display name, username, avatar, public profile fields, and content you choose to publish;
  • friends, group members, event participants, or conversation participants may see content shared within those features;
  • a message recipient may see message content and related delivery information;
  • moderators may review reported content and relevant context;
  • blocked users are restricted from applicable discovery, profile, messaging, friend-request, group, event, and notification interactions; and
  • Nearzu personnel and authorized service providers may access data only where needed to operate, support, secure, or moderate the Service.

Before posting, consider whether the content could identify your home, school, workplace, routine, or precise location. Do not post another person’s personal data without permission.

9. Blocking, reporting, moderation, and safety

Nearzu provides mechanisms to block users and report users or content from relevant parts of the Service.

We may use automated filters, rate limits, restricted storage rules, and human moderation to detect or address spam, abuse, sexual exploitation, grooming, harassment, impersonation, illegal content, safety threats, or violations of the Terms and Community Standards.

We may remove content; restrict features; suspend or delete accounts; preserve necessary evidence; and cooperate with competent authorities where legally required or necessary to protect a person from serious harm.

10. AI-avatar generation

AI-avatar generation is optional.

Before Nearzu shares the source selfie with WaveSpeed AI, the app must present a specific disclosure and obtain your affirmative consent.

WaveSpeed AI may receive a temporary signed link to the selfie and process the visible appearance needed to generate the requested stylized avatar and remove its background. Nearzu also processes generation identifiers and status data to retrieve and store the result.

Nearzu requires service providers handling personal data to apply appropriate safeguards and use the data only for the contracted service and lawful purposes.

Nearzu removes the source selfie from its own temporary source-storage path after a request completes or fails, on a best-effort basis. A service provider’s infrastructure may retain limited operational records according to its contracted retention settings and applicable law.

Nearzu does not use the selfie or generated avatar for facial recognition, identity matching, law-enforcement identification, or advertising profiling.

You may decline AI processing and use Nearzu without generating an AI avatar. You may replace or remove the resulting avatar and may delete your account.

11. When we share personal data

We may share personal data in the following circumstances.

11.1 With other users

We share profile, social, content, and communication data according to the feature you use, your privacy settings, your age cohort, and your relationships with other users, as described in Section 8.

11.2 With processors and service providers

We use service providers to operate the Service. Depending on the feature, these may include:

  • Supabase for authentication, databases, storage, server functions, and related backend infrastructure;
  • Apple for Sign in with Apple, device services, declared age-range information where available, app distribution, in-app purchases, notifications, and operating-system permissions;
  • Google for Google Sign-In, maps, geocoding, device services, app distribution, in-app purchases, notifications, and operating-system permissions;
  • Firebase for push messaging and, only after the relevant consent, Analytics and Crashlytics diagnostics;
  • RevenueCat for subscription receipt validation and entitlement management; and
  • WaveSpeed AI for optional AI-avatar generation and background removal after explicit consent.

These providers process data under their own infrastructure and, where acting as our processors, under contractual and legal data-protection obligations.

We may disclose information where reasonably necessary to:

  • comply with applicable law, regulation, legal process, or a valid government request;
  • investigate fraud, security incidents, or abuse;
  • enforce our Terms or Community Standards;
  • protect the rights, property, or safety of Nearzu, users, or others;
  • prevent serious harm; or
  • establish, exercise, or defend legal claims.

11.4 Business changes

If Nearzu is involved in a merger, acquisition, financing, reorganization, insolvency, or sale of assets, personal data may be disclosed as part of that transaction, subject to confidentiality, applicable law, and continued protection.

12. No sale, third-party behavioural advertising, or cross-app tracking

Nearzu does not sell personal data.

In the current version of the Service, Nearzu does not share personal data for third-party behavioural advertising and does not use personal data to track users across apps or websites owned by other companies.

Nearzu does not use advertising networks in the current release. If this changes, we will update this Privacy Policy, update applicable app-store disclosures, and obtain any consent required by law or platform rules before beginning such processing.

13. Your permissions and privacy controls

You can control your data through Nearzu and your device settings.

13.1 Location

You may decline or revoke location permission. You may use manual broad-area selection without GPS. You may disable discoverability and clear your broad discovery area.

13.2 Analytics and diagnostics

Usage Analytics and Diagnostics have separate controls. They are disabled until enabled by you and may be withdrawn later. Disabling them stops future optional collection, but does not retroactively invalidate prior lawful processing.

13.3 Notifications

You can disable Nearzu notifications or specific alert preferences and can revoke operating-system notification permission.

13.4 Camera, photos, and microphone

You may revoke these permissions in your device settings. Features that require the revoked permission may no longer work until permission is restored.

You may decline the AI-avatar feature. Withdrawing consent prevents new AI-avatar requests based on that consent. To remove an already generated avatar or related account data, use the profile or account-deletion controls or contact us.

13.6 Profile visibility and social controls

You can edit eligible profile information, disable discoverability, remove content where the feature allows, remove friends, block users, report users or content, and manage blocked users.

13.7 Account deletion

You can request deletion through the in-app Delete Account feature or through the account-deletion information page listed at the beginning of this Policy.

14. Data retention

We keep personal data only for as long as reasonably necessary for the purpose for which it was collected, including providing the Service, maintaining security, resolving disputes, enforcing agreements, and meeting legal obligations.

We determine retention using criteria including:

  • whether your account remains active;
  • whether the data is needed to provide a feature you requested;
  • whether you have deleted content, cleared a preference, withdrawn consent, or deleted your account;
  • the sensitivity and risk of the data;
  • applicable limitation periods;
  • safety, fraud-prevention, moderation, accounting, tax, and legal requirements;
  • technical backup and disaster-recovery cycles; and
  • service-provider retention commitments.

Typical retention treatment includes:

  • Account and profile data: retained while the account is active and deleted or anonymized through the account-deletion process, subject to legal exceptions.
  • Broad discovery area: retained until you change it, clear it, or delete your account.
  • User content and messages: retained while needed to provide the feature and removed through content or account deletion, subject to safety, dispute, legal, and backup limitations.
  • AI source selfie in Nearzu storage: removed after the generation request completes or fails, on a best-effort basis.
  • Generated avatar: retained until replaced, removed, or the account is deleted.
  • Push token: retained while notifications are enabled and removed when no longer needed, including after sign-out or account deletion where supported.
  • Analytics and diagnostic data: future collection stops when consent is withdrawn. Existing data is retained only for the applicable operational period and is deleted or de-identified when no longer needed.
  • Reports and moderation records: may be retained or anonymized for safety, audit, repeat-abuse prevention, legal claims, and compliance.
  • Purchase and entitlement records: may be retained by Nearzu, RevenueCat, Apple, or Google as needed for entitlement, accounting, tax, fraud-prevention, and legal obligations.
  • Backups: deleted information may remain temporarily in encrypted or access-controlled backups until those backups are overwritten under the applicable backup cycle.

15. Account deletion

When you complete Nearzu’s account-deletion process, we delete the authentication account and delete or anonymize user-owned app data and media in accordance with the implemented deletion workflow.

Certain records may be retained in anonymized form or where retention is necessary for:

  • safety and abuse prevention;
  • legal claims;
  • fraud prevention;
  • accounting or tax requirements;
  • transaction integrity; or
  • compliance with law.

Deleting your Nearzu account does not necessarily cancel an active Apple App Store or Google Play subscription. You must separately manage or cancel the subscription through the relevant app-store account. Store operators may retain transaction records under their own legal obligations and privacy policies.

16. Security

We use technical and organizational safeguards designed to protect personal data, including, where appropriate:

  • authenticated access;
  • authorization and database row-level access controls;
  • restricted storage policies;
  • encrypted network transport;
  • secure token handling;
  • generated media filenames;
  • media re-encoding and metadata reduction;
  • rate limiting;
  • input validation;
  • audit and security logging;
  • account blocking and suspension controls; and
  • deletion and anonymization workflows.

No system can be guaranteed to be completely secure. Protect your device and account, do not share access credentials, and contact us promptly if you believe your account or data has been compromised.

17. International data transfers

Nearzu is established in Slovenia, but some service providers may process data in other countries, including countries outside the European Economic Area.

Where required, we use an applicable transfer mechanism, such as:

  • an adequacy decision;
  • European Commission Standard Contractual Clauses;
  • contractual and technical supplementary safeguards; or
  • another transfer mechanism permitted by law.

You may contact us for more information about the safeguards applicable to a particular transfer.

18. Your privacy rights

Depending on your location and applicable law, you may have the right to:

  • obtain confirmation whether we process your personal data;
  • access your personal data;
  • correct inaccurate or incomplete data;
  • request deletion;
  • request restriction of processing;
  • object to processing based on legitimate interests;
  • receive data you provided in a structured, commonly used, machine-readable format and transmit it to another controller where applicable;
  • withdraw consent at any time;
  • request information about recipients and international-transfer safeguards;
  • request human review of an automated decision where required by law; and
  • lodge a complaint with a competent supervisory authority.

For users in Slovenia, the competent supervisory authority is the Information Commissioner of the Republic of Slovenia. You may also complain to the authority in the EU or EEA country of your habitual residence, place of work, or the alleged infringement.

To exercise a right, contact us using the privacy email in Section 22. We may request reasonable information to verify your identity and protect the account from unauthorized requests.

A parent, guardian, or authorized representative may submit a request where permitted by law. We may ask for proof of authority.

19. Automated systems and recommendations

Nearzu may use automated rules to:

  • enforce minimum age and age-cohort separation;
  • match eligible users within a broad area;
  • rank or randomize discovery results using non-location factors such as shared interests;
  • detect prohibited or unsafe text or media;
  • enforce rate limits;
  • detect abuse or suspicious activity; and
  • apply feature eligibility or safety restrictions.

These systems are intended to provide and secure the Service. Where applicable law grants a right to human review of a decision producing legal or similarly significant effects, you may request review through support.

Nearzu may contain links to websites, places, events, or services operated by third parties. We are not responsible for independent third-party privacy practices. Review their privacy information before providing data to them.

Apple, Google, and app stores may independently process account, device, purchase, notification, map, and permission data as separate controllers under their own policies.

21. Changes to this Privacy Policy

We may update this Privacy Policy to reflect changes in the Service, law, safety practices, or service providers.

We will change the “Last updated” date and, where required, provide notice in the app or request renewed consent before materially different optional processing begins.

Continued use of the Service after an update does not replace consent where consent is legally required.

22. Contact us

Nearzu d.o.o.

Slovenia

Privacy email: [INSERT WORKING PRIVACY EMAIL ADDRESS]
Support page: https://nearzu.com/support/
Account deletion: https://nearzu.com/account-deletion/

Please include enough information for us to identify the relevant account or request, but do not send passwords, full payment-card details, or unnecessary sensitive information.