Privacy Policy
Effective 24 June 2026 · version 8 · Previous versions
Adds disclosures for trip plans and guides, saved guides and remixes, public discovery and search of public content, third-party booking suggestions and affiliate links (Travelpayouts and travel-inventory partners), Mapbox maps, and updated AI / trip-guide data flows.
AutoVlog Privacy Policy
Effective date: 24 June 2026 Version: 8
This Privacy Policy explains how we collect, use, share and protect your personal data when you use the AutoVlog mobile application and the website at www.autovlog-app.com (together, the "Service").
We follow the European General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR"), the Slovenian Personal Data Protection Act (ZVOP-2), the Slovenian Electronic Communications Act (ZEKom-2) and the Slovenian Consumer Protection Act (ZVPot-1).
1. Who we are
The data controller responsible for your personal data is:
Računalniške storitve REK, Mihael Rek s.p. Ulica heroja Jevtiča 5, 2000 Maribor, Slovenia Matična številka: 7412037000 Davčna številka: 89184882 Privacy contact: support@autovlog-app.com Postal contact: the address above
We act as the controller under GDPR Article 4(7) for personal data processed through the Service. We have not appointed a Data Protection Officer; under GDPR Article 37 a DPO is not required for our scale and processing activities. You can reach our privacy contact directly at the email or postal address above.
2. What we collect
We collect only the personal data we need to deliver the Service, comply with our legal obligations, and protect the Service against abuse. We never sell your personal data and we never share it for third-party advertising.
2.1 Identity and account data
When you create an account or sign in, we collect:
- Your email address
- A user-chosen handle (username) and optional display name
- An identifier from your chosen sign-in provider — the opaque Apple user identifier (Sign in with Apple), or your Google account ID and the email/name claims you choose to share (Google Sign-In)
- Passkey credentials (WebAuthn public key, credential ID) for two-factor authentication, if you enroll one
- An optional avatar image that you upload
- An optional phone number in E.164 format, if you add it in your profile — stored alongside a one-way SHA-256 hash to allow contact matching (see §2.7). Clearing the field in Settings removes both. We never use your phone number for marketing or SMS notifications.
Profile visibility. Profiles are private by default. If you choose to make your profile Public in Settings → Account → Profile visibility, your handle, display name and avatar become visible to all AutoVlog users and to any unauthenticated visitor of www.autovlog-app.com/@<handle>. Your vlog count, follower count and following count are also shown on that public profile page. You can revert to private at any time; doing so immediately hides your profile page from non-followers.
Public profiles, public vlogs and published trip guides are also discoverable through in-app search and through the discovery and search features on www.autovlog-app.com — including by visitors who are not signed in — and may be indexed by external search engines. Only content you have made public is exposed this way; private profiles, private vlogs and unpublished plans are not.
2.2 Device data
When the app connects to our backend, we collect:
- A device identifier generated locally on first launch
- The Apple Push Notification Service token that allows us to deliver push notifications you have asked for
- Your device's platform (iOS), app version, build number and locale (e.g.,
sl_SI) - The IP address of API requests and a short User-Agent string (kept in session records to detect token theft and to revoke compromised sessions)
2.3 Content and media data
AutoVlog generates short vertical vlogs from media you choose. To do this we process, on your device:
- Photos and videos you select from your camera roll
- The technical metadata of those assets — creation timestamp, duration, resolution, frame rate, video codec, perceptual hashes (for deduplication), aesthetic scores (computed locally with Apple's Vision framework), and any EXIF location the camera embedded
- GPS waypoints (latitude, longitude, altitude, speed) sampled from location-tagged assets and used to compose the vlog's route
- Reverse-geocoded city and country names derived from those coordinates
When you save a vlog to the cloud (subscribers only), the following data is uploaded to our backend:
- The rendered vlog video file (MP4) and thumbnail image
- A composition snapshot in JSON form — the title, mood, music selection, captions, asset references, GPS waypoints, peak altitude and reverse-geocoded city/country
- The size of the file and our internal storage key
If you do not save a vlog to the cloud, none of this is uploaded — it stays on your device.
Trip plans and guides. AutoVlog can turn a trip into a structured trip plan or guide — a day-by-day itinerary with places and stops (their names and coordinates), a route, written notes and tips, and photos you attach to individual stops. A guide may also include GPS route tracks you import (for example from a .gpx file — a sequence of latitude/longitude/elevation points and the timestamps recorded with them) together with the type of activity (such as a hike or a bike ride). We store this so we can show and let you edit your plan. When you publish a guide it becomes public content that others can view and save (see §2.1 here and §8.8 of the Terms); a plan you keep private stays in your account and is not shown to other users.
2.4 Usage and behaviour data
To improve the auto-selection algorithm and protect against abuse we record, server-side:
- Auto-select telemetry events — anonymised at the algorithmic level (per-asset decisions, asset actions, composition completions and abandonments). Stored in monthly partitions and deleted after 30 days; aggregated rollups are retained for up to 2 years.
- Abuse signals — rate-limit breaches, schema rejections, deduplication storms, oversize batches. Used to detect and block automated abuse.
- AI quota ledger — a per-month count of AI editorial requests you have made, with a request identifier (no content).
- AI call log — for each AI editorial request: model used, token counts, cost, latency, error code (if any). The request body itself is not retained.
If you turn on telemetry opt-out in Settings, we no longer record auto-select telemetry for you. Abuse signals and AI call logs are kept under our legitimate interest in operating the Service safely.
2.5 Diagnostics
We use Firebase Crashlytics and Apple's MetricKit to collect crash logs and performance diagnostics. These include:
- Crash stack traces and the application state at the moment of the crash
- Performance metrics (launch time, hangs, energy, disk space)
- Your user identifier (so we can correlate crashes with the affected account and reach you if there is an account-level problem)
2.6 Billing data
We use RevenueCat (and, for App Store purchases, Apple) to manage subscriptions and one-time in-app purchases. We receive, depending on the product:
- Your subscription status (active / trial / grace / expired / canceled / refunded), the plan you are on, the billing period and the anniversary day — for auto-renewing subscriptions (Traveler / Daily Vlogger)
- A record of one-time purchases — product ID, purchase date and the AI-vlog quota credited to your account — for consumable AI vlog packs (10 / 20 / 100)
- A non-financial purchase or subscription identifier issued by RevenueCat or Apple
Apple is the merchant of record for App Store purchases. We never see your payment card or bank account details.
2.7 Contacts (optional)
When you tap "Find friends from your contacts" in the Search tab, AutoVlog asks iOS for permission to read your address book. If you grant it:
- We compute a one-way SHA-256 hash of each contact's email address and phone number on your device.
- We send only the hashes to our servers. We discard them after the lookup completes.
- We never store your contacts, their names, their phone numbers, or their email addresses on our servers.
- If a contact's own AutoVlog account email or phone matches one of those hashes, we show them to you so you can follow them.
You can revoke contacts access at any time in iOS Settings → Privacy & Security → Contacts → AutoVlog. If you deny or revoke access, the feature is simply unavailable — no other functionality is affected.
2.8 Social graph and interactions
When you use the social features of the Service, we collect and store the following data:
- Follow relationships. When you follow another user, or when another user follows you, we record the follow relationship, the user identifiers involved, and the timestamp. Your follower count and following count are displayed on your public profile if it is public. The identities of your individual followers and followees are not currently shown to other users — only aggregate counts are.
- Hearts (likes). When you heart a vlog, we record the interaction linked to your account, the vlog identifier, and a timestamp. The vlog's total heart count is visible to the creator and, on public vlogs, to all viewers. We do not currently display which specific accounts hearted a vlog to third parties.
- Block relationships. When you block a user, we record the block so that it can be enforced consistently across the Service. Block relationships are not visible to the blocked user or to third parties.
- Comments. When you post a comment on a vlog, we store the comment text, your account identifier, the identifier of the vlog, and a timestamp. A comment on a public vlog is visible to anyone who can see that vlog. You can delete your own comments, and the creator of a vlog can delete comments on their vlog or turn comments off; deleting a comment removes it from the Service (subject to backup rotation). We may notify a creator that you commented on their vlog.
- Companion tags and trip groups. When you tag another user as a companion on a trip — or another user tags you — we record the tag and the identifiers of the participants, the trip and trip-group identifier, each participant's own point-of-view (POV) vlog reference, and timestamps, so the participants' POV vlogs of the same trip can be presented together. This means another user can associate your account with a trip by tagging you, and you can do the same to them. Each participant controls their own POV vlog and its visibility, may decline or remove a tag, and may leave the trip group; doing so removes their participation and POV vlog from the shared trip. Companion stat cards generated from this data (for example, "You & @handle") may include the other participant's handle, display name, avatar and aggregate trip statistics.
- Saved guides (bookmarks). When you save another user's published trip guide, we record that you saved it, the guide identifier and a timestamp, so you can find it again and so the creator can see an aggregate count of how many people saved their guide. We do not show creators the identities of individual savers.
- Guide lineage (remixes). When you create a trip guide inspired by another published guide, we record the link between the two guides ("inspired by") and may display that attribution publicly, so the original creator is credited.
Social graph data is used solely to operate the social features of the Service and to protect users from harassment. We do not sell, license or share it with third parties for advertising, profiling or any purpose other than operating the Service.
2.9 What we do NOT collect
To be specific: we do not collect health or fitness data, browsing history outside our app, search history, sensitive personal data within the meaning of GDPR Article 9, or financial information beyond purchase history. We do not access your contacts without your explicit permission (see §2.7 for how contact matching works when you opt in). We do not use your data for tracking across apps or websites (see §2.10 for how third-party booking links work when you choose to tap one).
2.10 Booking suggestions and affiliate links
Inside trip guides we may show booking suggestions — such as stays, flights, activities, airport transfers or eSIM data plans — from third-party travel partners. To produce them we send a partner, or our affiliate-link provider, only the non-personal inputs needed for the lookup: a guide's destination place names and coordinates and, for flights, the major airports nearest your home region. We do not send your name, email, account identifier or device identifier to these partners.
When a suggestion is an affiliate link and you tap it, you are redirected out of AutoVlog to the partner's own website or app. From that point the partner is the controller of any data you give it, and its own privacy policy and cookies apply. So that the click can be attributed for our commission, our affiliate provider receives an attribution code that identifies the guide and its creator — not you. We also keep an internal, append-only log of these clicks (the guide, the creator and the partner's domain, with a timestamp) to calculate earnings; that log contains nothing that identifies the person who clicked.
We do not sell your personal data and we do not share your identity with these partners for advertising. Tapping a booking suggestion is always optional. The processors and partners involved are listed in §5.
3. Why we process your data and on what legal basis
| Purpose | Data categories | Legal basis (GDPR Art. 6) |
|---|---|---|
| Create and manage your account | Identity, Device | Art. 6(1)(b) — contract performance |
| Generate vlogs (on-device + cloud render) | Content, GPS, Identity | Art. 6(1)(b) — contract performance |
| AI-assisted editorial suggestions | Limited Content metadata, GPS timeline | Art. 6(1)(b) — contract performance |
| Music suggestions (music catalogue lookup) | Mood / activity / location keywords | Art. 6(1)(b) — contract performance |
| Billing and entitlements (subscriptions + one-time purchases) | Billing, Identity | Art. 6(1)(b) — contract performance |
| Security, abuse prevention and audit logging | Device, IP, Abuse signals | Art. 6(1)(f) — legitimate interests |
| Crash diagnostics and performance monitoring | Diagnostics | Art. 6(1)(f) — legitimate interests |
| Auto-select algorithm improvement | Auto-select telemetry | Art. 6(1)(f) — legitimate interests (with opt-out) |
| Contact matching ("Find friends") | On-device SHA-256 hashes of contact emails and phones — not stored server-side | Art. 6(1)(a) — your consent (revocable in iOS Settings → Privacy & Security → Contacts → AutoVlog) |
| Public profile display | Handle, display name, avatar, vlog count, follower and following count (public profiles only) | Art. 6(1)(b) — contract performance |
| Social interactions (follow, heart, block) | Follow and block relationships; heart interactions; all with timestamps | Art. 6(1)(b) — contract performance |
| Comments on vlogs | Comment text, author identity, vlog identifier, timestamps | Art. 6(1)(b) — contract performance |
| Companion tagging, POV vlogs and trip groups | Participant identifiers, trip / trip-group membership, POV vlog references, timestamps | Art. 6(1)(b) — contract performance |
| Create, store and publish trip plans and guides | Content, GPS, attached photos | Art. 6(1)(b) — contract performance |
| Saving guides and guide lineage (remixes) | Save records, guide identifiers, "inspired-by" links, timestamps | Art. 6(1)(b) — contract performance |
| Discovery and search of public content | Public profile, vlog and guide data | Art. 6(1)(b) / Art. 6(1)(f) — contract + legitimate interests |
| Booking suggestions and affiliate attribution | Destination place names / coordinates, home-region airports (no identity); click-attribution log | Art. 6(1)(f) — legitimate interests (offering relevant travel options and funding the Service) |
| Content moderation and safety | Cloud-stored vlog files accessed by authorised staff in strictly limited circumstances (see §5) | Art. 6(1)(f) — legitimate interests (safety, legal compliance) |
| Use of precise location | GPS, EXIF location | Art. 6(1)(a) — your consent (revocable in iOS Settings → Privacy) |
| Sending push notifications you asked for | Device token, content | Art. 6(1)(a) — your consent (revocable in iOS Settings → Notifications) |
| Compliance with legal obligations | All categories as required | Art. 6(1)(c) — legal obligation |
Where we rely on legitimate interests, we have weighed them against your fundamental rights and freedoms. You can object to that processing at any time (see Section 8).
4. Automated decision-making
AutoVlog uses artificial intelligence (Anthropic's Claude model, via our backend) to suggest an editorial composition for your vlog — which clips to feature, in what order, and with what tone. These suggestions are not solely automated decisions within the meaning of GDPR Article 22(1): you can always preview, edit, override or discard them before exporting your vlog. They produce no legal or similarly significant effect on you. We do not profile you for credit, employment or other consequential purposes.
We also use the same AI to draft and enrich trip-guide text — titles, descriptions and tips. For a plan you keep private, the request may include the place-names of your home and base location and your trip dates as context, so the suggestions are more relevant; this text is likewise a non-binding suggestion you can edit, accept or discard.
In line with EU AI Act Article 50 (transparency obligation for AI systems generating content), this Privacy Policy is the place where we tell you that AI is used to suggest editorial choices.
5. Who we share your data with
We share personal data only with the processors listed below, each acting under a Data Processing Agreement that complies with GDPR Article 28. We never sell your data.
| Recipient | Role | Data shared | Location |
|---|---|---|---|
| Anthropic, PBC | AI editorial and trip-guide suggestions (Claude API) | A summary of your trip — asset count, drone ratio, reverse-geocoded place names, GPS timeline (lat/lon/altitude/speed), drone clip summaries; for trip-guide text, a summary of the guide and, for a private plan, your home/base place-names and trip dates. No photos or videos. No email, no user ID. | United States |
| RevenueCat, Inc. | Subscription and one-time purchase state management | A pseudonymous user ID, your plan and status (for subscriptions), purchase records (for one-time AI vlog packs), and relevant timestamps | United States |
| Cloudflare, Inc. (R2) | Object storage of cloud-saved vlogs and avatars | The vlog video, the thumbnail, your avatar | EU + United States |
| Google LLC (Firebase Crashlytics) | Crash reporting and performance diagnostics | Crash stack traces, MetricKit payloads, user ID | United States |
| Apple Inc. | App distribution, Sign in with Apple, App Store payments, push notifications | What Apple needs to deliver each function | United States and EU |
| Google LLC (Sign-In) | OAuth authentication if you choose Google | OAuth ID token, your email and name claims | United States |
| Jamendo SA | Music catalog search | Anonymous mood / activity / location keywords. No PII. | Luxembourg (EU) |
| Travelpayouts (Go Travel Un Limited) | Affiliate-link generation and click attribution for booking suggestions | A pseudonymous attribution code identifying the guide and its creator (not the clicking user); destination keywords. No clicking-user identity. | Cyprus (EU) and United States |
| Travel-inventory partners (incl. LiteAPI for stays, Aviasales for flights) | Supplying the accommodation and flight options and prices shown in guides | Destination place names and coordinates; home-region airports. No PII. | EU and United States |
| Mapbox, Inc. | Map tiles, 3D terrain and tour-video rendering for trip-guide maps | Map-tile and styling requests, including the map area being viewed (approximate location) and your IP address | United States |
| AutoVlog authorised staff | Content moderation, technical support at user request, legal compliance | Cloud-stored vlog video files and thumbnails — accessed only in the strictly limited circumstances described below | Slovenia (EU) |
Staff access to private content. Your cloud-saved vlogs are encrypted at rest and are not browsed by staff in the ordinary course of business. An authorised administrator may access the content of a specific vlog only in the following three circumstances: (a) investigating a credible report of illegal or harmful content submitted through the in-app reporting flow or by a competent authority; (b) responding to a valid legal order or binding request from a law-enforcement or judicial authority; or (c) diagnosing a technical fault at your express written request to
support@autovlog-app.com. Every access is recorded in an audit log — which staff member, which vlog, the timestamp, and the reason. You may request a copy of the audit log relating to your own content at any time by writing tosupport@autovlog-app.com.
We may also disclose personal data (a) to comply with a legally binding request from a competent authority, (b) to protect our or others' rights, property or safety, (c) in connection with a corporate transaction (merger, acquisition or sale of assets), in which case the recipient will be bound by privacy commitments at least as protective as these.
Booking partners you are redirected to. When you tap a booking suggestion you may be sent to an independent travel provider — for example Booking.com, Agoda, Klook, Tiqets or Airalo. Once you leave AutoVlog these providers are not our processors: they act as independent controllers under their own privacy policies. We do not pass identifying information about you to them; any data they hold about you results from your own interaction with their website or app.
6. International transfers
Some of our processors are based outside the European Economic Area, primarily in the United States. When we send personal data there we rely on the Standard Contractual Clauses approved by the European Commission (Decision 2021/914) under GDPR Chapter V, supplemented by additional safeguards where appropriate. You can ask us for a copy of these clauses by writing to support@autovlog-app.com.
For the United States specifically, we additionally rely on the EU–US Data Privacy Framework where the recipient is certified.
7. How long we keep your data
| Data | Retention |
|---|---|
| Account, profile, billing | For the life of your account, then 30 days soft-delete grace, then permanent erasure |
| Cloud-saved vlogs and avatars | Until you delete them, or until your account is permanently erased |
| Cloud-saved vlogs after a paid plan ends | Soft-deleted (hidden, recoverable) when your subscription lapses, is cancelled and expires, or is downgraded to a plan without cloud backup; permanently erased 30 days later unless you resubscribe to a cloud-backup plan within that window |
| Comments | Until you or the vlog's creator delete them, or your account is permanently erased |
| Companion tags, POV references and trip-group membership | Until a participant removes the tag or leaves the trip group, or the account is permanently erased |
| Trip plans and guides, and photos attached to them | Until you delete them or your account is permanently erased; a published guide is kept after your account or subscription changes (Terms §8.8) until you delete the guide |
| Saved-guide (bookmark) records and guide-lineage links | Until you remove the save or the link, or your account is permanently erased |
| Affiliate click log | Up to 24 months for earnings and accounting; contains no clicking-user identity and may be retained in aggregated, de-identified form beyond account deletion |
| Sessions and refresh tokens | 30 days, or until revoked |
| Auto-select telemetry events | 30 days (monthly partitions are dropped) |
| Auto-select aggregate rollups | Up to 2 years (no per-user data) |
| AI call logs | 12 months for cost and abuse analysis, then aggregated |
| Abuse signals | 24 months |
| Crash diagnostics (Firebase) | Per Firebase's retention — typically 90 days for crashes, 30 days for performance |
| Acceptance records (legal documents) | For the lifetime of your account, plus 6 years after deletion (Slovenian limitation period for civil claims) |
| Backups | Encrypted off-site backups, rotated within 30 days |
When you delete your account we erase or anonymise your personal data within 30 days unless we are legally required to keep it longer (for example, billing records under Slovenian tax law).
Cloud backup is a paid feature. If a paid plan with cloud backup lapses, is cancelled and then expires, or is downgraded to a plan without cloud backup, the vlogs stored in your cloud are soft-deleted immediately (hidden from your feed but recoverable) and permanently erased 30 days later. Resubscribing to a cloud-backup plan within those 30 days restores them. Vlogs saved on your device are never affected, and you can download your cloud vlogs to your device at any time before the 30 days elapse.
8. Your rights
Under the GDPR you have the rights to:
- Access the personal data we hold about you (Art. 15) — in-app at Settings → Account → Export my data, or by emailing
support@autovlog-app.com - Rectify inaccurate or incomplete data (Art. 16) — most fields are editable in Settings → Account; for the rest, email us
- Erase your data, the "right to be forgotten" (Art. 17) — in-app at Settings → Account → Delete my account, or by email
- Restrict processing while a dispute is being resolved (Art. 18)
- Receive a portable copy in a structured, machine-readable format (Art. 20) — same export as above
- Object to processing based on legitimate interests, including profiling (Art. 21)
- Withdraw consent at any time, where processing is based on your consent (Art. 7(3)) — without affecting lawfulness of processing before withdrawal
- Not be subject to a decision based solely on automated processing, including profiling, that produces legal or similarly significant effects (Art. 22) — see Section 4
- Lodge a complaint with a supervisory authority (Art. 77)
To exercise any right, write to support@autovlog-app.com. We will respond within one month of receiving your request (extendable by two further months for complex requests, in which case we will tell you why). Most requests are free; we may charge a reasonable fee or refuse to act on manifestly unfounded or excessive requests as permitted by GDPR Article 12(5).
If you believe we have not handled your data correctly, you can complain to the Slovenian supervisory authority:
Informacijski pooblaščenec RS Dunajska cesta 22, 1000 Ljubljana, Slovenia Phone: +386 (0)1 230 9730 Web: https://www.ip-rs.si
You may also contact the supervisory authority of your EU country of residence.
9. How to delete your account
You can delete your account at any time:
- In the app: Settings → Account → Delete my account. We will ask you to confirm.
- By email: write to
support@autovlog-app.comfrom the address on your account.
After confirmation, your account enters a 30-day grace period during which you can sign back in to recover it. After 30 days we permanently erase or anonymise your personal data. Some data may be retained beyond that window when we are legally required to keep it (for example, billing records under Slovenian tax law) — those records are kept only for the legally required period and only for the legally required purpose.
10. Children
AutoVlog is not directed at users under 15 years of age, which is the digital-consent age in Slovenia under ZVOP-2 (implementing GDPR Art. 8). We do not knowingly collect personal data from anyone under 15. If you believe a child under 15 has provided us with personal data, please contact us at support@autovlog-app.com and we will delete it.
For users under the age of 18 (the age of majority in Slovenia), parental authorisation may also be required for in-app purchases under the Slovenian Civil Code (OZ).
11. Security
We protect your personal data using:
- Encryption in transit — HTTPS / TLS 1.2 or higher for all client–server traffic
- Encryption at rest — Postgres data encryption and Cloudflare R2 object encryption
- Authentication — Sign in with Apple, Google Sign-In, or passkey-based two-factor authentication for high-risk actions
- Access control — admin access requires passkeys, an IP allow-list, and full audit logging
- Operational hardening — least-privilege roles, dependency scanning, and regular review of our security posture
No system is perfectly secure. We continually work to improve our defences and to detect, contain and notify in the event of an incident.
12. Data breach notification
If we become aware of a personal data breach within the meaning of GDPR Article 4(12), we will:
- Notify the Slovenian Information Commissioner (Informacijski pooblaščenec RS) within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to your rights and freedoms (GDPR Art. 33).
- Notify affected users without undue delay when the breach is likely to result in a high risk to their rights and freedoms (GDPR Art. 34), describing the nature of the breach, the likely consequences and the measures taken or proposed.
13. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. When we do, we publish the new version on www.autovlog-app.com/privacy together with the new effective date and an archive of all previous versions.
For material changes — for example, a new processor receiving sensitive data, a new processing purpose, or a change to your rights — we will ask you to review and accept the updated Policy in the app before you can continue using AutoVlog. For non-material changes (typo fixes, clarifications) we publish the new version without asking for re-acceptance, but you can always read the current text and the change log on the website.
We keep a permanent record of which version of this Policy you accepted and when, so we can demonstrate compliance.
14. Contact
For any privacy question or to exercise any of your rights:
- Email:
support@autovlog-app.com - Post: Računalniške storitve REK, Mihael Rek s.p., Ulica heroja Jevtiča 5, 2000 Maribor, Slovenia
For complaints you cannot resolve with us, please contact the Informacijski pooblaščenec RS as described in Section 8.
This Privacy Policy is also available in Slovenian at https://www.autovlog-app.com/privacy?locale=sl. In case of any discrepancy between the English and Slovenian versions, the Slovenian version prevails for users domiciled in Slovenia.