FMX

Privacy & data

Privacy Notice

FMX is account-free and stores memo content locally. This notice explains the app's verified data behaviour and the current website delivery and recovery services.

Version 12 October 2026 · Effective 12 October 2026

Publisher and controller

PITIP is the legal organization, publisher, and controller for FMX. PITIP uses PITIP-MITIM as its international/public short name and developer identity. PITIP-MITIM is not a separate legal entity.

No FMX account

FMX does not require an FMX account, email registration, a password, or a PITIP cloud login. A distribution store may separately manage a purchase, installation, entitlement, and update under its own terms. For direct delivery, PITIP uses the original purchase or grant email only to administer entitlement, secure delivery, recovery, and related support; this does not create an FMX account.

Memos and settings

FMX stores saved memos and settings locally in app-private storage on the Android phone. PITIP does not operate a server or cloud service for FMX memo storage.

Local data includes memo identifiers, text, active states and timestamps, the selected memo and display mode, rotation and pulse timing, appearance, position, and movement settings. The current app uses private Android SharedPreferences named fmx_state.

Internet, advertising, and analytics

FMX's memo storage and floating-memo functions work locally on the Android phone. No PITIP cloud connection or FMX account is required for normal memo use, and PITIP operates no FMX memo cloud. The current direct-distribution build has no Android INTERNET permission. FMX contains no PITIP advertising SDK and no PITIP analytics SDK.

Some store-specific builds may use network access where required for distribution-platform licence or entitlement verification. Huawei AppGallery DRM is the current specific example. This verification is separate from FMX memo storage and floating functions and does not send memo contents to PITIP.

Floating overlay and foreground service

Floating a memo requires Android's display-over-other-apps permission. FMX uses a foreground service and shows a visible notification while floating is active. The relevant manifest permissions are SYSTEM_ALERT_WINDOW, FOREGROUND_SERVICE, and FOREGROUND_SERVICE_SPECIAL_USE.

Speech-to-write

Speech-to-write is optional and starts only when the user requests it. FMX delegates recognition to an Android or device speech-recognition provider. FMX does not hold persistent RECORD_AUDIO permission, record audio itself, or save audio. The selected provider may use a network or process speech and text under its own terms and privacy practices.

Cloud backup and device transfer

FMX requests that its app data not be included in Android cloud backup:

  • The manifest sets android:allowBackup to false.
  • API 31 and later data-extraction rules exclude every FMX app-data domain from cloud backup.
  • API 26–30 full-backup rules exclude every FMX app-data domain.

PITIP does not operate an FMX backup server. Some Android or device-manufacturer migration and device-to-device transfer paths may remain controlled by the platform or manufacturer and can vary.

Removing local data

Clearing FMX app data or uninstalling FMX may remove saved memos and settings. Do not rely on PITIP for remote recovery because PITIP does not provide FMX cloud storage or backup.

Store and platform services

Distribution stores and platform services may separately process purchase, payment, installation, entitlement, refunds, updates, device information, or other platform data under their own terms and privacy practices. PITIP does not control those providers.

This website

This website includes no PITIP analytics, advertising tracker, session recording, customer account system, or contact form. Its code sets no marketing cookies. The public direct-checkout, secure-delivery, and account-free recovery functions process only the information needed for those services. Hosting and network providers may process ordinary technical request information for delivery, reliability, and security under their own policies.

The account-free update form accepts an email address and returns the same public response whether or not an eligible direct entitlement is found. PITIP normalizes the address and checks it against private FMX purchase records in the active payment environment. It is used to send a time-limited secure delivery message only where an eligible paid and active direct entitlement exists.

For a private direct purchase, PITIP records the purchaser's selected country of residence as purchase-bound evidence used to prepare the seller invoice and required tax records. A country reported separately by Stripe or PayPal is retained only as corroborative payment-provider evidence; it does not replace the purchaser's declaration or decide tax treatment by itself. Country evidence is retained with the purchase, invoice and accounting records for applicable tax, audit and legal retention periods.

The private commerce system may hold the canonical purchase email; product, package, price, currency, payment-provider and environment identifiers; provider transaction references; payment, refund, reversal and entitlement states; required consent and policy-version evidence; security event digests; secure-claim state and expiry; and transactional-email delivery state. PITIP does not store full card details or PayPal login credentials. Raw secure-claim tokens are not stored in the database; only a cryptographic digest is retained.

A direct purchaser may optionally provide a separate business billing identity so PITIP can issue and deliver an accounting document. This may include the legal or business name, registered address, company or registration number, national tax number, VAT ID, and a separate invoice email. The invoice email may differ from the canonical purchase email. The canonical purchase email remains the authority for the FMX purchase, secure delivery, and update recovery; billing details do not transfer that authority or create an FMX account.

Where an EU VIES check is requested for a supplied VAT ID, PITIP sends the normalized country code and VAT number to the official EU VIES service for VAT-identification verification. PITIP may retain the check time, result, request reference, and any name or address returned by VIES as verification evidence. A VIES result does not by itself prove ownership, identity, entitlement, or the correctness of every billing field. PITIP does not use VIES to transfer FMX ownership or recovery authority, and a returned VIES name or address does not automatically replace the purchaser-supplied invoice identity.

Vercel hosts the website, Supabase provides the private database (including private accounting records), private APK storage, and private invoice PDF storage, and Resend sends FMX transactional email. Stripe and PayPal process their respective payment and payment-event data. These providers process information as necessary to supply their services and under their own applicable privacy terms. Store purchase and update information remains separate and store-managed.

Invoice and accounting information may be processed in PITIP's accounting system as necessary for bookkeeping, tax, audit, and legal obligations. Processing is limited to the information required for those purposes and remains subject to PITIP's accounting controls.

If a customer contacts FMX about support, withdrawal, a refund, payment, delivery, or an invoice correction, PITIP processes the correspondence and the identifiers needed to investigate and respond. An invoice attachment is optional. Customers should not send passwords, card details, PayPal credentials, API keys, or other unnecessary payment or security credentials.

Purchase, entitlement, provider-event, claim, and email-delivery records are retained for as long as reasonably necessary for delivery, security, audit, support, fraud prevention, dispute handling, and applicable legal obligations. Issued invoice PDFs, frozen billing snapshots, tax and VIES evidence, payment evidence, accounting exports, delivery history, and correction records may be retained for the period required by accounting, tax, or other applicable law. Revoked, expired, and redeemed claim records may be retained as security history, but they do not restore a revoked entitlement. Contact FMX support for an applicable privacy request.

Contact

Contact FMX support at fmx@pitip-mitim.si.