Skip to content
pointMoA

Privacy Policy

Version 1.14 · updated November 18, 2026

This is a translation of the Polish original. In case of any discrepancy between the two versions, the Polish text prevails.

1. What this document covers

  1. This Policy describes the processing of data in two places:
    • the Service — the pointmoa.eu website,
    • the Application — the pointMoA app (package identifier pl.fatpirat.pointmoa), distributed through Google Play on Android and the App Store on iPhone and iPad.
  2. Sections 3–4 concern the Service only, section 5 the Application only, and the remaining sections both.
  3. This document is also the privacy policy referenced in the Application's Google Play and App Store listings.

2. Data controller

  1. The controller of personal data is Eryk Kozłowski, a natural person operating the pointmoa.eu website and publishing the Application, under the designation pointMoA.
  2. Contact for data protection matters: kontakt@pointmoa.eu.
  3. No data protection officer has been appointed — the conditions of Article 37 GDPR do not apply.
  4. Neither the Service nor the Application provides user accounts. There is therefore no account deletion procedure and no separate address for such requests; deletion of Application data is described in §5.7.

3. The pointmoa.eu website

The Service is designed to collect as little data as possible. Using it requires no account and no name, surname or e-mail address.

3.1. Correspondence

Scopee-mail address and message content
Purposereplying to the message
Legal basisArticle 6(1)(f) GDPR — legitimate interest in conducting correspondence
Retentionuntil the matter is concluded, then 14 days at most

Correspondence is kept solely in the Google Workspace mailbox and only for as long as the matter lasts. Once it is concluded the message is deleted — within 14 days at the latest. A deleted message then sits in the mail provider's bin for 30 days, after which the provider erases it on its own. The Controller keeps no correspondence archive of its own and no copy outside the mailbox.

3.2. Server logs

ScopeIP address, date and time of request, page address, browser type
Purposeoperating and securing the Service, diagnosing errors
Legal basisArticle 6(1)(f) GDPR — legitimate interest in maintaining and securing the Service
Retentionat the hosting provider, in accordance with its own terms

Logs are created and kept solely by the hosting provider. The Controller keeps no log archive of its own, does not download them and cannot extend their retention period.

3.3. Visit statistics — Vercel Web Analytics

The Service uses Vercel Web Analytics to measure visits and page views, identify popular pages and improve the Service. The provider is Vercel Inc.

Scopepage views and event time, page address and path, referrer, filtered URL query parameters, approximate location (country, region, city), device type, operating system and browser with their versions
Purposeaggregate statistics about use of the Service and improvements to its content
Legal basisto the extent personal data is processed: Article 6(1)(f) GDPR — legitimate interest in measuring use of the Service while limiting the scope of data
Retentionsession identification is discarded after 24 hours; aggregate statistics remain available for the retention period applicable to the Vercel plan in use

The tool does not use cookies. Vercel distinguishes visits using a hash derived from the incoming request. It does not serve to track the same person across different websites. The 24-hour period concerns session identification, not deletion of all statistics.

The Controller receives aggregate statistics. They are not used for advertising, marketing profiling or linking activity across websites. Page views are recorded; the Service sends no custom events containing data entered into the Calculator, Targets or Shooting Licence module. Analytics concerns the website only, not the Application (§5).

Further processing details are set out in the Vercel Web Analytics privacy documentation.

3.4. Data we do not collect

The Service does not carry out marketing profiling or automated decision-making, does not use advertising tools or cross-site tracking, does not create user accounts and does not share data for marketing purposes.

4. Cookies and browser local storage in the Service

