LEGAL

Privacy Policy

ELBA Solutions is a one-person indie studio. This page explains, in plain language, what happens to your information when you visit this website, use the contact form, or play one of the studio's games. It is also the official privacy policy for every ELBA Solutions app, on Google Play and on the Apple App Store.

Last updated: 24 October 2026

Permanent address of this policy: https://elba-solutions.com/privacy-policy

The short version

This website has no ad pixels and shows no ads. It does use Google Analytics to count visits and see which pages people read, which sets analytics cookies on your device. The studio's mobile apps are free and, with the exception of Snake, supported by ads: they display ads through Google AdMob, which uses your device's advertising ID. No account is required, the apps never ask for your email or contacts, never read your location, and no data is ever sold. Game data stays on your device, with two exceptions: Quizinho has a public ranking list that shows the nickname you choose, your country, and your score — and you can switch it off — and Mills and Four in a Row pass the name you type and your moves through a relay server while an online match is running. Most apps also send automatic crash reports to Sentry in the EU: technical details about the failure, never anything you typed.Snake goes furthest: it has no ads and no studio server, and the only thing it ever sends is such an anonymous crash report. Daily Weight Tracker is stricter still: its crash reports carry no error text at all, and your weight and health data never leave your phone.

Who is responsible

ELBA Solutions (Elbin Hasic, one-person studio, Bosnia and Herzegovina) is the data controller for this website and for the apps published under the ELBA Solutions developer account on Google Play and the Apple App Store. Contact: elba.solutions.dev@gmail.com.

What this website collects

Browsing the site does not require an account and places no advertising cookies on your device. Two kinds of cookie can be set: a language preference cookie, only after you switch languages yourself, and the Google Analytics cookies described in the next section. The web host keeps short-lived server logs (IP address, browser user-agent, requested URL, timestamp) for security and abuse prevention. These logs are not used to build profiles and are rotated on the host's standard schedule.

Website analytics

This website uses Google Analytics 4 (the gtag.js tag) so the studio can see how many people visit and which pages are useful. The tag sets first-party cookies (_ga and _ga_<id>) that hold a randomly generated identifier for your browser, and sends Google the pages you view, referrer, approximate location derived from your IP address, and basic device and browser information. IP addresses are anonymised by Google Analytics 4 and are not stored. The studio sees only aggregated reports and never uses this data to identify an individual visitor.

You can opt out at any time by blocking cookies for this site in your browser, using its "Do Not Track" or tracking-protection setting, or installing the Google Analytics Opt-out Browser Add-on.

The contact form

If you send a message through the contact form, the name, email address, optional subject, and message you provide are transmitted by email to the studio inbox. That information is used only to read and reply to your message. It isn't added to a mailing list, shared with third parties, or used for marketing. Messages are kept as long as needed to handle the conversation, then deleted.

Mobile games & apps

The games and apps published under ELBA Solutions on Google Play and the Apple App Store are free, work without an account, and — all except Snake — are supported by ads. In short:

No sign-up, no account. The apps never ask for your real name, email address, phone number, contacts, microphone or camera, and they never read your location. The one location permission any app requests is in Four in a Row, and only when you join a Bluetooth match, because Android requires it to search for nearby devices — see its section below. Quizinho, Four in a Row and Snake let you pick a nickname and, if you like, a profile picture through the system photo picker, which hands the app only the one picture you select. That picture never leaves your device.
Game data stays on your device. Progress, high scores, and settings are stored locally on your phone (some apps also allow them into your own Android or iCloud backup, others deliberately keep their data out of system backups). The studio operates no server that receives them — except for Quizinho's ranking list and question updates, and the online matches in Mills and Four in a Row, both described in the sections below. Quizinho can also export your profile and quiz history to a backup file you choose the location of yourself, optionally protected by a password you set; that file goes only where you put it and is never sent to the studio.
Ads are the exception. To keep the apps free, they display ads served by Google AdMob, and that advertising SDK does collect data. The "Advertising and the advertising ID" section describes exactly what. Snake is the exception to the exception: it shows no ads and contains no ads SDK. Before any ad appears, Quizinho, Mills, Four in a Row, Daily Weight Tracker, Lucky Wheel Spinner and some of the other apps also ask a small server run by the studio, admobcontrol.elba-solutions.com, once per launch whether this version of the app should show ads at all. That request carries only the app's identifier, the platform and the version number — nothing about you or your device.
Crash reports are the other exception. When an app crashes or hits an unexpected error, it sends a technical report so the failure can be found and fixed. It carries no game content and nothing you typed — see "Crash reports" below.

