Privacy policy

Last updated: 24 October 2026

The short version: the mappy app does not send your maps, app usage, or personal information to me.

Who is responsible

I am Dmitrii Russu, the independent developer operating mappy and the controller for the processing described in this notice. Apple and any cloud-storage provider you choose are responsible for the parts of their services that they control.

The mappy app

mappy works locally on your Mac. It does not create an account, connect to a server I operate, or include a developer-operated service that sends me your maps, app usage, analytics, telemetry, diagnostics, or crash reports. mappy has:

• no accounts and no sign-in,
• no developer analytics, telemetry, or crash-reporting service,
• no advertising or third-party data-collection SDKs,
• no developer-operated backend.

Your maps are plain files stored in the location you choose. Local preferences and recovery data also stay on your Mac. I cannot access any of them. You control these files and can delete them in mappy or Finder.

If you choose a synced location such as iCloud Drive, Dropbox, or OneDrive, the relevant provider syncs those files under your agreement with that provider. mappy does not send me a separate copy. Opening the privacy policy, a web link, or a support email from within mappy happens only when you ask it to and uses your default browser or email app.

This website

The mappy website has no account, contact form or advertising, and its analytics does not use cookies. The site is hosted and delivered by Netlify. When you request a page, Netlify automatically processes standard technical data such as your IP address, request time, requested page, browser or user-agent information, referrer, and response or security information.

This data is used to deliver the site, keep it reliable, and detect or prevent abuse. Where the EU or UK GDPR applies, the legal basis is my legitimate interest in operating and securing the website. Netlify Analytics also provides server-side traffic reports; these include requests that may come from bots and do not measure in-app activity. I do not keep a separate copy of visitor-level access logs. Netlify's current data-processing terms state that logs for service components are retained online for 90 days and offline for one year. Netlify may retain particular information longer where its legal obligations require it. See the Netlify DPA and retention notice.

Optional website analytics

I use Umami at metrics.mappy-ai.com to understand which public pages and features are useful and which links lead people to the App Store. Reports include page visits, referring website domains, browser and operating-system information, approximate location, coarse screen size, page performance, and selected interactions such as demo actions, feature-card dragging, pricing views, scroll milestones, approximate foreground time, guide reading milestones, template links and App Store button clicks. We also record limited snapshots when a page becomes hidden, which can mean switching tabs or leaving; this is not proof of abandonment. A click is not proof of a download or purchase.

This measurement is limited to the public website. It does not collect your demo notes, typed search queries, emails, map contents, screenshots or session recordings. Private pages and local or deployment previews are excluded. URL fragments and arbitrary query parameters are removed; only a small, predefined set of campaign labels is allowed. No account ID or persistent visitor identifier is added by mappy.

Umami processes the IP address and browser information accompanying a request to derive approximate location and pseudonymous visit statistics. Raw IP addresses are not stored as analytics fields, but infrastructure and security logs may process them. Cookieless does not mean that no personal data is processed. This installation currently retains analytics records until they are deleted; you can contact me about the data practices and your rights. Website analytics is used for my legitimate interest in improving the public website, not for targeted advertising or decisions about you.

Umami is not loaded when your browser sends Global Privacy Control or Do Not Track, or when you opt out below. Your choice is saved locally in this browser only, using browser storage rather than a cookie. It does not disable the hosting and security processing described above or analytics independently provided by Apple.

Messages and support

If you email me, I process your name and email address, message headers, the contents and attachments you choose to send, and our replies. I use this information to answer you, provide support, investigate a reported problem, prevent abuse, and keep necessary support records. I do not add you to a marketing list or sell your information.

If you call or text the published telephone number, I process your telephone number and the information you choose to provide for the same enquiry and support purposes.

Email is provided through Google Workspace, which processes the mailbox on my behalf. Depending on why you contact me, the legal basis is taking steps at your request or performing the mappy contract, or my legitimate interest in replying and supporting the product. Providing this information is optional, but I cannot reply without a working contact method.

