Ejectly Privacy Policy

Effective date: 29 September 2026

Prepared against the implementation reviewed on 28 September 2026.

1. Who we are and scope

Ejectly is a Water Eject & Speaker Test utility published by Optima Solutions S.r.l. for Android and iOS, with application identifier com.optimasolutions.ejectly.

Publisher/legal entity responsible for Ejectly: Optima Solutions S.r.l., registered office: Via S. Negretti 42, Bracciano (RM), Italy. Privacy contact details appear in section 12.

This policy explains processing on your device and processing through the services integrated into Ejectly. Ejectly has no account, login or publisher-operated backend. This does not mean that its third-party services process no personal information. Optima Solutions selects these integrations and remains your contact for processing carried out on its behalf.

2. Information processed directly by Ejectly

The installed mobile app plays bundled audio files locally. Its audio features work offline. It processes your selected frequency or sample channel, playback position, session status and controls on the device to operate playback. It uses device language and appearance settings to display the interface.

Ejectly does not request microphone access, record sound, upload audio, access contacts or read location sensors. It does not collect health information or user-generated content and has no form requesting your name, email address or an account password. Speaker Test is a listening tool, not a source of medical or hardware diagnostic records.

Manual frequency selection is held only for the current screen session. Playback state and the app's advertising eligibility counters are kept in memory, not saved as a session history or sent to a publisher backend. Network connections made by the SDKs below can disclose technical information independently of these local features.

3. Advertising: Google Mobile Ads / AdMob

Advertising can be disabled, use Google's official test advertisements during testing, or use configured production advertisements in supported release builds. Production advertising is currently supported on Android only. When advertising is enabled, Ejectly requests non-personalized ads. Ads are blocked until Google UMP permits requests and purchase status confirms that Pro is not active. No ads are shown on audio screens, including paused playback. An interstitial can be shown on returning Home after natural completion, subject to frequency limits.

Non-personalized or test advertising does not mean no data processing. Google's SDK documentation describes processing of IP addresses, identifiers available on the device, interactions and performance information for ad delivery, measurement and fraud prevention. IP addresses may indicate a general area even though Ejectly does not access device location. Data available to the SDK depends on platform, settings and consent. See Google's Android disclosure, iOS disclosure and Privacy Policy.

4. Consent: Google User Messaging Platform

When the advertising integration is enabled, Ejectly uses Google UMP to refresh consent information and present Google's form when required. This involves communication with Google to determine the applicable message and consent status. Consent choices can be retained by the SDK on your device. UMP processing can occur before an ad is requested and is separate from purchase processing.

Open Settings → Privacy choices to review or change choices when Google makes the privacy-options form available. Otherwise Ejectly displays an unavailability message. Privacy Policy is a separate action for reading this document. Declining personalization does not necessarily prevent all ad requests; Ejectly uses UMP's permission result. Audio features do not require accepting advertising personalization. See Google's UMP documentation.

5. Purchases and RevenueCat

When configured, RevenueCat initializes and checks purchase status even before you attempt a purchase. Ejectly uses the SDK's generated anonymous App User ID rather than an Ejectly account. This identifier can persist through SDK storage and is not a guarantee that transaction information is non-personal. Ejectly does not supply names, email addresses, custom customer attributes or advertising identifiers to RevenueCat through its integration. See RevenueCat customer identifiers.

RevenueCat processes purchase records and store transaction/receipt information to verify purchases, restore access and determine the pro entitlement. Its service also provides purchase reporting. Requests include technical SDK/platform and locale information needed by the service. Ejectly offers a one-time non-subscription Pro product, not a subscription. Payment is handled by the platform store, or its test environment during testing; Ejectly does not receive payment-card details. See RevenueCat's app privacy disclosure.

RevenueCat processes customer data on the publisher's behalf under its Data Processing Addendum. Its Privacy Policy explains the distinction between its own website/business data and data processed for app publishers. Requests about Ejectly purchase data should be directed to Optima Solutions using section 12. Store processing is also described in Google's Privacy Policy and Apple's Privacy Policy.

6. Analytics actually used

Ejectly's own analytics is disabled. Its internal event calls are discarded, with no analytics provider, event queue, storage or transmission. Consent does not enable this analytics component. This is distinct from Google's advertising measurement and RevenueCat's purchase reporting described above; disabling Ejectly analytics does not disable those services.

7. Purposes, retention and international processing

Processing serves local audio playback and interface display, consent management, advertising where permitted, and purchase verification/restoration.

Local session state is temporary as described in section 2. SDK consent preferences, identifiers and purchase caches may outlast a playback session. Clearing local app data or uninstalling the app does not by itself delete records held by Google, RevenueCat or a store, and may not remove every identifier retained by platform storage or backups.

Provider records may be retained to maintain consent, validate or restore purchases, prevent fraud and meet applicable obligations. The app does not define a fixed server-side retention period or implement an automatic server deletion schedule. Exact retention of records held by Google or RevenueCat is managed by those providers under their applicable policies and service arrangements, including publisher instructions where applicable. See Google’s retention information and RevenueCat’s Privacy Policy and Data Processing Addendum. Contact us about records processed on our behalf. We do not promise that uninstalling the app deletes third-party records.

Providers may process information outside your country, including in the United States. Google's policy describes international handling; RevenueCat's DPA describes processor obligations and transfer safeguards, including standard contractual clauses where applicable. This policy does not assert that all information stays in the EU or on your device.

8. Your rights and choices

Depending on applicable law, you may have rights to access, correct, delete or receive a copy of personal information, restrict or object to processing, withdraw consent and complain to a competent data-protection authority. Contact us using section 12 to exercise applicable rights or ask about processing on our behalf. Because Ejectly has no login, information sufficient to identify the relevant purchase record may be needed; do not send payment-card numbers or passwords.

You can revisit available advertising choices in Settings, use your operating system's advertising controls, and use Restore purchases to check an existing entitlement. Restoring purchases is not a deletion request. Withdrawal of consent does not undo processing already carried out lawfully. See the providers' linked information for controls over processing they undertake independently.

9. Children's privacy

Ejectly does not ask for a birth date and has no age-verification or parental-consent flow. Ejectly is a general-purpose utility and is not specifically directed to children. If you are a parent or guardian concerned that a child has provided personal information through Ejectly's integrated services, contact us so the relevant records and appropriate action can be assessed.

10. Security

Local audio features avoid sending recordings or session histories to a publisher backend. Google and RevenueCat describe transport encryption and security measures in their linked documentation. No storage or transmission system can be guaranteed completely secure. This policy does not promise security certifications or controls that Optima Solutions has not established.

11. Changes to this policy

Updates will be published on this page with a revised effective date. Changes to data processing, service providers or advertising configuration will be reflected in the policy, with any additional notice or consent required by applicable law.

12. Contact

Optima Solutions S.r.l. — Ejectly privacy enquiries

Main privacy contact: privacy@optimasolutions.it.

Registered office: Via S. Negretti 42, Bracciano (RM), Italy.

Certified email (PEC): amministrazione@pec.optimasolutions.it.

Data Protection Officer (DPO): dpo@optimasolutions.it.

DPO correspondence address: Via Venezia 124 int. 5, 35129 Padova, Italy.

Phone: +39 049 8071490.