LensPing Privacy Policy

Effective date: October 4, 2026

This policy applies to the LensPing iOS app.

Who is responsible for your data

The data controller is Aleksey Martinovsky, Poland.

For any questions about your data, or to make a request, contact support@lensping.com.

What data we process

• Account data: identifiers and technical information for sign-in and account protection, language, and creation, activity and consent dates. Sign in with Apple uses an Apple identifier; we do not request your name or email. Guest accounts receive their own access identifier.
• Lens and eye health data: lens and vision parameters, wearing periods and replacement history, lens stock, wellbeing ratings, symptoms, eye drop use, doctor visit dates and results, and notes.
• Preferences: language, theme, reminder dates and settings, and markers for viewed educational content. Your phone's time zone is used for dates and reminders.
• Technical data: device and app information, usage events, installation identifiers and error diagnostics described below. Server logs may include IP address, request time and address, client information and processing results.
• Support requests: your email address, message and attachments needed to respond.

You enter lens and health data yourself.

Storage and sync

Lens and health records, language and reminder settings are stored on your phone and automatically synced to our server, including in guest mode. There is no separate mode without sync. Offline changes are sent later; only successfully synced records can be restored, provided you have access to the account.

The theme and viewed-content markers stay on your phone. Reminders are created locally with your permission. Their text may contain dates or lens stock counts and appear on the lock screen; you can change their display in iOS settings.

You can link an Apple ID to move guest data to another phone. If two sets of data conflict, you choose which to keep; the other is deleted.

Analytics and crash reports

Google Firebase Analytics receives events about sign-in, account actions, app setup, use of journal, lens and visit features, and screen views. They do not contain medical values, dates, symptoms or notes you entered, but indicate use of health-related features.

Event times, device model, iOS and app versions, language, approximate region derived from IP address, and installation and device identifiers are also processed. We do not send Firebase your account identifier or sign-in credentials, but events from the same installation can be linked: these data are not fully anonymous.

Firebase Crashlytics receives technical error and crash reports, including time, device information, installation identifiers and diagnostics. The app removes original error messages from reports it sends itself; automatic Firebase reports may contain error messages.

Usage statistics and crash reports are sent only with your consent. Collection is off by default: until you allow it, Firebase sends nothing. You can allow collection on the last step of the initial setup and change your choice at any time in Settings → “Statistics and crash reports”. The choice is stored on your device; signing out or deleting your account does not change it. The iOS advertising identifier is not collected, and ad personalization is disabled. See the Firebase documentation and Google Analytics documentation.

Why we process data and on what legal basis

• Account, sign-in and settings sync — performance of a contract, GDPR Art. 6(1)(b).
• Journal, calculations, reminders and record sync — consent, Art. 6(1)(a), and explicit consent to processing health data, Art. 9(2)(a).
• Service security and abuse prevention — legitimate interest in service security, Art. 6(1)(f).
• Usage statistics and crash reports — your consent, Art. 6(1)(a) GDPR and Art. 5(3) of the ePrivacy Directive. Consent is optional, the app works fully without it, and you can withdraw it in Settings.
• Responding to requests and meeting data protection duties — performance of a contract or legal obligation, Art. 6(1)(b), 6(1)(c), depending on the request.

Providing health information is voluntary. Consent to processing is requested at sign-in and its date is recorded. You can withdraw consent at any time by deleting your account or contacting support; this does not affect the lawfulness of earlier processing. The health journal and its sync cannot operate without processing this information.

We don't use your data for advertising, don't sell it, and don't make automated decisions based on it that have legal effects on you.

Who receives data

• Apple — information for sign-in and app integrity checks.
• Google — Firebase analytics and crash reports; support correspondence through Gmail.
• CGI Global Limited — server hosting in France, where accounts and synced records are stored.
• Cloudflare — hosting the policy and support pages and processing requests to them.

Journal contents are not sent to Apple for sign-in or to Google as analytics event parameters. If you include such information in a support email, it is processed by the email provider. Data may also be disclosed where required by law.

International transfers

Servers operated by Apple, Google, Cloudflare and the hosting provider may be located outside your country. This means your data may be transferred to and processed in other countries, including countries whose level of data protection differs from yours. We use these companies' services under the terms they offer to protect data in international transfers.

How we protect your data

Data transfers between the app and server are encrypted. Sign-in information is protected using secure device storage, encryption and hashing. The server processes synced records; this is not end-to-end encryption.

How long we keep data

• Account and synced records — while the account exists, unless a record is deleted earlier through an available app feature or on request.
• Technical sign-in records — session records remain with the account. Sign-in verification records are stored separately and are not automatically deleted when a check finishes.
• Inactive guest accounts may be removed manually by the owner; there is no fixed automatic deletion period.
• Firebase Analytics: retention of user and event data is configured in the Google Analytics project. It does not apply to standard aggregated reports. See Google Analytics retention rules.
• Firebase Crashlytics: according to Google, reports and associated identifiers are retained for 90 days, after which removal from live and backup systems begins.

Account deletion does not initiate removal of infrastructure logs, backups or support correspondence. Their retention depends separately on storage settings and the need to handle your request; you can ask the controller for details at the email address provided.

Deleting data

Delete your account via Settings → Account → "Delete account". Internet access is required. After a successful request, the account and associated records are removed from the primary server database; lens and health records and current sign-in information are cleared on the current phone, and reminders are cancelled. The account cannot be restored through the app.

Interface preferences may remain on your phone; copies on other devices are not remotely erased. Signing out and uninstalling the app do not remove server data, and sign-in information may remain in your phone's secure storage.

Account deletion does not remove previously collected Firebase data or reset its identifiers. These data are retained separately under the rules above.

Your rights

Under the GDPR (EU General Data Protection Regulation), subject to its applicable conditions, you have the right to:

• access your data and learn how it is processed;
• correct your data — some information can be changed directly in the app, the rest (for example, lens replacement history) on request to support@lensping.com;
• delete your data — by deleting your account in the app or by request;
• restrict or object to processing, including processing based on legitimate interest; consent to statistics and crash reports can be withdrawn in the app settings;
• receive your data in a portable format (data portability);
• withdraw your consent at any time — this does not affect the lawfulness of processing before withdrawal;
• lodge a complaint with a data protection supervisory authority — in Poland, the President of the Personal Data Protection Office (UODO); you can also contact the authority where you habitually live or work in the EU.

To exercise your rights, email support@lensping.com. For GDPR requests, the usual response period is one month; we will notify you within that period of any legally permitted extension and its reasons. We may need to verify account ownership. There is no automatic data export in the app — request it through support.

Children

The app is not intended for children under 16, and we do not knowingly collect their data. If you believe a child has provided us with data, contact support@lensping.com and we will delete it.

Changes to this policy

The current policy is available on this page, with its effective date at the top.