The full list — the name of every record, its content, lifetime and how to delete it — is set out in the separate Cookie Policy. What follows is the summary.

  1. The Service stores one cookie, of a strictly necessary kind: it keeps the language chosen by the User while they move between pages. The cookie is a session cookie — it disappears when the browser is closed and does not carry the choice over to the next visit.

  2. The Service additionally keeps in the browser's local storage (localStorage), not in cookies, what the User enters into the Service's tools: the data typed into the Calculator and the Targets (firearm, optic, ammunition and weather parameters), the column settings of the results table, and the learning progress and mock-exam state in the Shooting Licence module. The sole purpose is to let these entries survive a page refresh and navigation between pages. Nothing is sent to a server — the Calculator runs in the User's browser, and the Service has no backend that could receive this data.

  3. The strictly necessary cookie and the local storage described in point 2 do not require consent — they are essential to provide a service explicitly requested by the User.

  4. The Service uses no analytics, advertising or third-party cookies. Vercel Web Analytics (§3.3) measures visits without cookies or cross-site tracking. In this configuration the Service displays an information bar, without an “Accept/Reject” dialog. Closing it acknowledges the information; it is not consent and does not control analytics. A change to measurement or the addition of other tools requires reassessment and, where consent is required, obtaining it before those tools are enabled. See §6 of the Cookie Policy.

  5. Cookies and local storage can be deleted or blocked in browser settings (site data). Blocking them does not prevent use of the Service — the User merely loses the remembered entries.

  6. The Application uses neither cookies nor advertising identifiers.

5. The pointMoA Application

5.1. Local log data and separate Store connections

  1. Calculations and log data are processed on the device. The Application has no pointMoA accounts, sign-in or Controller server receiving log entries, photographs, firearm profiles or training results.
  2. The Application has no advertising, advertising identifiers, proprietary analytics or telemetry. This does not mean that there are no third-party connections: Google handles distribution and purchases on Android; Apple does so on iOS/iPadOS (§5.8–5.9). System backups are described in §5.5.
  3. The purchase description applies to Android from 2.530.0 and iOS/iPadOS from 2.531.0, and earlier test packages with the model enabled. An older package with purchases disabled does not start using them merely because this Policy changes.
  4. The Android Application has the INTERNET permission. On both platforms, calculations, local storage, image analysis and laser training do not themselves require a network. Loading prices, purchasing and refreshing Store entitlement require one. To confirm time, the Application also sends an HTTPS HEAD request: to the fixed Google Play page for the Application on Android, or to www.apple.com/library/test/success.html on iOS/iPadOS. On iOS/iPadOS and in earlier Android versions this happens after losing trusted-time continuity; on Android from 2.546.0, after a successful Store connection if time has not yet been confirmed over the network. The Application reads time from the response with a random cache-busting parameter. It includes no account, purchase token, log or photographs. The respective provider receives ordinary connection data, including IP, request URL and the random parameter; the Google URL also includes the Application identifier. The iOS request uses no cookies. The local time anchor is excluded from the log backup and system backup on both platforms.
  5. Offline time on Android from 2.546.0. With automatic date and time enabled in the system, the Application can create a time anchor from the phone's clock alone, without a network connection, including after the phone restarts. For this it reads the automatic-date setting, the time since the phone started and the system boot counter. The anchor contains the time, the time since start-up, the boot number and whether time was confirmed through HTTPS. It stays on the device and is not sent anywhere. A manually set date or time inconsistent with the saved boundary — and, on iOS/iPadOS and in earlier Android versions, also unconfirmed time — can suspend time-limited Pro and new actions subject to period allowances.
  6. Manufacturer, range-map, document and Store links open the browser or application selected by the system at the User's request. That service's rules then apply. §5.10 describes voluntary Google Play reviews on Android.

5.2. Data created by the User and kept on the device

The Application stores what the User enters into it. The data sits inside the app's private directory: the User's records in an IndexedDB database, and the user name and minor interface settings in the local storage of the web engine. The Application does not send these records to a Controller server. Android and iOS/iPadOS system backups (§5.5) and export or sharing requested by the User (§5.6) are separate mechanisms.