Quizinho: question updates and the ranking list

Quizinho talks to a server run by the studio (Mills and Four in a Row do too, for online matches — see the next section). It does so for two reasons: to download new and corrected quiz questions, and to show a public ranking list of players worldwide and by country. For that, the app sends the studio's server:

An installation identifier — a random ID the app creates on first launch, together with the platform (Android, iOS, Windows, or macOS) and the app version. It lets the server issue and revoke access tokens and limit how often a single installation can call it. It is not the advertising ID and is never linked to it.
Your ranking profile — the nickname you choose, the country you select, and the app's language, plus a random player identifier created on your device. The nickname starts out as a random code; replacing it is up to you, and it does not have to be your real name.
Your scores — total points, best single-quiz score, and number of quizzes played, sent after each quiz so your rank stays current.
IP address — visible to the server with every request, as with any internet connection. It is used only in memory, to limit abuse, and is not stored with your profile.

Your nickname, country, total points, and best quiz score are visible to every Quizinho player on the ranking list. Nothing else is shown — not your profile picture and not your identifiers — so choose a nickname you are comfortable showing publicly. Your profile picture, quiz history, answers, and settings stay on your device, and downloading questions carries no personal data.

Reporting and hiding nicknames: nicknames containing offensive words cannot be saved, and the server hides any such name from the ranking list. Next to every other player you can report an offensive nickname or hide that player. A report sends the server the reported player's identifier; the server adds your installation identifier and the nickname as it stands, and the studio receives the report by email so it can be reviewed, normally within 24 hours. A nickname reported by several players, or hidden after review, is shown to everyone as “Player #…” instead. Reports are kept for moderation and deleted together with the rest of your data on request. Players you hide are remembered only on your device and are never sent to the server.

Challenge (duel): a duel on one phone sends nothing. An online duel — a friend challenge by code, a random opponent or a rematch — sends the studio's server your nickname, country and the random player identifier, and for each question your answer and how long it took; the server calculates the points. Your opponent sees your nickname, your score and, once the duel is over, your answers question by question. The server keeps duel results and a duel rating that only you see, and a finished round may later be replayed to another player as a recorded round, without your name or country. The camera is used only to scan a challenge QR code: the code is read on the device, and no image is kept or sent. Reporting an opponent's nickname sends the duel code and your installation identifier; a nickname reported by several players is hidden from every opponent. Duel results and reports are erased with the rest on request.

Leaving the ranking list: in Profile → Settings, turn off Show me on the leaderboard. The app deletes your entry from the ranking list on the server and stops sending your nickname and scores. If you are offline at that moment, the deletion is sent the next time the app connects.

Deleting everything: leaving the ranking list removes your public entry, but the server keeps the nickname, country, and language you last sent, along with the installation record, so that switching back on restores your place. To have all of it deleted, email elba.solutions.dev@gmail.com with the nickname and country shown on the ranking list, and it will be removed within 30 days. Uninstalling the app alone does not remove this server data.

Mills and Four in a Row: online matches

Mills and Four in a Row each have an online 1v1 mode, and both use the same relay server; a game code from one game never pairs with the other. There is no account and no sign-up: one player creates a room and gets a short game code, the other types it in. The two devices exchange their moves through a relay server run by the studio, which forwards messages and knows nothing about the game itself — the rules and the board stay on the two devices. While a match is in progress, the relay sees:

The name you enter — passed to your opponent so each side knows who it is playing. It does not have to be your real name, it is tied to no account, and it is not stored once the match ends.
The moves in that match — forwarded between the two devices while the game runs and not kept afterwards. The server stores no game state and no match history.
IP address — visible to the server with every request, as with any internet connection. It is used briefly to protect the server from abuse (for example, too many wrong game codes), and the hosting provider may keep it in standard technical server logs for a limited time. It is linked to no profile.

The other game modes need no server at all: playing against the computer and two players on one device are entirely offline, and a Bluetooth match goes directly between the two phones without touching the internet.

