Privacy Policy
Last updated: 25 April 2026 · Version 1.2
Controller: Vis2Go OÜ, registry code 16462903
1. Who We Are
Vis2Go OÜ ("Vis2Go", "we", "us", "our") operates the Vis2Go mobile application ("App").
| Company | Vis2Go OÜ |
| Registry code | 16462903 |
| Registered address | Harju maakond, Tallinn, Pirita linnaosa, Ranniku tee 35, 12113, Estonia |
| Website | https://vis2go.com |
| Representative | Vaidas Rudis |
| Contact | hello@vis2go.com |
Vis2Go OÜ is the data controller for the personal data described in this Privacy Policy, except where a third-party service acts as an independent controller for its own processing.
This Privacy Policy explains what data we collect, why we collect it, who receives it, how long it is kept, and what rights you have under the General Data Protection Regulation (EU) 2016/679 ("GDPR") and other applicable privacy laws.
2. Summary
Vis2Go is designed to minimise personal data collection. We do not require an account. We do not collect your name, email address, password, payment details, contacts, photos, microphone data, camera data, advertising ID, or push notification token.
The App uses location, search, diagnostic, and request information to provide maps, directions, place information, experiences, tickets, tours, activities, booking links, natural-language search, diagnostics, infrastructure, and related travel functionality. Some requests are sent to selected third-party providers where this is necessary to provide the requested feature.
The current list of third-party providers is available in our Third-Party Provider List, which we may update from time to time.
We do not sell personal data. We use AppsFlyer for mobile attribution analytics. On iOS, we request permission to access the advertising identifier (IDFA) via Apple's App Tracking Transparency framework (see §3.6). We also use server-side conversion tracking via Meta Conversions API (see §3.7).
3. Data We Process
3.1 Location Data
| Data | Purpose | Legal basis | Retention by Vis2Go |
|---|---|---|---|
| Foreground precise or approximate device location | Anchor nearby discovery, map view, geocoding, directions, venue search, ticket/experience discovery | Consent, Art. 6(1)(a) GDPR | Not stored by Vis2Go as a user profile. Used during the app session. |
| Manually selected destination or city | Plan-mode discovery, map anchoring, ticket and experience search | Performance of contract, Art. 6(1)(b) GDPR | Not stored on our servers. May be used in local app state. |
Location permission is foreground-only. Vis2Go does not request background location access. Location is not sent to OpenAI for vibe search. You can revoke location permission at any time in your device settings.
3.2 Trip, Itinerary, Preferences, and Recent Places
| Data | Purpose | Legal basis | Retention by Vis2Go |
|---|---|---|---|
| Current trip plan, timeline nodes, shortlist, and itinerary state | Core trip-planning functionality | Performance of contract, Art. 6(1)(b) GDPR | App memory only; cleared when the app restarts. |
| User preferences (style level, vibe mode, mobility default, map style) | Remember app preferences | Performance of contract, Art. 6(1)(b) GDPR | Stored locally on your device until you clear app data or uninstall. |
| Recent places (capped list) | Convenience feature | Legitimate interests, Art. 6(1)(f) GDPR | Stored locally until app data is cleared or App is uninstalled. |
Vis2Go does not currently sync trip plans, itineraries, preferences, or recent places to a Vis2Go account or cloud database.
3.3 Vibe Search Using OpenAI
When you use vibe search, your query text is sent to OpenAI via our Cloudflare Worker proxy to convert natural-language search text into structured discovery parameters. The request does not include your GPS location, destination city, itinerary, preferences, persistent user ID, or session ID.
Please do not include names, addresses, phone numbers, health information, or other sensitive personal information in vibe search queries. If you include personal information in a vibe search query, it may be sent to OpenAI for processing as part of interpreting your request. OpenAI processes API data under its applicable business/API terms and states that it does not train its models on API Platform data by default.
3.4 Maps, Places, Directions, Tickets, Experiences, and Booking Links
Vis2Go uses third-party providers to retrieve maps, directions, place information, experiences, tickets, tours, activities, and booking links. These providers may receive limited data necessary to fulfil the relevant request. The current list is available in our Third-Party Provider List.
When you tap a booking link, you leave Vis2Go and complete any booking directly with the relevant third-party provider. Vis2Go does not receive your payment details, booking details, or purchase confirmations. Vis2Go may receive affiliate commissions or referral fees from third-party booking providers.
3.5 Crash Reporting, Diagnostics, and Sentry Metrics
| Data | Purpose | Legal basis | Retention |
|---|---|---|---|
| Crash logs, stack traces, device model, OS version, app version, build version | Diagnose and fix crashes and technical errors | Legitimate interests, Art. 6(1)(f) GDPR | 90 days on Sentry |
| Performance and operational metrics (request completion/failure, latency, result count) | Maintain app reliability | Legitimate interests, Art. 6(1)(f) GDPR | 90 days on Sentry |
Vis2Go does not intentionally send raw location coordinates, vibe search text, itinerary content, personal notes, payment data, or contact details to Sentry.
3.6 Mobile Attribution and Analytics (AppsFlyer)
| Data | Purpose | Legal basis | Retention |
|---|---|---|---|
| Advertising identifiers (IDFA on iOS with ATT consent; GAID on Android) and device identifiers | Measure marketing campaign performance; fraud prevention | Consent, Art. 6(1)(a) GDPR (IDFA) / Legitimate interests, Art. 6(1)(f) GDPR (other identifiers) | Retained by AppsFlyer per their privacy policy |
| App launch and usage events; device and network info (device type, OS, IP address) | Attribution analytics and fraud prevention | Legitimate interests, Art. 6(1)(f) GDPR | Retained by AppsFlyer per their privacy policy |
On iOS, the ATT prompt is shown before any IDFA is accessed. You can withdraw permission at any time in device Settings → Privacy & Security → Tracking. On Android, you can reset or limit the advertising ID in Google Settings.
AppsFlyer acts as a data processor. See: appsflyer.com/legal/privacy-policy.
3.7 Advertising Conversion Tracking (Meta Conversions API)
| Data | Purpose | Legal basis | Retention |
|---|---|---|---|
| Event type (e.g. "Search", "ViewContent", "Contact") | Measure ad campaign effectiveness; optimise ad delivery on Meta platforms (Facebook, Instagram) | Legitimate interests, Art. 6(1)(f) GDPR | Not stored by Vis2Go. Forwarded to Meta immediately. Meta retains conversion event data per their Data Policy. |
| IP address (collected server-side from your network request) | Improve event match quality for Meta attribution | Legitimate interests, Art. 6(1)(f) GDPR | Not stored by Vis2Go. Forwarded to Meta immediately. |
When you perform a key action in the App (search, view a place card, tap a booking link), our server receives a notification containing only the event type. Your device's IP address is captured server-side from the network request — the App itself never sends your IP address. These signals are forwarded to Meta's Conversions API to attribute advertising conversions.
No native Meta SDK is installed in the App. We do not use Meta's mobile SDK, IDFA, or any device advertising identifier. This is a server-side integration only.
Meta Platforms Ireland Ltd. acts as an independent controller for conversion data received. See: facebook.com/policy.
3.8 Infrastructure and request routing
We use infrastructure providers to securely route selected requests to third-party services and protect API credentials. These providers may process limited request metadata, such as IP address, request path, timestamp, and technical headers. We do not use this infrastructure to store user trip data.
4. Data We Do Not Collect
Vis2Go does not collect:
- account registration data;
- name, email address, password, or phone number;
- payment or financial data;
- advertising identifiers collected beyond what is described in §3.6 (AppsFlyer) and §3.7 (Meta CAPI);
- contacts, camera, microphone, photos, or media library data;
- background location;
- push notification tokens;
- Firebase or Google Analytics identifiers;
- no native Meta/Facebook SDK is installed in the App;
- no cross-app tracking.
We use server-side conversion tracking via Meta Conversions API (see §3.7) — your IP address is shared with Meta for ad attribution purposes.
5. Legal Bases Summary
| Processing activity | Legal basis |
|---|---|
| Foreground device location | Consent, Art. 6(1)(a) GDPR |
| Vibe search text sent to OpenAI | Performance of contract, Art. 6(1)(b) GDPR |
| Trip planning and local app preferences | Performance of contract, Art. 6(1)(b) GDPR |
| Recent places stored locally | Legitimate interests, Art. 6(1)(f) GDPR |
| Map, place, ticket, and experience discovery | Performance of contract and/or legitimate interests, Art. 6(1)(b) and Art. 6(1)(f) GDPR |
| Crash reporting and operational diagnostics | Legitimate interests, Art. 6(1)(f) GDPR |
| Infrastructure proxying and security logs | Legitimate interests, Art. 6(1)(f) GDPR |
| Mobile attribution (AppsFlyer) | Consent, Art. 6(1)(a) GDPR (IDFA) / Legitimate interests, Art. 6(1)(f) GDPR |
| Conversion event tracking via Meta Conversions API | Legitimate interests, Art. 6(1)(f) GDPR |
6. International Transfers
Some providers process data outside the European Economic Area, including in the United States. Where required, transfers are protected by appropriate safeguards such as the European Commission's Standard Contractual Clauses, data processing agreements, or other lawful transfer mechanisms. The current list of third-party providers is available in our Third-Party Provider List.
7. Retention
| Data category | Retention |
|---|---|
| Current trip plan / itinerary state | In app memory only; cleared when the app restarts |
| Preferences and recent places | Stored locally on your device until app data is cleared or the App is uninstalled |
| Vibe search queries | Not retained by Vis2Go after processing through the proxy |
| Crash logs and Sentry metrics | Typically 90 days in Sentry |
| Infrastructure request routing | No application database or persistent request-body storage configured by Vis2Go |
| AppsFlyer attribution data | Retained by AppsFlyer per their privacy policy |
| Conversion events (Meta CAPI) | Not retained by Vis2Go; forwarded immediately to Meta |
| Provider logs | Retained by each provider according to its own privacy terms |
8. Your Rights
Under GDPR, you may have the right to:
- access your personal data;
- correct inaccurate data;
- request deletion;
- restrict processing;
- object to processing based on legitimate interests;
- receive portable data where applicable;
- withdraw consent at any time;
- lodge a complaint with a supervisory authority.
To exercise your rights, contact hello@vis2go.com. Because Vis2Go does not currently provide accounts and does not store trip data on its own servers, many requests can only be fulfilled practically on your device. You may lodge a complaint with the Estonian Data Protection Inspectorate or with your local EU/EEA supervisory authority.
9. Children's Privacy
Vis2Go is not directed to children under 16. We do not knowingly collect personal data from children under 16. If you believe a child has provided personal data to us, contact hello@vis2go.com.
10. Security
The Vis2Go mobile App does not use cookies. We do not use web tracking pixels or fingerprinting. No native Meta/Facebook SDK is installed in the App. We use AppsFlyer for attribution — IDFA may be collected on iOS with ATT consent (see §3.6).
We use server-side conversion tracking via Meta's Conversions API. When you perform key actions in the App, an event signal (type only) and your IP address (captured server-side) are forwarded to Meta for ad attribution purposes. See §3.7 for full details.
We use reasonable technical and organisational measures to protect personal data, including:
- HTTPS/TLS for network requests;
- server-side proxying for selected provider API keys;
- no Vis2Go account database in the current version;
- no persistent server-side storage of trip plans;
- device-local storage for preferences and recent places;
- restricted provider keys where supported;
- diagnostic data minimisation.
No method of transmission or storage is completely secure.
11. App Store and Google Play Privacy Disclosures
This policy is intended to align with Apple App Privacy and Google Play Data Safety disclosures.
| Data type | Collected | Linked to user | Tracking |
|---|---|---|---|
| Precise or approximate location | Yes | No | No |
| Crash data and diagnostics | Yes | No | No |
| Performance data / operational metrics | Yes | No | No |
| Search text for vibe search | Yes, when submitted | No | No |
| Contact info | No | No | No |
| Financial data | No | No | No |
| Advertising identifiers (IDFA with ATT consent on iOS; GAID on Android) | Yes, via AppsFlyer | No | Yes (attribution) |
| IP address (server-side, Meta CAPI) | Yes, server-side | No | Yes (forwarded to Meta for ad attribution) |
| Conversion event types (Search, ViewContent, Contact) | Yes | No | No |
12. California Privacy Rights (CCPA/CPRA)
We do not sell your personal information. We share advertising identifier and attribution data with AppsFlyer (see §3.6) and event-type and IP address data with Meta (see §3.7) for advertising measurement purposes. This may constitute "sharing" under CPRA for cross-context behavioural advertising purposes. You may opt out by contacting hello@vis2go.com.
13. Changes to This Policy
We may update this Privacy Policy when the App changes or when legal, technical, or provider requirements change. Material changes will be communicated in the App or through another appropriate channel.
14. Contact
| Company | Vis2Go OÜ |
| Registry code | 16462903 |
| Address | Harju maakond, Tallinn, Pirita linnaosa, Ranniku tee 35, 12113, Estonia |
| Website | https://vis2go.com |
| Representative | Vaidas Rudis |
| Official queries | hello@vis2go.com |
| Support | info@vis2go.com |