Armouryfirearm, optic and ammunition profiles, individual firearms and air guns (including round count and its corrections, assigned profile, modifications, and purchase date and price), firearm photographs (at most six per firearm, with captions) and the remembered firearm report layout, a service log (date, kind of work, replaced part, note, cost), ammunition products and lots, ammunition purchases including prices, the current zero and the reminder thresholds for checking it; in Calculator profiles also the provenance of a muzzle velocity or ballistic coefficient trued at the range (date, distance and group-centre position), measured muzzle velocity–powder temperature pairs, a custom bullet drag curve and the click value measured with the tall-target test (date, distance, number of clicks and shift)
Shooting logdate, start and end time, range (selected or entered name and town), training type, round count, malfunctions and notes; planned sessions with preparation lists, and saved series and targets
Competitionsname, dates, ammunition preparation and consumption, results and placings, notes
Zeroingzeroing configuration (firearm or one-off set-up, optic and mount, click value, ammunition and lot, distances, conditions), shot series with accepted hits, recommended and applied clicks, result and zeroing history, checklist
Dry-fire trainingstandalone laser-training sessions: training or drill type, target and distance, position and time of each laser spot, results, scores and times, plus camera data needed to assess the measurement (system-reported lens name, sensitivity, exposure and zoom ranges, camera activity log and frame calibration)
Rangesrange cards entered by the User: name, club, locality, address, directions, map link, phone number, opening hours, distances and lanes, prices, restrictions, pros and cons, rating, description, notes and one photograph; club membership with the date the fee is paid until — no membership number
Goalslive-fire and dry-fire goals (measure, target value, deadline). Records, insights and statistics are not stored — the Application computes them on the fly from the other data
Targetsscores, groups and hit analyses, target photographs (including those from Zeroing), photographs from range visits and competitions, how the target was aimed (scope at zero, dialled correction or holdover with its value)
User namean optional name (40 characters at most) entered in Settings and shown in the greeting on the Start screen; empty by default
Interface settingschosen language, theme (dark, light or system), units, first-run state, whether the feature tour and the "First steps" list have been seen, viewed hints, unsaved Calculator form draft, the Calculator's advanced mode settings (cant, wind direction, wind zones, shot azimuth, uncertainties and — if the User enters it — the geographic latitude for the Coriolis correction), the energy threshold in the results table, "Shooting" screen settings (distance step, night mode) and its target list (name, distance, angle), the zero error of the phone's orientation sensor from the calibration in "Measure with phone", selected target overlays, remembered report graphic layout, dry-fire settings (sound signal, chosen lens, view), the date of the last backup and of a postponed backup reminder, whether the "Next visit" line is expanded, names and localities of deleted range cards (so that they do not return when cards are created from history)
Free working pool and reviewsIn versions with the model enabled: identifiers of available and known records, a sequence of successful card use and a Free pool. On the Pro-to-Free transition, journals select the latest entered session dates, with creation time breaking ties; other cards follow use. Import preserves the established pool. Pool state is included in backups and merges with local state; it is not sent to Google, Apple or the Controller. Review-prompt dates are described in §5.10 and are separate from the log backup.
Version counterslocal counters (§5.9): first launch of the version introducing this record and whether data already existed, live-fire session, dry-fire training and competition counts per period and the quick-target day marker; versions with the model enabled also record the introductory period and advanced-calculation use. From Android 2.546.0 the introductory-period record has a length of 14 or 30 days and an installation welcome-rules marker; the length is decided locally by comparing the system dates of the Application's first installation and last update, which the Application does not store. Counters are in the database and backups; the Store entitlement cache stays separate and is not part of the log export
Where it livesin device memory, in the app directory; system backups and exported files are described in §5.5–5.6
Who can read itthe User and recipients of a backup or shared file chosen by the User. The Controller does not automatically retrieve these records

Data from earlier versions: the database and backup file may still contain previously saved drill queues (version, level, firearm and configuration), live-fire drill and check results (times, scores, hits, penalties, conditions, a snapshot of the rules and target links), training sheets, and run and step identifiers from earlier dry-fire plans. Records of how those runs were counted are also retained. Version 2.525.0 withdrew creation and execution of these plans and the new results screens; it did not delete historical data from the database or backups. Earlier planned sessions with preparation lists and standalone laser training remain available.

Log, competition, Zeroing and dry-fire entries, range cards and the latitude in advanced mode can indirectly reveal where and when the User was present (range name and address, locality, club membership, date and time). The User enters them, they are entirely optional, and the Application works without them.

The Controller has no access to these records and does not receive them through the Service. The User manages them on the device and decides whether to export or share them (§5.6). Contact data and any order handling by the Controller are described separately in §3.1 and §5.9.