Bluetooth in Four in a Row: only the name you chose and the moves are exchanged. While you host a game and wait for an opponent, your chosen name is broadcast so nearby phones can find the game, which means any Bluetooth device in range can see it. To join a game, Android requires the location permission before an app may search for nearby Bluetooth devices; the app asks for it only at that moment, and never reads or sends your location. Hosting needs no location permission. No record is kept of the devices you played against.

Daily Weight Tracker: health data stays on your phone

Daily Weight Tracker handles the most sensitive data of any studio app: body weight is health data, a special category under the GDPR. That is why it is built so the studio never receives any of it. The app stores, only in its private storage on your device:

What it keeps — your weight entries, the optional note and mood on each entry, your start and target weight, and the profile fields you choose to fill in: height, year of birth, sex and activity level (the last two exist only so the TDEE calculator can run). Every profile field is optional and can be cleared. Units, language, theme and reminder time are kept as settings. BMI, BMR, TDEE and the macro figures are calculated on screen and never stored.
What it sends — none of the data you enter. The app has no account and no analytics. It does send crash reports, more narrowly than the other apps — see the next point. Two things reach Google: the app asks the Google Play app on your device whether a newer version of itself exists, and it requests the advertising banner from Google AdMob. And once per launch it asks a small server run by the studio, admobcontrol.elba-solutions.com, whether this version of the app should show ads at all; that request carries only the app's identifier, the platform and the version number. The service logs which app versions asked and what they were told, keeps those logs for 31 days, and itself records no IP address and no device identifier. None of these requests carries your weight, goal, height, notes or anything else you typed. Reminders are scheduled on the device itself, with no notification server.
Crash reports — when the app crashes or logs an error, it sends a report to Sentry as described in the "Crash reports" section below, under stricter rules. The report carries the error type and its stack trace, the app version, the device model and operating-system version, the app's language, theme and unit, whether it shows ads, and the technical events just before the failure — but no error or log message text at all, because such text could contain a number you typed. It never contains a weight, goal, height, note or profile field, a screenshot, or a user identifier. The app also counts launches and crashes to measure how often it crashes; that count carries a random number the app creates itself. The legal basis is the studio's legitimate interest in an app that works (Art. 6(1)(f) GDPR), and there is no switch to turn it off.
Backups — Android's automatic cloud backup and the device-to-device transfer during phone setup are both switched off for this app, so no copy is made on your behalf. Instead you can save your own backup file from the More screen, encrypted (AES-256-GCM) either to the app or to a password you choose, or export a plain CSV file that contains your weight history and notes. Once you save or share either file, it is under your control and is never sent to the studio. A forgotten backup password cannot be recovered.
Advertising — the app shows one banner on its five main screens. You are asked for consent before the first ad is requested, and the ads SDK is not even started until that question is answered; you can change your answer at any time under More → Ad privacy settings. What the ads SDK collects is described in the advertising section below.
Adults only, not a medical device — the app is intended for people aged 18 and over. It records what you enter and does arithmetic on it; it gives no medical advice, diagnosis or treatment.

To delete your data, delete individual entries in the app, or uninstall it, which removes its storage. Because the studio never receives any of this data, there is nothing on the studio's side to request, export or delete. Crash reports cannot be found or deleted on request either, because nothing in them identifies you; Sentry deletes them after 30 days at most.

Snake: your data stays on your phone

Snake transmits and shares no personal data. Progress, records and settings, and the name and photo you choose for your profile, stay in the app's private storage on your device; the photo is copied from your gallery when you pick it and never leaves the device. Playing needs no internet. The app goes online for only two things: to ask the store whether a newer version exists — Google Play on Android; on iPhone and iPad the public App Store lookup, which receives only the app's identifier and your device's region — and to send anonymous crash reports as described in "Crash reports" below. The "Rate" and "Share" buttons open the store and the system share sheet. It contains no ads, no analytics and no studio server, so the advertising section below does not apply to it. On Android, cloud backup and device-to-device transfer are switched off, so nothing is copied to Google Drive or a new phone. On iPhone and iPad, iOS includes the app's data in your own iCloud or computer backup, as it does for every app; that happens within your Apple ID, and the app itself sends nothing. If you allow notifications, reminders are scheduled and delivered on the device itself. To delete everything, use "Reset progress" in Settings or uninstall the app.

Country City River: account, games and answers

Country City River (application id com.elbasolutions.dgs.app) is the only ELBA Solutions game with an account and a server of its own. The account is created for you as a guest on first launch — no email address, nothing to type — and registering with an email address is optional, so that the account survives a change of phone. The server keeps:

