WANDRO Privacy Policy
Version of: 9 November 2026.
Applies from: 9 November 2026.
1. Controller and scope
The controller is „ФАЙЪР 09“ ЕООД (FIRE 09 EOOD), UIC 207134356, 28 Stefan Stambolov Blvd., Sofia 1000, Bulgaria.
Contact: contact@wandro.io, https://wandro.io, telephone +359 877 743 009.
The Policy covers the app for iOS and Android, wandro.io and correspondence.
The Company has not designated a data protection officer. Questions are to be sent to the contact details stated above.
This document provides information and does not require general consent to processing.
2. Key points
- A profile is created with an email address or through Apple/Google.
- Personal features are not public.
- Impressions are reviewed by a person.
- Optional analytics is switched off by default.
- There is no background use of location and no recording of it in the profile.
- “For You” („За теб“) uses local preferences based on the tags of liked impressions, without sending these preferences to the server infrastructure.
- Notifications are local.
- The Company does not receive full card data for in-app purchases.
- Deleting a profile does not stop the subscription in the store.
3. Categories and sources
3.1. Provided by you
We process the necessary email address, name, profile identifier, authentication data (including the time of the last sign-in to the profile), entries and photos in the diary, saved places and routes, plans, trips, visited places (“Your Path” („Твоят път“)), drafts, impressions, reports, correspondence and choices regarding technologies.
3.2. From providers
Apple/Google transmit the data necessary for the chosen sign-in, including name and email address. Apple may provide a hidden forwarding address.
We do not receive your Apple or Google passwords.
The App Stores and RevenueCat provide data on the product, the transaction, the subscription and the access entitlement.
With an in-app purchase, we do not receive full card numbers, security codes or bank details.
3.3. Technical data
When a connection is made, the necessary IP address, request, date, time and other technical records are processed.
When analytics is switched on, events and data about the device and the installation are processed.
An identifier without a name is not automatically treated as anonymous.
3.4. Local data
Location, settings, preferences for “For You” and reminders are used on the device.
Local calculation does not exclude the separate requests to Google Maps or the permitted collection of analytics events.
3.5. Technologies not used
No advertising SDKs, advertising identifier, cross-app tracking, Meta SDK or separate crash reporting tool are used. The fonts are embedded.
4. Purposes and legal bases
Each legal basis applies only to the processing that is specifically necessary. Legitimate interest does not justify operations where the rights and interests of the person concerned prevail.
| Processing | Purpose and data | Legal basis and recipients |
|---|---|---|
| Registration and sign-in | Creating and managing a profile, including keeping the profile active on one device at a time (section 5.4 of the Terms of Service); email address, name, identifiers, authentication and the time of the last sign-in | Performance of the requested contractual features; Firebase Authentication and Firestore, the chosen Apple/Google sign-in |
| Personal features | Diary, photos, saved places, plans, trips, visited places (“Your Path”) and drafts; memories (“A year ago” („Преди година“)) and an annual summary are shown from them | Performance of the contract; Firestore and Storage |
| Sensitive data in the diary | Data on health, religion and other special categories, if the User records them in the diary | Explicit consent (Article 9(2)(a) GDPR), given before the first entry; Firestore and Storage |
| Impressions | First name, text, photos, place and coordinates of the place, tags, date, status, profile identifier | Publication on request — contract; review and prevention of abuse — legitimate interest; the specific obligations regarding reports and statements of reasons — the applicable legal obligation |
| Reports | Post, reporter, reason, necessary contact | Protection of persons and the Platform — legitimate interest; handling of applicable notices under the Digital Services Act — legal obligation |
| Purchases | Identifiers, product, transaction, subscription status and unlocking | Performance of the contract; RevenueCat, the App Stores, Firestore and Cloud Functions |
| Separate accounting records | Only the necessary financial and identification data | the obligations under the Accountancy Act and the Value Added Tax Act |
| Restoration of purchases | Minimal link between the proof of purchase and the acquired right | Performance of the continuing contractual obligations; separately justified retention where necessary |
| Location and local reminders | Expressly requested “Near Me” („Близо до мен“), map, navigation, reminders and events | Performance of the requested feature; technical permission from the operating system |
| “For You” | Optional local recommendations based on the tags of liked impressions | Separate consent |
| Maps | IP address, requests and what is necessary for the map and navigation | Performance of the requested feature; Google Maps according to its specific role |
| In-app analytics | Usage statistics and events | Separate consent; Google Analytics for Firebase |
| Website — delivery and protection | Necessary technical requests and records | Legitimate interest in a functioning and secure website; Firebase Hosting (Google) |
| Website language | The selected bg/en language, wandro_locale | Implementing the choice |
| Correspondence | Contact, message, attachments and necessary identifier | Contract, when providing service; legitimate interest, for other replies; legal obligation, for a request under legislation |
| Data rights | Request, necessary identification and response | Fulfilment of the obligations for the exercise of rights |
| Copy of the data | Preparing an archive at Your request from the app; the profile data and the delivery address | Fulfilment of the obligations under Articles 15 and 20 GDPR; Firestore, Storage, Cloud Functions and email |
| Security | Necessary identifiers, time and technical records | Legitimate interest and the specific security obligations |
| Claims and authorities | The data necessary for a specific claim or legal obligation | The applicable legal basis for the specific case, without general unlimited disclosure |
4.8. In-app analytics
With consent, the automatic events and parameters of Google Analytics for Firebase are collected, including first open, session start, screen view, device, operating system, app version and approximate location.
Documentation: https://support.google.com/analytics/answer/9234069.
The WANDRO events are opening a route, opening a map, starting, saving, liking and sharing, with the route identifier.
The app does not set a User ID and does not use an advertising identifier. This does not mean that all data is anonymous or unlinkable.
4.9. Correspondence
Email provider: Google (Google Workspace — Gmail).
A copy of an identity document is not routinely required. Where there is reasonable doubt, only the necessary additional information is requested.
4.11. Website
The website does not use visit statistics tools.
The deletion page does not require sign-in and does not create an authentication session. The request is sent by email; identity is verified separately through the necessary correspondence.
The information on the purposes, legal bases, recipients, retention periods and consequences is provided in line with Article 13 GDPR.
5. Consent and choices
There is no implied consent and no consent through continued use.
The separate choices are for:
- in-app analytics;
- “For You”;
- advertising messages, if introduced;
- storage of your special categories of personal data in the diary, where you choose to provide such data — under the conditions of and through the mechanism in Section 6.1.
Analytics is managed from “Profile” („Профил“) → “Settings” („Настройки“) → “Usage statistics” („Статистика за ползването“). The choice is made with a separate box when the profile is created; the box is not ticked in advance and is not a condition for registering; an unticked box is a refusal. Until a choice is made, analytics stays switched off.
“For You” is switched on, switched off and reset through Profile → Settings → “For You suggestions” („Предложения „За теб““) (on, off and reset).
Refusal does not block unrelated features. Withdrawal is possible at any time and is as easy as giving consent. The lawfulness of prior processing is preserved. The Company keeps evidence of consent, limited to what is necessary.
6. Content, sensitive data and publicity
6.1. Special categories
Special categories of data are not required for ordinary use, but they may appear in texts and photos.
Regime for personal features and posts: special categories of data are not allowed in impressions, and such impressions are rejected at review; in the “Diary” the Company does not ask for or analyse such data — if the User records them, they are kept only for the User to see, on the basis of the User’s explicit consent (Article 9(2)(a) GDPR). Before the first entry a separate message is shown with two choices: “I agree” — the User gives explicit consent for the entries to also contain such data about the User; or “Ordinary entries only” — the diary is used without such consent and the User does not record such data. The diary works with either choice. The consent given is recorded with the date, time and version of the text. It may be withdrawn at any time from Profile → Settings → “Withdraw consent for the diary”; before withdrawal the User is told that entries with such data must be deleted, and deletion of individual entries or of all entries is offered. Individual entries may be deleted at any time. Sensitive data about other people must not be recorded in the diary; the User’s consent is not a basis for such data. Where an impression is rejected because of special categories of data, its text and photos are deleted immediately with the decision from the active systems; they disappear from the backups and from the protection against accidental deletion within 14 days (Section 10); only the decision, the reason and the dates are kept — for the appeal.
Uploading to a personal diary is not presented as manifestly making data public. Publishing does not automatically create a right to process other people’s sensitive data.
6.2. Access
| Category | Access |
|---|---|
| Profile | You, authorised persons and the necessary providers |
| Personal features | Not accessible to other Users |
| Pending and rejected impressions | The author, the Company and the necessary technical providers |
| Published impressions | All Users at the place: first name, text, photos, place, tags and date |
| Reports | Authorised persons and the necessary contractors |
| Purchases | You, the Company and the providers necessary for the purchase |
Impressions are not displayed on the website and are not made available for indexing. The audience is shown before submission.
6.3. Photos
The selected photos are uploaded. Access is through the camera or the system photo picker.
EXIF: photo metadata (EXIF), including coordinates, is removed on upload.
7. Permissions and device
Location is used only actively, without background use and without being recorded in the profile. “I was here” („Бях тук“) records the chosen place and the date, not the device coordinates. Impressions are linked to the coordinates of the place.
On the map, location is displayed through the Google Maps SDK. With “How to get there” („Как да стигна“), the current coordinates are passed as the starting point and the place as the destination.
The camera and the selected photos are used when a photo is added.
Local notifications are only those You requested: reminders, events and “Tell me” („Кажи ми“). They are not sent from a server and do not advertise third parties. They are managed from “Profile” → “Settings” → “Notifications” („Известия“) and the operating system.
Refusing a permission affects the dependent features, not automatically all access.
8. Recipients and roles
The following services are used for the features described. The legal entity and the role are determined by the specific applicable contract, not only by the trade name.
| Service | Entity and specific role |
|---|---|
| Firebase Authentication, Firestore, Storage, Cloud Functions | Google Cloud EMEA Limited (Ireland); processor |
| Google Analytics for Firebase | Google Ireland Limited (Ireland); processor, while the data-sharing settings with Google are switched off |
| Google Maps SDK | Google Cloud EMEA Limited (Ireland); Google is an independent controller for the data it receives when the maps are used |
| RevenueCat | RevenueCat, Inc., USA; processor under the RevenueCat data processing agreement |
| Apple/Google sign-in | Apple Distribution International Ltd. and Google Ireland Limited; independent controllers for the data they process for the sign-in itself |
| App Store/Google Play | Apple Distribution International Ltd., Google Ireland Limited and Google Commerce Limited; independent controllers for the purchase and the payment; Apple Distribution International Ltd. acts as commissionaire of the Company |
| Firebase Hosting | Google; processor for hosting the website |
| Google (Google Workspace); processor |
Other recipients are competent authorities and parties to specific legal claims, only where there is a legal basis and necessity.
Within the Company, authorised persons have access according to their tasks. Data is not sold and is not provided for advertising purposes.
Relationships with processors are governed by the necessary contractual safeguards, including on assistance with rights and on erasure or return after completion.
9. International transfers
The region of one database does not determine all places of processing, access and onward transfer.
| Service | Confirmed countries and regions | Specific mechanism and access to the safeguards |
|---|---|---|
| Firestore and Storage | Firestore — europe-west3 (Frankfurt, Germany); Storage — europe-west1 (Belgium); access is held by the Company and by Google as processor | The main storage is in the stated EU regions. If there is access or a transfer outside the EU (support, sub-processors), the recipient is Google LLC or its sub-processors, and the mechanisms are the EU-U.S. Data Privacy Framework (Google LLC is certified) and the Firebase standard contractual clauses (Modules 2 and 3; https://firebase.google.com/support/privacy). |
| Authentication | USA — Firebase Authentication runs only from data centres in the USA | the EU-US Data Privacy Framework (Google LLC is certified) and standard contractual clauses; recipient Google LLC |
| Cloud Functions | europe-west3 (Frankfurt, Germany) — all functions except photo resizing; europe-west1 (Belgium) — the function that resizes uploaded photos | The functions run in the stated EU regions. If there is access or a transfer outside the EU (support, sub-processors), the recipient is Google LLC or its sub-processors, and the mechanisms are the EU-U.S. Data Privacy Framework (Google LLC is certified) and the Firebase standard contractual clauses (Modules 2 and 3; https://firebase.google.com/support/privacy). |
| Analytics | the USA and other countries where Google or its sub-processors have data centres | the EU-US Data Privacy Framework (Google LLC is certified) and standard contractual clauses; recipient Google LLC |
| Maps | the USA and other countries where Google processes data; recipient — Google LLC | standard contractual clauses under the Google Maps Platform Controller-Controller Data Protection Terms (https://mapsplatform.google.com/resources/trust-center/eu-standard-contractual-clauses/); the EU-U.S. Data Privacy Framework (Google LLC is certified) |
| RevenueCat | USA (Amazon Web Services) | standard contractual clauses (modules 2 and 3) under the RevenueCat data processing agreement |
| Apple/Google | the EU and the USA — sign-in, purchases and payments; recipients Apple Inc. and Google LLC | Apple: standard contractual clauses (Apple Privacy Policy, https://www.apple.com/legal/privacy/); Google: the EU-U.S. Data Privacy Framework (Google LLC is certified) and standard contractual clauses (https://policies.google.com/privacy) |
| Firebase Hosting | the Google global content delivery network | the EU-US Data Privacy Framework (Google LLC is certified) and standard contractual clauses; recipient Google LLC |
| the EU, the USA and other countries where Google has data centres | the EU-US Data Privacy Framework (Google LLC is certified) and standard contractual clauses; recipient Google LLC |
The status of “independent controller” is not a mechanism for international transfer. Consent to analytics is also not in itself such a mechanism.
Transfers and onward transfers take place only under the conditions of Chapter V GDPR. Information and a copy of the applicable safeguards can be obtained via contact@wandro.io.
10. Retention periods
| Category | Period and starting point |
|---|---|
| Profile and authentication | Until deletion; final erasure within 30 days. The time of the last sign-in is replaced at each new sign-in. |
| Personal entries, photos and drafts | Until deletion of the content or the profile; removal from active systems within 30 days |
| Published and pending impressions | Until deletion; technical erasure within 30 days |
| Rejected impressions | Until 6 months have passed from the notification of the decision or, where an appeal has been lodged, until it is concluded. On rejection because of special categories of data the content is deleted immediately from the active systems (from the backups — within 14 days); only the decision, the reason and the dates are kept |
| Reports, appeals and moderation | 1 year from closure — for accountability and for defence in an appeal |
| Records of acceptance of the terms | For as long as the profile exists; they are deleted together with it. The email confirming the acceptance (version, date and time) is kept as correspondence for 3 years |
| Operational subscription record | Until deletion of the profile; erasure within 30 days |
| Accounting records | 10 years from 1 January of the year following the year of the purchase (Accountancy Act) |
| Minimal records for restoration | 1 year after the deletion of the profile; only the minimal data needed to perform the continuing right are kept: the transaction number, the product, the date, the store and the unlocked city, plan or route; the deleted content of the profile is not restored |
| RevenueCat | until the profile is deleted; the data in RevenueCat is then deleted within 30 days |
| Firebase Analytics | 2 months; events and technical device data |
| Technical records | Firebase and Cloud Functions — 30 days (Google Cloud Logging); website hosting — the Company keeps no separate request logs |
| wandro_locale | 180 days |
| Correspondence | 3 years from the end of the correspondence, unless it is needed for a pending dispute |
| Rights requests | 3 years from the fulfilment of the request |
| “Download my data” archive | 30 days from preparation, including when requested on profile deletion; then deleted automatically. It is kept apart from the other data, without backups, and serves only to be downloaded. |
| Withdrawal requests | 5 years from the request — to prove performance and in case of a dispute |
| Legal claims | until the applicable limitation period expires or the dispute ends; the need is reviewed once a year |
| Backups | The database (Firestore) is copied once a day and each copy is kept for 14 days; separately, its earlier states are kept for the last 7 days. The copies are in the same region as the database (Frankfurt) and serve only to restore data after a failure or an error. Deleted data disappears from them within 14 days of deletion. Deleted files in storage (the photos from the diary and from impressions) are kept for 7 more days, only for recovery after an error, and are then deleted permanently. The “Download my data” archive is in a separate storage without these 7 days. |
The entire profile is not retained merely because of a purchase. The different purposes are kept separate. Undefined “operational needs” do not justify indefinite retention.
The periods are limited to what is necessary under Article 5(1) GDPR.
Local data is managed through the settings and the device. Uninstalling does not guarantee deletion of system backups.
11. Profile deletion
Deletion is requested in “Profile” or by email in accordance with https://wandro.io/en/delete-account.
Before deletion, You can request a copy of Your data with “Send me a copy” (Section 16). The archive is prepared before deletion and kept for 30 days.
The profile, the personal features, the drafts, the operational and gifted unlocks, the subscription record, the impressions, the photos, the related reports and the authentication are removed.
The minimal purchase records, the correspondence, the requests, the technical records, the backups, RevenueCat and Analytics are dealt with separately.
- RevenueCat: when a profile is deleted, the Company deletes the customer data in RevenueCat within 30 days; this does not cancel the subscription with Apple or Google.
- Analytics: the app does not set a user identifier (User ID), so the data is linked to the installation identifier; the 2-month period applies to event-level and user-level data, while aggregated reports in Google Analytics are not affected; requests are made to contact@wandro.io and handled within 1 month.
- Reports for a specific obligation or claim: restricted storage of only the necessary data until the obligation is met or the claim ends.
The absence of a set User ID does not automatically exclude identification or the handling of a rights request. Inability to identify is substantiated in accordance with Article 12(2) GDPR. The automatic erasure period does not replace the handling of the request.
Where further retention is permissible, the category, the purpose, the access and the period are limited.
Deletion does not remove the Apple/Google accounts and does not stop the subscription. Purchases are restored under Section 5.4 of the Terms of Service, without restoration of deleted personal content.
12. Security
Appropriate technical and organisational measures are applied for confidentiality, integrity, availability and protection, commensurate with the risk. Absolute security is not promised, and statutory liability is not transferred to the User.
In the event of an incident, an assessment, containment and the necessary notifications are carried out.
The measures are determined in accordance with Articles 25 and 32 GDPR.
13. Automation and recommendations
Publication, rejection and moderation decisions are made by people.
The limit of 3 impressions per 24 hours is automatic and can be reviewed if challenged.
“For You” orders recommendations based on local preferences for the tags of liked impressions. Relative importance of the parameters: the greatest weight is given to personal interest — the tags of impressions You liked; the likes, saves and views of the impression, how new it is and how close it is to You are also taken into account.
The data on local preferences is not sent to the server infrastructure and is not used for advertising. Separately permitted analytics events remain distinct.
The place of the week is the same for everyone. The personal weekend suggestion is selected based on the city You chose, the season and the places in “Your Path”. It is not used to advertise third parties.
Under the model described, no solely automated decisions with legal or similarly significant effects are taken.
14. Advertising
Current sending of advertising messages: none are sent.
For advertising email to Users, separate prior consent is obtained. The general acceptance of the contract is not used.
Every message includes an easy and free way to unsubscribe. Upon objection, direct marketing stops. Service messages on performance and security are separate.
15. Age
WANDRO is intended for persons aged 18+.
Where use by a person under 18 is established, access is restricted and the data is dealt with in accordance with the applicable rights and obligations.
A parent or guardian may write to contact@wandro.io.
16. Rights
Subject to the applicable conditions, you have the rights of:
- access and a copy;
- rectification;
- erasure;
- restriction;
- portability;
- objection;
- withdrawal of consent.
Access and the copy are provided with respect for the rights of others.
Restriction may be requested in the case of contested accuracy, of unlawful processing instead of erasure, of a need for the data for your claims or of verification of an objection.
Portability covers data provided by you and processed by automated means on the basis of consent or contract, and direct transmission where technically feasible.
Where you object, on grounds relating to your particular situation, to processing based on legitimate interest, the processing stops, unless there are demonstrated overriding grounds or it is necessary for legal claims. For direct marketing, it stops without such an assessment.
Requests: contact@wandro.io.
Copy from the app. From “Profile” („Профил“) → “Settings” („Настройки“) → “Download my data” („Изтегли моите данни“), and when deleting the profile with “Send me a copy” („Изпрати ми копие“), You receive an archive with the profile and sign-in data, the diary (text, dates and places), the photos from the diary and the impressions in the form in which they are stored, the saved places and plans, the visited places (“Your Path” („Твоят път“)), the reports, the withdrawal requests, the purchases, the unlocks and the history of consents — in a readable form and in JSON format. The archive also says what it does not include; the purposes, recipients and retention periods are in this Policy. The archive is sent as a link to the profile email address; another address is used only after confirmation with a code. The link and the archive are valid for 30 days, after which the archive is deleted automatically. This does not limit the right to submit a request to contact@wandro.io.
A response is provided without undue delay and within one month. Where necessary, the period may be extended by a further two months, with notice and reasons given within the first month.
If no action is taken, the reasons and the available remedies are communicated. Additional identification is requested only where there are reasonable concerns and to the extent necessary.
As a rule, exercising the rights is free of charge. For a manifestly unfounded or excessive request, a fee or a refusal is permitted only under the conditions of the GDPR and where the Company demonstrates this.
A complaint may be lodged with the Commission for Personal Data Protection (CPDP) — https://cpdp.bg, subject to the applicable conditions and time limits. Judicial protection is preserved.
17. Cookies and SDKs
The details are set out in the separate policy. A lack of technical support for DNT is not a ground for ignoring a valid objection or withdrawal.
18. Changes
Before a new purpose is pursued, the necessary information is provided and, where needed, separate consent is obtained.
Publishing a new policy is not consent. Material changes are communicated in an appropriate manner. Previous versions can be obtained via contact@wandro.io.
19. Contact
„ФАЙЪР 09“ ЕООД (FIRE 09 EOOD), UIC 207134356
28 Stefan Stambolov Blvd., Sofia 1000, Bulgaria
contact@wandro.io · https://wandro.io
Telephone: +359 877 743 009.