5.3. Camera, photographs, sensors and files

  1. Target photographs — in the Shooting log, Competitions, Quick targets and Zeroing — are taken through the system camera, the system photo picker or — in the mode described in point 3 — through a camera preview inside the Application. Photographs of firearms, ranges, range visits and competitions are chosen by the User in the system picker. The system camera hands the Application only the photograph taken with it, and the system picker only the image the User selected.

  2. Android: the Application declares camera permission (CAMERA) for the preview and dry-fire training. Android requires the same permission before opening the system camera. Without it, an image can be chosen in the picker. The Android edition declares no gallery permissions and does not browse the photo collection. iOS/iPadOS: the system may request camera and Photos access when selecting an image or saving a report to the "pointMoA" album. Saving to the album requires finding or creating that album in Photos. The User controls the permission scope, including limited access, and revocation in system settings. The Application does not upload the library to the Controller. If saving to the album fails, it offers the system share sheet.

  3. The "Photo with assist" mode shows a camera preview and suggests how to improve the framing before the photograph is taken. On first use the system or the browser asks for camera consent; consent can be withdrawn at any time in the settings — a photograph can then be chosen in the system picker (point 1). The preview image is analysed solely on the device, in memory — preview frames are never stored, sent anywhere or used for anything beyond the on-screen hints, and the preview ends the moment this screen is closed. The only thing stored permanently is the photograph the User takes; it goes where all other target photographs go (§5.2) and carries no EXIF metadata.

  4. Dry-fire training turns on the camera preview only after the User confirms the safety rules with the "Confirm and turn the camera on" button. Frames are processed solely on the device, in memory: the Application crops the area of the printed target and looks for the laser spot in it. It neither stores nor sends the frames — the session receives numbers: the position and time of shots, results, and the camera and calibration technical data listed in §5.2. The preview ends the moment the training screen is closed.

  5. The Application plays the dry-fire signals and commands: the phone generates the sound, and voice commands are read by the system speech synthesiser. The microphone is not used — the Application records no sound and has no permission that would allow it. The camera is not used for recording or recognising people, and the Application never starts it in the background.

  6. A photograph taken this way is not saved to the device gallery; it goes only into the app's database. Saving a finished report graphic to the "pointMoA" album is started only by the User (§5.6(2)).

  7. The Application reads technical EXIF metadata from the file that is needed for measurement: focal length, frame orientation, declared image dimensions, exposure time, ISO sensitivity, camera designation and the capture date. This metadata is used only in memory, at the moment the photograph is attached, for calibration. It is not stored — only the calibration result reaches the database, expressed as fractions of the image dimensions.

  8. The Application reads no geographic coordinates from metadata — it contains no code capable of recognising them.

  9. Before being stored, every photograph — of a target, a firearm, a range, a visit or a competition — is downscaled to at most 1600 pixels on its longer edge and re-encoded as JPEG. The re-encoding runs through a canvas, which removes all EXIF metadata, including any geographic coordinates recorded by the camera. What reaches the database is an image stripped of metadata.

  10. The Application does not use device location — it reads neither GPS nor Wi-Fi nor cell towers. The User types in the geographic latitude for the Coriolis correction (§5.2) by hand. Nor does the Application access contacts, the list of installed apps, the microphone or device identifiers.

  11. Motion sensors and compass. The "Measure with phone" button in the Calculator reads the phone's attitude — the shooting angle and the cant of the firearm, and on the "Shooting" screen the target angle — or the phone's direction relative to magnetic north, that is the shot azimuth. The readings are processed in memory only and only while the measurement window is open; what reaches the form is the result alone, once the User accepts it with a button. The only thing stored permanently is the sensor zero error from calibration (§5.2) — a property of the phone, not of a place. Android requires no permission for this; iOS may request motion and orientation access. The compass shows a direction, not a position — the Application still does not determine where the device is (point 10).

  12. Files chosen by the User. A backup file to restore, a chronograph CSV file and a drag-curve file are chosen by the User in the system file picker, and the Application reads them on the device. From a chronograph shot series it stores only what the User carries over into the form or a profile (e.g. the average velocity and velocity–powder temperature pairs); it does not store the series itself.

  13. Diagnostic data from earlier test APKs. Earlier test versions installed from a file allowed a local detection correction queue to be enabled in Settings. It recorded approval, rejection or addition of a shot hole, its coordinates, scan parameters, Application version and a small image patch used by the former classifier (32 × 32 pixels, not the whole photograph). From version 2.546.0 the queue is no longer in Settings and the Application creates no such records. Records created earlier remain in the database and in the backup file (§5.6(5)); Settings → Clear data removes them (§5.7). Nothing was or is uploaded automatically. The feature was not available in Google Play or App Store installations.