Account: the name you type, your avatar colour, the app's language and — if you register — your email address and your password in a form the original cannot be recovered from.
Device: a randomly generated number tying a guest account to that phone, and a sign-in token held in the device's secure storage. Neither is an advertising identifier and neither follows you outside the app.
Games: the game code, who played, the answers you type, the points per round and the votes cast in disputes. The other players at the same table see your answers — that is the game. A game is joined only with a five-character code its host hands out: there is no public list of games, no random matchmaking and no chat.
Statistics and progress: games played, wins, XP and level, achievements, coins and your solo record.
Your IP address, but only in the moment of the request, to limit how many accounts and games one address can create. It is not written to the database.
On the phone itself stay your settings, solo runs waiting to be sent, the downloaded word list and a local crash log. All of it is deleted with the app and is never sent to anyone.

The game contains no ads, no analytics, no crash-reporting tool and no third-party SDK of any kind, so the advertising and crash-report sections below do not apply to it. Data goes to the studio's own server and nowhere else, over an encrypted connection, and is shared with nobody. The coins in the game are earned by playing — they cannot be bought and cannot be cashed out.

An account and its statistics are kept while the account exists; a sign-in token lasts up to 180 days from its last use. The full policy for this game is built into the app itself, under Settings → Privacy, and reads offline.

Account deletion and data deletion requests

This section covers Country City River, the only ELBA Solutions app that creates an account. You can delete your account and its data yourself, and you can request deletion without having the app installed:

In the app: Settings → Delete account. The fastest way, and it needs no correspondence.
Without the app: send a request through the contact form, giving the email address the account is registered with and saying that you want your Country City River account deleted. A confirmation goes to the account's own address before anything is deleted, so nobody else's account can be deleted this way. A real person replies, normally within 30 days.
A guest account has no email address, so it cannot be recognised by one — it is deleted in the app. If the app is already uninstalled, write through the contact form with the name you used and roughly when you last played; a guest account holds no personal data beyond that name, so it is all we need to find it and delete it.

What is deleted. A guest account at once. A registered account after 30 days, so signing in within that window brings it back; after that the name is replaced with a neutral record, and the email address, the password and the link to the device are gone. Statistics, achievements, coins, solo records and every sign-in token go with the account.

What remains. The games you finished and the points scored in them, because they are part of the other players' results at the same table — but without you in them, under a neutral record. None of it leads back to your address, your password or your phone.

Advertising and the advertising ID

ELBA Solutions apps contain ads. Ads are delivered by Google AdMob (the Google Mobile Ads SDK), a Google service. The SDK runs inside the app, requests an ad from Google's ad servers, and displays it. The studio receives only aggregated, anonymous reports (impressions, clicks, revenue) — never data that identifies an individual player.

To serve and measure those ads, the Google Mobile Ads SDK collects the following and sends it to Google, which acts as an independent controller for advertising purposes:

Advertising ID — on Android the Google Advertising ID (AAID), on iPhone and iPad the Identifier for Advertisers (IDFA). Either way it is a resettable identifier the operating system provides specifically for advertising, used to cap repeated ads, to measure ad performance, and, where permitted, to select ads relevant to you. On iOS the app receives the IDFA only if you allow tracking in Apple's prompt described below.
Device and app information — device model, operating system version, language, screen size, app package name and version, and IP address.
Approximate location — derived from the IP address, roughly at country or region level. The apps never collect GPS or precise location and never pass a location to the ads SDK. The only location permission any app requests is Four in a Row's, solely because Android requires it to search for nearby Bluetooth devices, as described above.
Ad interaction data — whether an ad was requested, shown, viewed, or tapped, plus basic diagnostic and crash data from the ads SDK itself.

This data is used for advertising (showing ads and, where you consent, personalising them), fraud prevention, and measurement. The studio does not use it to build a profile of you, does not combine it with anything you send through the contact form, and does not sell it. Google's handling of this data is governed by the Google Privacy Policy and the Google Advertising Services notice.