I normally delete ordinary support correspondence and retained call or text records from my active accounts and devices within 24 months after the issue is resolved. Google states that deletion from its active and backup systems may take up to 180 days after a deletion instruction. Telecommunications providers apply their own retention periods to network records. I may keep a record longer while a matter remains open, where the law requires it, or where it is reasonably necessary to establish, exercise, or defend a legal claim. You may ask me to delete it earlier, subject to those exceptions. Please do not send a map or other sensitive content unless it is necessary for your request.

Apple and App Store purchases

Apple independently processes Apple Account, payment, billing, device, purchase, download, and refund information to operate the Mac App Store. I do not receive your payment-card details or Apple Account credentials. Apple may provide me with aggregated sales, download, storefront, and refund reports. If you have opted to share diagnostics and usage information with Apple and app developers, Apple may also make privacy-protected diagnostic or crash information available to me. I do not currently access or download those diagnostic or crash reports. mappy itself does not add a third-party crash-reporting tool. If I begin using Apple-provided diagnostic reports, I will update this notice first. Apple's handling of this information is explained in App Store & Privacy.

If you choose to send me a receipt, order detail, or diagnostic report while asking for support, I handle that copy as support correspondence under the section above.

Service providers and international transfers

I disclose personal data only when needed to the providers described above: Netlify for website delivery and traffic reports, the Umami analytics installation described above, Google Workspace for email, and the relevant telecommunications providers if you call or text. Apple and a sync provider you choose process their own services under their own terms. Your telecommunications provider and mine process call or text metadata under their respective terms. I do not sell or rent personal data and do not disclose it for targeted advertising.

I may disclose information to courts, regulators, law-enforcement authorities, or professional advisers where this is necessary to comply with a legal obligation or enforceable request, or for the legitimate interest of establishing, exercising, or defending legal claims. Where the EU or UK GDPR applies, the corresponding legal bases are Article 6(1)(c) and, where relevant, Article 6(1)(f).

Netlify and Google may process information in the United States, Switzerland, the EEA, the United Kingdom, and the countries in their current subprocessor lists. Where an applicable adequacy decision or recognised data-privacy framework covers a transfer, the provider may rely on it. Otherwise, their current terms provide for approved standard contractual clauses and applicable Swiss or UK adaptations or alternatives. The data-processing agreements govern provider obligations; those adequacy mechanisms and contractual clauses are the transfer safeguards. Details and current locations are available in the Netlify DPA, Netlify subprocessor list, Google data-processing terms, and Google's subprocessor list.

Your privacy rights

Depending on where you live and subject to legal exceptions, you may ask whether I hold personal data about you and request access, correction, deletion, restriction, or a portable copy. You may object to processing based on legitimate interests. mappy does not currently rely on consent for the processing described here and does not use profiling or automated decisions with legal or similarly significant effects.

Send a request or privacy complaint to dmitrii@russu.net. I may need to verify your identity before acting on a request. Rights requests are normally answered within one month where the EU or UK GDPR applies and within 30 days under the Swiss FADP, subject to any extension the applicable law permits; if more time is needed, I will explain why. UK privacy complaints are acknowledged within 30 days and handled without undue delay. Because I never receive your maps or local app data, requests to me cannot return or erase files that remain only under your control.

You may also complain to the Swiss Federal Data Protection and Information Commissioner, your local EEA data-protection authority where applicable, or the UK Information Commissioner's Office.

Security

I use service providers with contractual and technical safeguards and limit access to support messages to what is needed for the purposes above. No internet or email service is completely secure, so avoid sending information that is not needed for support.

Changes to this notice

If mappy's data practices change, I will update this notice before the new processing starts where required and change the date above. Material changes will not be described retroactively as if they had always applied.

Contact

Questions about this notice or mappy's privacy practices can be sent to dmitrii@russu.net or to the postal address above.