5.4. Shot and laser spot detection

Shot-hole detection on a target photograph, the calibration and rectification of the photograph (including recognition of the pointMoA target markers in Zeroing and in dry-fire training) and laser spot detection run entirely on the device — on a bundled model and the Application's own code. From version 2.546.0 shot holes are detected by a bundled neural-network model through the ONNX Runtime library shipped with the Application — on Android, iPhone and iPad. The model and the library are part of the Application package and are not downloaded from the network. The image passed to the model is processed in memory and no separate file is created from it. Neither the photograph nor the camera image is sent anywhere for this purpose. The Application does not train a model on the device and collects no samples to improve it. Diagnostic data from earlier test APKs is described in §5.3(13).

5.5. Google backup and Apple device backups

The device system can copy Application data off the device under the User's backup settings, without a separate export from pointMoA.

  1. Android: the Application enables system backup (allowBackup). The database (profiles, log, zeroing, targets, dry-fire training, ranges, goals and photographs), settings and user name may enter a backup linked to the Google account and be restored after changing phones. Android and Google services create it under Google's privacy policy. The backup is encrypted; on devices with a screen lock, encryption also uses protection associated with that lock.
  2. iPhone and iPad: Application data may be included in an iCloud system backup or a device backup on a computer, depending on the User's settings and system rules. These are Apple mechanisms, not a pointMoA cloud. See Apple — what iCloud backs up. The Application does not continuously sync the log through iCloud. The local trusted-time record is excluded from backups (§5.1).
  3. The Controller has no access to the User's system backups. Their creation, scope, available space and restoration depend on the system and selected service. A backup may not cover all the data; the primary way to make your own copy is the export described in §5.6.
  4. Google backups are managed in Android backup / Google One settings; iCloud backups in Apple Account and iCloud storage settings. Turning off future backups does not mean that existing ones are deleted. Computer backups are removed separately in the tool that created them.
  5. An image the User exports to the gallery, Photos or Files (§5.6) may later sync through a selected service, such as iCloud Photos or Google photo backup. That service's settings control this, not pointMoA.

5.6. Export, reports, graphics and sharing

  1. The Application can save data to a file: a backup (JSON), reports and printouts (PDF), a graphic for social media from a session, a competition or a season or year summary, and a firearm report from a firearm card (a PNG image, or JPEG when it contains a photograph), and — from the target scan screen — a scan diagnostics file (JSON: shot-detection data and the versions of the Application, browser and system, with no photograph). The Calculator also shows a profile code — a text and a QR code that the User can copy to the clipboard (point 8). Every save is started by the User only.
  2. Backups, PDF printouts and diagnostics go to the system share sheet, where the User chooses the destination (cloud drive, e-mail, messenger, social network, cable). A graphic can be handed over the same way or saved with the "Save image" button in the "pointMoA" album in the phone's storage — it then appears in the device gallery; if saving fails, the file goes to the share sheet. Before being handed over, the file is created in the Application's cache (§5.7).
  3. From the moment a destination is chosen, the data is governed by the privacy policy of the service the User selected. The Controller has no influence over this.
  4. A social media graphic contains only what the User ticks in its composer: a photograph or drawing of the target, results and charts, firearm, ammunition and optic, a custom title and — switchable off with separate toggles — the date and the location. A season or year summary graphic contains only figures from the period (visits, rounds, grouping, records, competitions, firearm, ammunition, weekly streak, goals and the number of ranges); a range name goes in only when the User adds that element. A firearm report contains a photograph of the firearm and the modifications and firearm data the User selects (e.g. calibre, barrel, optic, round count). The user name from Settings is placed on none of these graphics. The Application publishes nothing by itself and signs in to no social network — it hands the finished file over solely by the route described in point 2.
  5. The backup file contains all data from the database, photographs included, and is not encrypted. It is worth treating like any document holding personal data. It does not contain the settings kept in local storage (§5.2), including the user name and the latitude.
  6. Printouts (PDF) carry no user name. The Zeroing sheet shows the selected set-up in its header (firearm, calibre, optic, ammunition and zero). Among the printouts, a QR code appears only on the dry-fire aim-ring target and holds only the sheet geometry and a random copy identifier.
  7. The Application does not sync the log with Google Drive or iCloud Drive. Saving a file to a chosen service through the system sheet does not create a pointMoA account. The Store account separately handles purchases (§5.9).
  8. The profile code contains only the Calculator form data: firearm and optic names, ammunition, ballistic data, zero, shooting conditions and — if present — the dates and results of range truing and of the tall-target test. It contains no user name, photographs or log entries. The code is created only at the User's request and is shown on the screen; the "Copy code" button puts it on the system clipboard, from which the User pastes it. A second phone reads the QR code with its own camera as text. Loading a code fills in the form — a profile in the database is created only when the User saves it.