If you are in the EU, the UK, or Switzerland, the apps show a consent dialog (Google's User Messaging Platform, aligned with the IAB Transparency & Consent Framework) before any personalised ads or non-essential data use. You can accept, refuse, or change your choice later from the app's privacy option. If you refuse, the app still works and still shows ads — they are simply non-personalised. Where consent is not legally required, personalised advertising relies on legitimate interest and you can opt out with the device settings listed below.

On iPhone and iPad there is a second prompt. After the consent dialog above, iOS itself asks, through App Tracking Transparency, whether the app may track you across other companies' apps and websites. If you say no, the app receives no advertising identifier and the ads it shows are non-personalised. Saying no never removes a feature and never leaves the app broken — it keeps working and still shows ads. You can change the answer at any time in the iOS settings listed below.

Crash reports

When an app crashes or hits an unexpected error, it sends an automatic report so the studio can find and fix the failure instead of waiting for someone to describe it in an email. This happens in the Android and iOS apps; the Windows and macOS builds contain no crash-reporting component at all.Daily Weight Tracker sends less than described here — see its section above. A report contains:

What is sent: the error and its stack trace (the technical path through the code), the app version and build, your device model and operating-system version, and basic context about the state the app was in — the app's language and theme, which screen or game mode you were on, and a short trail of the app's own technical log messages leading up to the failure.
What is never sent: your name or nickname, your game history or scores, the contents of anything you created (wheel names and entry texts in Lucky Wheel Spinner, game codes in Mills and Four in a Row), and no advertising identifier. Where such text could end up inside an error message, the apps replace it with a placeholder before the report leaves the device, and storage of IP addresses is switched off on the receiving side.
Who processes it: Sentry, a crash-reporting service, in its EU region — the reports are stored in Frankfurt, Germany. Only the studio can see them, and they are never used for advertising, analytics about you, or profiling.
How long it is kept: up to 30 days, then deleted automatically.

Crash reporting is on by default and has no separate switch in the apps: it collects no personal data, and an app that crashes silently for everyone is a defect the studio has no other way of learning about. If you would rather not send these reports, you can block the app's network access in your system settings, or stop using the app. On both platforms the store itself also collects its own crash reports separately — those are governed by Google's and Apple's policies, and on iOS by whether you agreed to share diagnostics with developers.

Store privacy declarations

This section mirrors the Data safety declaration on the studio's Google Play listings and the App Privacy declaration on its App Store listings:

Data collected: device or other IDs (the advertising ID), app activity limited to ad interactions, device and app diagnostics, and approximate location derived from the IP address. Snake declares none of these: it has no ads SDK, so its only entry is crash logs and diagnostics, described below.
Quizinho only, in addition: personal info limited to the nickname you choose, your selected country, and the app language; app activity limited to quiz scores; and device or other IDs (a random installation identifier and player identifier). This data is collected for app functionality — the ranking list and question updates — is not shared with third parties, is encrypted in transit, and can be deleted on request. Appearing on the ranking list is optional.
Crash logs and diagnostics: collected, not shared with anyone else, not optional, for app functionality — plus analytics in the narrow sense of how often the apps crash. Google Play groups these under App info and performance; on the App Store the same thing is declared as Crash Data for App Functionality, not linked to your identity and not used for tracking.
App Store specifics: the App Privacy declaration lists Device ID and Advertising Data for the ads SDK, marked as linked to you and used for tracking, which is why iOS shows the App Tracking Transparency prompt; and Crash Data, marked neither linked nor tracking. Mills' online mode declares nothing of its own: the name you type is not tied to an account and is not kept after the match. Daily Weight Tracker additionally declares Other Diagnostic Data (the launch and crash count), also neither linked nor tracking.
Data shared: the advertising data above is shared with Google AdMob for advertising and measurement. Nothing else is shared with any third party for its own purposes. Crash reports go to Sentry, and the online messages of Mills and Four in a Row pass through the relay server, as processors acting only on the studio's instructions — which is why both stores' forms record them as collected but not shared.
Purposes: app functionality, advertising or marketing, analytics limited to ad performance and crash rates, and fraud prevention and security.
Required or optional: ad delivery is required for these free, ad-supported apps to function. Personalisation of those ads is optional and consent-based wherever the law requires consent.
Security: everything the apps send — ad requests, crash reports, Quizinho's ranking data and the online messages of Mills and Four in a Row — travels over encrypted HTTPS connections. This website is served over HTTPS as well.
Deletion: the studio holds no user accounts. Crash reports delete themselves after 30 days, and nothing from an online match is kept once it ends. For Quizinho, leaving the ranking list removes your public entry, and an email to the studio removes everything described in the Quizinho section. You can reset or delete the advertising ID at any time in your device settings, and you can email the studio to have any correspondence you sent deleted.

Your choices and how to opt out

You stay in control of the advertising identifier on your own device:

Android — reset the advertising ID: Settings → Google → All services → Ads → Reset advertising ID. Earlier ad data can no longer be linked to the new identifier.
Android — delete the advertising ID: the same screen offers Delete advertising ID, which stops apps from receiving an identifier at all. Ads then become non-personalised.
iPhone and iPad — turn tracking off: Settings → Privacy & Security → Tracking lets you withdraw permission for a single app, or switch off Allow Apps to Request to Track for all of them at once. Settings → Privacy & Security → Apple Advertising separately controls Apple's own personalised ads.
Withdraw consent: where the consent dialog applies, reopen it from the app's privacy option and change your answer at any time.
Leave the Quizinho ranking list: Profile → Settings → Show me on the leaderboard. See the Quizinho section above.
Uninstall: removing an app deletes its local data from your device and ends all collection by that app. For Quizinho, leave the ranking list first, or email the studio, if you also want your server data gone.

Children

The studio's apps are not directed at children. They are not part of the Google Play Families programme, and their target audience on both stores is 13 years and older — except Daily Weight Tracker, which is intended for adults only and declared for ages 18 and over. The studio does not knowingly collect personal data from children under 13 (or the equivalent minimum age where you live). If you believe a child has provided personal data, email the studio and it will be deleted.

Retention and security

The studio runs no user database apart from Quizinho's. Crash reports are kept by Sentry for up to 30 days and then deleted. The relay server used by Mills and Four in a Row keeps nothing after a match ends, beyond whatever the hosting provider holds in its standard technical logs for a limited time. For Quizinho, the server keeps the installation record and the ranking profile described above until you ask for them to be deleted; access credentials are stored only as a one-way hash. Contact-form emails stay in the studio inbox only as long as the conversation needs, then are deleted. Server logs are rotated by the web host on its standard schedule. Advertising data and Google Analytics data are retained by Google according to Google's own retention periods, not the studio's. All traffic to this website, to the Quizinho server, to the online relay, to Sentry, and from the ads SDK uses encrypted HTTPS connections. The ad-mode server that Mills, Four in a Row, Daily Weight Tracker and the other apps using it ask at launch keeps its request logs (app, platform, version and the answer) for 31 days, records no IP address or device identifier, and is also reached over HTTPS.

Third-party services

These are the only third parties involved, and each has its own privacy policy:

Google AdMob — ad serving and measurement inside the apps. See how Google uses data from apps that use its services.
Sentry — crash and error reporting inside the Android and iOS apps, processing the reports described above in its EU region (Frankfurt, Germany). See the Sentry privacy policy.
Google Play — app distribution, updates, and the crash reporting the Play Store itself collects, all governed by Google's policies. Apart from the Google Mobile Ads SDK and Sentry, the apps embed no other third-party component — no Firebase, no analytics SDK, no social or tracking library.
Apple App Store — app distribution and updates on iPhone and iPad, plus the crash and usage diagnostics Apple itself collects and passes to developers only if you agreed to share them, all governed by Apple's policies. The iOS apps check the App Store for a newer version by version number; that check carries the app's identifier and, in Snake, your device's region so that the right storefront answers — nothing that identifies you.
Google Analytics — audience measurement on this website only (it is not embedded in the apps). See how Google uses data from sites that use its services.
Outbound links (LinkedIn, store pages, and similar) lead to services with their own privacy policies. Apart from Google Analytics, this website embeds no third-party trackers, social widgets, or ad pixels.

Your rights

Under the GDPR and similar laws, you can ask what personal data the studio holds about you, request a copy, a correction, or deletion, object to processing, withdraw consent for any future contact, or lodge a complaint with your local data protection authority. If you are a California resident: the studio does not sell personal information and does not share it for cross-context behavioural advertising in the CCPA/CPRA sense. Email elba.solutions.dev@gmail.com and you'll get a reply from a real person, normally within 30 days.

Changes to this policy

If anything material changes — new tools, new data flows, a new ad partner — this page will be updated before the change goes live, and the date at the top will reflect it. The address of this page stays the same, so the link filed with Google Play and the App Store always points at the current version.

Contact

Questions, concerns, or data requests? Reach out at elba.solutions.dev@gmail.com.