ItalianoEnglish

Privacy Policy — Eject

Last updated: 6 September 2026

Eject does one thing, and collects as little as possible to do it.

Data controller: MindContact — privacy@mindcontact.net

In short

• Eject creates no account, asks for no sign-up, and collects no name, email or contacts.
• We run no servers: no app data is ever sent to us.
• The only data leaving your device is what Google AdMob collects to serve ads.

Permissions and what they are for

Eject asks for nothing else: it does not use the microphone, it does not know where you are, it does not touch your photos or files. It makes a sound — it never listens to one — and every sample is computed on the device.

Advertising

Eject shows ads through Google AdMob. AdMob may collect and process:

• the device advertising identifier (Advertising ID / IDFA);
• the IP address and technical device information;
• ad interaction data.

Google processes this data as an independent controller. Policy and options: policies.google.com/technologies/ads

You can limit personalised ads from your system settings:

• Android — Settings › Privacy › Ads
• iOS — Settings › Privacy & Security › Tracking

In the EEA, the UK and Switzerland, Google's consent message appears on first launch; until you answer it, the app requests no ads at all.

Data that stays on the device

App preferences are stored on the device only and are removed when you uninstall the app.

Children

The app is not directed at children under 13 and does not knowingly collect their data.

Your rights

With no account and no backend, we hold no data about you and cannot identify you. For data processed by Google AdMob, exercise your rights directly with Google, using the contacts in its own policy.

Any question: privacy@mindcontact.net

Changes

Any change to this policy updates the date at the top. Previous versions remain in the history of the public repository mcma-docs.