5.7. How to delete Application data

  1. Individual entries are deleted in the Application, in their module.
  2. All data from within the Application: Settings → Clear data; requires typing a confirmation word. This clears the database, including photographs, dry-fire training, ranges, goals, drafts, profiles and counters, plus settings and user name; only the chosen language remains. It does not remove cached files, exports, images in the gallery or Photos, or system permissions. Permissions are managed in device settings.
  3. Android: System Settings → Apps → pointMoA → Storage → Clear data also removes the cache. Uninstalling removes the private Application directory. Copies of images outside it must be checked and, if needed, deleted separately in the gallery or Files.
  4. iPhone and iPad: use Delete App to remove its private data and cache. Offload App retains documents and data for reinstallation. Images saved in system Photos, including the "pointMoA" album, remain separate and are deleted in Photos. Clearing the Application's database does not delete them.
  5. Deleting data or the Application does not delete Google or iCloud backups, computer device backups, or previously exported or shared files. These are deleted separately with the relevant provider (§5.5). It does not cancel subscriptions either; use the relevant Store's settings.
  6. Deletion cannot be undone in the Application. Recovery requires an accessible, valid file or system backup that contains the data and can be restored. Without such a backup the loss is irreversible; the Controller keeps no copy of the log. Restoring a purchase recovers Pro entitlement, not deleted records.

5.8. Google Play and the App Store as distributors

  1. Downloading, installing and updating use Google Play on Android or the App Store on iOS/iPadOS. Google and Apple process the resulting data as separate controllers, under their own rules: Google and App Store & Privacy.
  2. System and Store services may process diagnostic data, including crash reports, depending on device settings and provider rules. The Controller receives the installation, usage and stability statistics made available in the Store consoles. The Application adds no proprietary analytics tool or automatic log upload.
  3. The Application contains no advertising and never will. In-app purchases are described in §5.9. TestFlight separately distributes Apple beta versions; feedback and screenshots voluntarily sent by a tester may reach the developer through Apple tools. The tester chooses to send such materials; this is not an automatic upload of log records.

5.9. Purchasing Pro

Version scope: Android from 2.530.0, iOS/iPadOS from 2.531.0 and earlier test packages with the model enabled. Points 1–4 describe Google Play, points 7–10 describe Apple, and counter rules are shared. On Android, Google Play Billing 9.1.0 handles Pro purchases and Google In-App Review 2.0.2 handles optional reviews (§5.10). Version 2.530.0 activates the public model; update availability depends on publication in the relevant Store. Earlier packages with the integration disabled do not start using it merely because this document changes. The following describes data flows when using these features.

  1. Purchases are handled through Google Play, under the Store's terms and the seller information shown before purchase. Google's service processes payment details under its own privacy policy.

  2. The Controller receives neither card numbers nor payment authentication details. Play Console does, however, provide management of individual orders, rather than aggregate reports alone: identifier, product, date, amount, currency and order state, together with information made available by Google to find and handle the order and refunds. Orders can also be searched for by the buyer's e-mail address. We do not treat this information as anonymous.

  3. The Google Play connection loads products, offers and prices, handles purchases, acknowledges delivery, and checks and restores entitlements. The code passes the Application identifier, product identifiers and offer or purchase tokens needed for those operations. It does not include log entries, photographs, firearm profiles or training results in these requests to Google or a Controller server. Google's libraries, including their diagnostics, require a separate assessment before release; their operation is not described as a single purchase-status query. From version 2.546.0 a new installation with 14 days of introductory Pro also loads, from its first day, the first-subscription offer with a free trial period. Google Play decides on the basis of its own data whether the account is eligible; the Application receives only the offer or its absence and passes no local counters or installation data to Google.

  4. The purchase entitlement is tied to the Google account on the Store's side. Restoring a purchase on the same account restores Pro, not the log; User Data is transferred through a backup (§5.6). The entitlement cache stores the signed purchase record, its signature and the last-check time locally, to recognise access offline as well. It is not part of the log backup file. Android system backup is a separate mechanism (§5.5); absence from the export does not prove exclusion from the system backup.

  5. Limit and introductory-period counters run on the device. Current records are described in §5.2. They go into backups and are merged with the device's state, rather than resetting use when an older backup is imported. They are not sent to Google, Apple or the Controller.

  6. A purchase creates no pointMoA account. The Controller still receives no log data. Order information in point 2 may, however, be processed to handle purchases, complaints and refunds and to fulfil accounting obligations, under Article 6(1)(b) and, to the extent required by law, Article 6(1)(c) GDPR. It remains in Google's tools under their retention rules; where it constitutes legally required documentation, it is retained for the period required for that documentation. Correspondence is described in §3.1.

  7. iOS/iPadOS from 2.531.0 — Apple StoreKit 2: the App Store handles products, prices, purchases, renewals and restoration. Entitlement is tied to the Apple Account used for the purchase. The Application reads StoreKit-verified transactions and product, expiry, renewal, plan-change and revocation information. It sends no log, photographs, firearm data, training results or local counters in these requests. On iOS/iPadOS all installations still receive 30 days of introductory Pro and no trial offer. Reading the Application's original App Store version (AppTransaction), prepared for recognising new installations, is not used; we will update this Policy before enabling it.

  8. Apple processes account and payment data under its own rules. The Controller receives no card number, Apple Account password or payment authentication details. Apple provides developers with purchase and refund information and sales and subscription reports, including product, dates, amounts, currencies, country or region and transaction or subscriber identifiers. Reports containing identifiers are not automatically treated as anonymous. See App Store & Privacy.

  9. StoreKit is the source of Apple entitlement, not a Pro field in a log backup. The Application does not put its own copy of Apple transaction history into that backup or send it to a pointMoA server. Restoring purchases may prompt system confirmation of the Apple Account; it does not transfer log records. The local trusted-time file described in §5.1 is separate from Store data.

  10. The local-counter rules and purposes of order handling in points 5–6 also apply to Apple. Data made available to the Controller serves purchase, complaint and refund handling and accounting obligations under Article 6(1)(b), and where legally required Article 6(1)(c), GDPR. It remains in Apple's tools under their retention rules; legally required documentation is retained for the applicable statutory period. A purchase creates neither a pointMoA account nor a shared Google and Apple purchase account.

5.10. Voluntary Google Play review — Android from 2.530.0

  1. After at least 7 full days and 3 different days of use, the Application may request a review after a successful action on returning to Start. Its own cooldown is at least 90 days. There is no satisfaction screening or selection based on an expected rating. Introductory free Pro (14 or 30 days) and the Store trial period are independent of reviews and their content; reviewing earns no reward.
  2. Locally stored values are the observation start, last launch, up to three days of use and the last attempt date. They limit frequency, are not sent to the Controller, are not purchase history and are excluded from the log export. Clearing Application data removes them.
  3. Google In-App Review manages the system card. Google decides whether to display it; completion proves neither display nor submission. The Application receives no stars, text or review-submission result. A manual Settings link opens the Google Play page.
  4. If the User submits a review, Google processes the rating and optional text under Google Play's rules. Public reviews, or private developer feedback in the appropriate test track, are visible in Google's tools; the Controller can read them there. Management and deletion are through the Google account. We promise neither anonymity nor that published reviews will not be read. See In-App Review data documentation and Google's Privacy Policy.

6. Recipients of data

  1. Vercel Inc. (Service) — provider of hosting and Vercel Web Analytics, processing data within the scopes described in §3.2–3.3.
  2. E-mail provider — handling correspondence sent to the contact address, under a data processing agreement concluded with that provider. Correspondence is stored in Google Workspace.
  3. Google — as distributor of the Application (§5.8), purchase-handling provider (§5.9) and provider of Android's system backup (§5.5), in each case on its own terms.
  4. Apple — distributor and purchase provider on iOS/iPadOS (§5.8–5.9) and iCloud backup provider (§5.5), under its own rules.
  5. Data described in §5.2 is not automatically sent to the Controller. It may leave the device through Google or Apple system backup (§5.5) or export and sharing requested by the User (§5.6); recipients then depend on the selected service or addressee.
  6. Data may be transferred to third countries (outside the European Economic Area) in connection with the use of international providers' infrastructure. Such transfers take place on the basis of mechanisms provided for in Chapter V GDPR, in particular standard contractual clauses or an adequacy decision.

7. Rights of data subjects

In relation to data actually processed by the Controller — that is, the data in sections 3–4 and the order information described in §5.9(2) and (8) — Users have the right to:

  • access their data and obtain a copy (Article 15 GDPR),
  • rectify their data (Article 16 GDPR),
  • erase their data (Article 17 GDPR),
  • restrict processing (Article 18 GDPR),
  • data portability (Article 20 GDPR),
  • object to processing based on legitimate interest (Article 21 GDPR),
  • lodge a complaint with the President of the Personal Data Protection Office, ul. Stanisława Moniuszki 1A, 00-014 Warsaw, Poland (current UODO contact details).

To exercise these rights: kontakt@pointmoa.eu.

In relation to the data in §5.2, Users exercise these rights directly and themselves: viewing and correcting in the Application, portability through export to a file (§5.6), erasure as described in §5.7. The Controller has no access to this data and therefore cannot perform these actions on the User's behalf.

8. Voluntary nature of providing data

Providing data is entirely voluntary. Not providing an e-mail address only makes it impossible to reply to a message. Data entered into the Application is voluntary in full — the Application works even if the User fills in nothing beyond the calculation fields.

9. Security

  1. The Service is delivered exclusively over an encrypted connection (HTTPS).
  2. Application data is protected by the Android or iOS/iPadOS sandbox: the app directory is not accessible to other applications, nor to the device user without elevated privileges. On devices with a screen lock enabled, storage is additionally encrypted by the system.
  3. The Application adds no encryption or password of its own to the database. Whoever has access to an unlocked phone has access to the log. A screen lock is recommended.
  4. In relation to the data the Controller actually holds (sections 3–4), the technical and organisational measures applied are appropriate to the risk within the meaning of Article 32 GDPR, in particular: minimisation — the Service operates no accounts or forms and collects only what is described in §3; restriction of access to a single person; two-factor authentication on administrative accounts (hosting, domain, e-mail, Google Play Console, App Store Connect); encryption in transit; a data processing agreement concluded with the e-mail provider; and deletion of data within the periods set out in §3.

10. Children's data

Neither the Service nor the Application is directed at children. Google Play or the App Store states the age restriction for the relevant release. The Application participates in neither Google's "Designed for Families" programme nor Apple's Kids Category. The Controller does not knowingly collect data of persons under 16. Local log data and separate purchase and distribution processing are described in §5; the absence of a log server does not mean that Store services process no data.

11. Changes to this Policy

This Policy may change, in particular in connection with the release of new Modules, the development of the Application, or changes in law. Amended text is published in the Service together with the date of update and the version. Any change to the scope of data processed by the Application is introduced together with an update of the relevant Store privacy information: "Data safety" in Google Play or "App Privacy" in App Store Connect.


This Policy was drawn up in Polish. In the event of any discrepancy between language versions, the Polish version prevails.