StampMyShot — Privacy Policy
Updated 25 October 2026. Feature descriptions apply according to your installed app version.
Scope: the RC16 feature descriptions below apply to version 0.99.60 (16), including TestFlight use. Feature availability depends on the installed version; this notice does not announce public App Store availability.
1. Who we are and scope
StampMyShot is provided by STAMPMYSHOT LTD, registered in England and Wales, company number 17389164. Registered office: 4 Farm Road, Rowley Regis, England, B65 8ER. Contact admin@stampmyshot.com for support and privacy requests. This notice covers the app, our website and information you choose to send us. The company controls information it receives for support and website administration; it does not automatically receive the media or project data held only on your device.
2. Local-first storage
Your user-created media, audio, notes, reports, QR data, logos, templates, routes and backups are stored locally unless you choose to export, share, enable optional Cloud Sync/Teams, or store them with another provider. STAMPMYSHOT LTD does not automatically receive content held only on your device. RC16 includes optional Apple CloudKit sync and Teams, described in section 23; it has no separate StampMyShot media-upload backend or StampMyShot account system.
You can choose Apple Photos, Files, AirDrop or another app/provider as a destination. That destination may store or synchronise its copies according to your choices and system settings. Separately, requested Apple address, weather, search and map functions use online services as explained below. Local storage of your content does not mean that these online requests stay on your device.
3. Camera, selected photos and permissions
Camera access is used for photo capture and video recording. Apple’s system photo picker imports the images you select. The app requests permission to add media to Apple Photos when saving there. Editing an imported photo creates a copy and does not alter the original in Apple Photos. Saving to Apple Photos and saving locally are separate operations and may succeed or fail independently. Optional motion readings support the camera level; the current implementation does not save those readings with photos.
4. Video recording and microphone audio
Video mode may record microphone audio when microphone permission is granted. The app requests microphone access when you start a video recording, rather than merely when you open Photo mode. If access is denied, the current implementation can record video in its No Audio mode, subject to camera availability, storage and other recording conditions. It does not require microphone access for still photos.
Videos, audio tracks, retained editing sources, video tags, timing information and available recording metadata are stored locally. Saved or exported videos may contain voices and other people’s personal information. Changing a visible tag or export location option does not remove recorded speech.
5. Foreground location, GPS, speed and altitude
Location access is optional and uses the iOS foreground/When In Use permission. It supports current GPS tags, automatic addresses, current-location weather, enabled photo location metadata and video GPS/speed/altitude functions. The current app does not request background location permission. Location sampling stops when the video screen leaves the active recording state.
Available location records can include coordinates, time, accuracy, speed, altitude and course. Poor or unavailable measurements may be omitted. They are approximate device measurements, not a survey or certified measurement. Manual GPS/address text can be entered without location permission. Denying permission affects the corresponding automatic functions.
6. Video GPS routes and timeline metadata
Record GPS Route is off by default. When enabled, with location permission, the app samples the location during foreground video recording and stores the available track with the local video document. Location samples can also be needed and stored when current GPS, speed or altitude tags are enabled, even if Record GPS Route is off. Turning off that switch alone is therefore not a guarantee that a video document contains no location samples.
Samples are linked to recording time for tags, route display and available summaries. A route map uses Apple MapKit and may load map data online. Video exports can include a separate Recorded-Route.json file; use Remove Location Track to omit that structured route from the export. This does not delete the saved source document or location already visible or audible in the video.
7. Structured location versus visible content
These are different: location embedded in a photo file; GPS/address text rendered into image pixels or video frames; video route samples; and coordinates/search text used for Apple weather or map services. Save Location Metadata is off by default for new installations and controls embedding in new camera photos. Existing/imported images may already contain GPS metadata.
Removing EXIF/file location metadata does not remove visible GPS or Address Tags, location QR codes, notes, speech or route information stored separately. Disabling a permission or changing a setting does not retrospectively clean existing files, templates, backups or shared copies.
8. Apple MapKit, address lookup, search and maps
Automatic address lookup sends the selected coordinates to Apple MapKit. Place searches send the entered search text to Apple. Coordinates can come from current GPS, imported metadata or manual selection. Map and route views may request map data from Apple. These functions are not processed entirely on your device; Apple receives the network information necessary to deliver its services.
You can enter GPS/address text manually instead of requesting an online lookup. Do not include unnecessary personal information in search queries. See Apple privacy information and Apple Maps privacy information.
9. Apple WeatherKit
Weather requests send the selected place’s coordinates to Apple WeatherKit. A manually chosen weather place still uses online services. Weather attribution and artwork can also require network requests; the app provides the attribution and data-source links. StampMyShot does not receive your media through these lookups. Weather data and address/weather tags may be stored in local templates or video documents. Video address, weather and QR content is captured into the recording document; it is not a promise of continuously refreshed weather, address or QR data on every frame.
10. QR Tags, contact details and Wi-Fi credentials
QR Tags may encode user-entered URLs, social links, phone numbers, SMS or email addresses/messages, contact/vCard details, Wi-Fi network names and passwords, GPS/map locations, calendar details, reference identifiers or custom text. The app generates these codes locally and does not require access to your Contacts database merely to enter contact details.
QR fields and encoded payloads can be saved in editable local documents, settings/templates and backups where used. A rendered QR can remain readable even when its human-readable caption is hidden. Wi-Fi QR content may expose credentials to anyone who scans it; a QR code is not encryption. Share only networks and information you are authorised to disclose. A destination opened by a QR reader may contact another service, dial a number or prepare an email according to that reader’s behaviour.
11. Watermarks, custom logos and templates
Watermark text, Custom Logo Library images/names, tag content and reusable templates are stored locally. A logo may itself contain identifying or confidential information. Tags and logos can become visible parts of exported media and reports. Local templates may retain personal text, QR payloads and selected locations independently of any single library photo. Deleting a photo does not necessarily remove its templates or logo assets; manage those items separately.
12. Library, notes and reports
The local Library stores media and associated organisation/editing data. Notes and saved PDF report documents can include text, images, dates, locations and other details you add. Saved reports hold independent image copies. Deleting a library photo does not remove the image from an existing report; delete the report separately. Available video-frame/report workflows can create further image copies. An exported PDF is separate from its editable report document.
13. Backup and Restore
When you create a backup, the app packages local photos, retained sources, videos, notes, reports, templates, custom logos, settings and applicable receipts/metadata. A backup can therefore contain private tag text, QR secrets, Wi-Fi credentials and location samples. The app’s backup archive is not encrypted by StampMyShot. Save it only to a trusted destination and use suitable protection offered by your chosen device/provider.
Backup creation and sharing are user actions. Restore reads a selected archive, validates it and presents a preview/confirmation before applying a restore. It does not upload that archive to a StampMyShot server. Restored content can reintroduce older personal data. External backups are not erased when you delete app items or enable App Lock.
14. Local SHA-256 verification and receipts
Local integrity verification compares the SHA-256 digest of exact file bytes with records on the device. Receipts can include a hash, file name, local item identifier, receipt creation date, app version and original/Derived Copy classification. Review receipts before sharing: a file name or linkage to another file may itself reveal information.
A Derived Copy may have its own separate receipt. Re-encoding, changing metadata or editing a file can change its bytes and digest. A match establishes a match to the local receipt; it does not prove reality, authorship, capture time, location, authenticity or legal admissibility. No Receipt means no matching record was found, not proof of tampering. A Verification QR is a local reference, not a server-backed certificate or the final file hash embedded inside that same file.
15. Diagnostics and support exports
In Help & Feedback, Generate Diagnostic Report creates a local preview when you request it. Storage & Maintenance also prepares a local technical summary when you open that screen or run its checks. Technical operation summaries may be recorded locally during backup, restore and maintenance. Diagnostic reports are never transmitted automatically by StampMyShot. Creating an export file and choosing a recipient require your action.
The diagnostic export contains only the following categories of technical information: app/build and OS versions, device class, locale, aggregate counts and sizes, integrity/index status and operation timestamps/results. It excludes photo/video/audio content, Notes text, exact GPS coordinates, QR secrets, Wi-Fi passwords, email bodies, private Tag contents and authentication secrets. Review the preview before exporting. If you separately attach media or other files to a support email, those attachments are not protected by the diagnostics allowlist.
16. App Lock and device security
Optional App Lock uses Apple’s device-owner authentication through LocalAuthentication, which may offer Face ID, Touch ID or the device passcode. Authentication is handled by the system; the app does not receive biometric templates or your device passcode. Locking depends on your selected timeout/settings and device support.
App Lock controls access through the app interface and covers the interface when inactive. It is not separate encryption of every file, and it does not lock exported files, Apple Photos, backups or recipient copies. iOS storage protections apply; we do not promise that all files are inaccessible in every device state.
17. Export privacy and user-chosen providers
Photo export can remove structured location from the newly exported copy. Video export can omit its separate structured route file and can create a Derived Copy when re-encoding. Those controls do not erase visible tags, QR content or recorded audio, and do not clean the original or other saved copies. Review the whole file and any sidecar/receipt before sharing.
You choose whether to export/share media, folder archives, PDF reports, templates, backups, receipts or diagnostics using Files, AirDrop, Apple Photos or another app. Folder exports may contain a separate notes JSON file. Your selected service/recipient receives the chosen content under its own arrangements. Apple Photos may synchronise copies through iCloud Photos, and iOS/device backups may include app data according to your system settings. RC16 includes optional CloudKit sync and Teams (section 23); user-selected cloud storage and system backups remain possible. Browser, mail, map, attribution and other external links can make network requests.
RC16 optional CloudKit Sync and Teams are distinct from iCloud Photos, iOS/device backups and storage services you choose for export. See section 23.
18. Storage, retention and deletion
Active local content remains until you delete it, replace it through applicable restore operations or remove the app and its data. Photos/folders and videos moved to Recently Deleted have a seven-day recovery period. Expired files are cleared when the relevant library processes them; deletion is not guaranteed at an exact time while the app is closed. Saved report deletion has no Recently Deleted recovery period. Failed cleanup may need to be retried.
Templates, logos, settings, receipts, source assets and report copies may have separate storage lifecycles. Temporary editing/sharing/preview files are normally cleaned up after use, but interrupted operations may leave files until later cleanup or iOS storage management. Use Delete App rather than Offload App to remove the local container. Manage Apple Photos, exported archives, cloud copies, recipients and backups separately. We cannot remotely erase device-only data or recall shared files, and do not promise forensic erasure.
Support is handled manually by the owner of STAMPMYSHOT LTD using Gmail. We keep support messages, voluntarily supplied diagnostics and attachments only for as long as reasonably necessary to address the enquiry and any related follow-up, resolve a dispute or meet an applicable legal obligation. We assess the purpose, sensitivity and continuing need for the information and delete unnecessary company-controlled copies when they are no longer needed. We do not operate a guaranteed automatic deletion period or promise complete deletion within 30 days. Deletion requests are assessed individually under applicable data protection law. Email-provider backups, delivery/security records and information held independently by other providers may have different retention periods under their applicable terms and policies; deleting our mailbox copy does not guarantee immediate erasure of those records. Our support-retention criteria do not set a deletion date for content held only on your device or for copies you have shared with other recipients.
19. Support correspondence and website delivery
For support and privacy enquiries, contact admin@stampmyshot.com. Messages follow this route: admin@stampmyshot.com → Cloudflare Email Routing → stampmyshot@gmail.com. We receive the sender’s email address, message and attachments to respond to enquiries, investigate support issues and handle privacy requests. The app’s feedback action opens your mail service; you decide whether to send.
The receiving mailbox is a normal consumer Gmail account, not Google Workspace. Gmail is used under Google’s applicable consumer terms and privacy framework. See Google Terms of Service, Google Privacy Policy and Cloudflare Privacy Policy. Send only information necessary for your enquiry.
Support is handled manually by the owner of STAMPMYSHOT LTD using Gmail. We keep support messages, voluntarily supplied diagnostics and attachments only for as long as reasonably necessary to address the enquiry and any related follow-up, resolve a dispute or meet an applicable legal obligation. We assess the purpose, sensitivity and continuing need for the information and delete unnecessary company-controlled copies when they are no longer needed. We do not operate a guaranteed automatic deletion period or promise complete deletion within 30 days. Deletion requests are assessed individually under applicable data protection law. Email-provider backups, delivery/security records and information held independently by other providers may have different retention periods under their applicable terms and policies; deleting our mailbox copy does not guarantee immediate erasure of those records.
Diagnostic exports are separate from other attachments you choose to send; their allowlist does not remove personal information from those other files.
The website is hosted by Netlify. Cloudflare is used for DNS and Email Routing, and for normal proxied delivery/CDN on the website routes configured to use it. Website delivery and security services can process IP addresses, requested URLs, request times and browser/network information necessary to serve and protect the site. See Netlify Privacy Policy and Cloudflare Privacy Policy.
Netlify Web Analytics is not enabled. Cloudflare Web Analytics, Real User Monitoring (RUM), Bot Management, additional custom WAF configuration and custom raw log-retention configuration are not enabled. These disabled features are not used as analytics or monitoring activities for this site. This does not mean that the providers perform no normal delivery/security processing or retain no operational information. The website files contain no advertising or analytics script, contact-submission form or custom cookie/local-storage code.
20. No tracking and recipients
RC16 has no built-in analytics, tracking, advertising, Crashlytics or Sentry integration, separate StampMyShot sign-in or custom media-upload backend. Optional CloudKit/Teams processing is described in section 23. Apple online services and the support/website processing described in this notice still apply.
Recipients can include Apple for requested online/system services; your chosen sharing recipients, apps and storage services; Cloudflare for DNS, configured website delivery and Email Routing; Google for the consumer Gmail support mailbox; Netlify for website hosting; and STAMPMYSHOT LTD when you contact support. These service descriptions do not state that all providers have the same legal role or contractual terms.
STAMPMYSHOT LTD does not automatically receive your locally stored media or project data. Diagnostic reports are never transmitted automatically by StampMyShot.
21. Your rights, complaints and changes
Depending on the circumstances and lawful basis, you may have rights to access, correct, erase, restrict or port personal information, and object to processing based on legitimate interests. Where consent is relied on, it may be withdrawn without affecting earlier lawful processing. Rights have conditions and exceptions. Contact admin@stampmyshot.com; we may request proportionate identity checks and will respond within applicable statutory time limits, normally one month, explaining any lawful extension or refusal.
We cannot access information held only on your device; use the app/iOS controls to manage it. You may complain directly to the UK Information Commissioner’s Office or your applicable supervisory authority, without contacting us first. The current app does not require an account or date of birth. Material changes will receive appropriate notice; changing a notice alone is not consent to a new use.
22. Purchases and subscriptions
Apple processes in-app purchases and auto-renewable subscriptions through StoreKit. StampMyShot uses verified StoreKit transactions and entitlement information to determine access to Pro and permanent Remove Branding. The app may retain the last verified entitlement state for offline use; StoreKit remains authoritative. Payment-card details are handled by Apple and are not supplied to STAMPMYSHOT LTD by this purchase flow. If you contact support about a purchase, send only the information needed for the enquiry. See Apple Privacy Policy and Terms of Use.
23. Optional CloudKit Sync and Teams in RC16
RC16 uses the signed-in user’s private CloudKit database and, for invited Teams participants, the shared database. Sharing follows the owner’s invitations and permissions. Enabling sync does not itself send a separate copy of your media to a StampMyShot upload server. Information you choose to send to support is a separate flow described in section 19.
Cloud Sync is optional and off by default in RC16. When you enable it, supported content can be uploaded to Apple iCloud/CloudKit. This may include photos and video, retained sources and metadata, PDF report packages, projects and assignments, project notes/presets, tag/report templates and folders, and logo/signature assets. Your content may include location, recorded audio, tag text and other personal information you add.
The cloud catalog excludes Secure Folder storage. Moving content there does not erase copies previously uploaded, downloaded, exported or backed up. Backup archives are separate exports, not the Cloud Sync catalog.
Cloud operations require an available iCloud account and network connection. Downloads are presented for review before local Merge/import. Offline changes may not have reached another device; automatic resolution of every conflict is not promised.
Teams uses CloudKit sharing for selected workspace projects. Owners manage invitations, roles and participant removal. Refreshing downloaded data and applying Merge may be needed to update a local role. Revocation prevents subsequent server access; it does not recall copies already downloaded, exported or otherwise retained by participants.
Turning Sync off stops future app sync operations. It does not promise deletion of existing CloudKit records or copies on other devices. Local deletion, app deletion, disabling sync and revoking a participant are separate actions. There is no remote-wipe or instantaneous cloud deletion guarantee.
RC16 does not propagate local deletions to CloudKit and does not provide an in-app bulk cloud-data purge in this release. Do not rely on deleting a local item, moving it to Secure Folder, deleting the app or turning Sync off to erase previously uploaded content. For privacy enquiries, contact admin@stampmyshot.com; this contact route does not promise that the company can remotely access or erase your private iCloud database.
24. Paired Apple Watch companion in RC16
The companion uses a paired iPhone and Apple Watch. They exchange commands and app state through WatchConnectivity, which may include project/folder/tag choices, notes, recent-item labels and recording or measurement status. With Pro, preview frames and capture thumbnails can be sent to the Watch. Remote capture requires the reachable paired iPhone and the relevant active Stamp My Shot screen. The Watch companion is not a standalone camera.
25. Purposes and lawful bases
Where UK GDPR or EU GDPR applies to personal information processed by STAMPMYSHOT LTD, we use the following purpose-specific bases. Ordinary support correspondence and voluntarily supplied diagnostics are processed for our legitimate interests in answering users and investigating reported problems (Article 6(1)(f)). Necessary website delivery and security processing serves our legitimate interests in operating and protecting the website. These interests are balanced against users’ rights; they do not authorise advertising, tracking or unnecessary collection.
Where processing by us is objectively necessary to provide a service you request under our contract, including enabling the app features or purchase access you request, the basis is performance of that contract or requested pre-contractual steps (Article 6(1)(b)). Processing needed to comply with our statutory data protection duties, including handling applicable rights requests, uses legal obligation (Article 6(1)(c)). This is not a blanket basis for retaining all support correspondence.
System permissions and your choices control optional camera, microphone, location, cloud and sharing functions. Granting a device permission is not consent to unrelated company processing. If we rely on consent for a particular additional use, we will explain that use and obtain the required consent before it starts; you can withdraw it. Apple and other independently selected services explain their own processing and lawful bases in their privacy notices. We do not routinely request sensitive personal information in support; please avoid sending it unless necessary for your specific request.
There is no company-run automated decision-making or profiling with legal or similarly significant effects in the workflows described here. Core local use does not require you to supply support correspondence; choosing not to contact us does not prevent that use. We may be unable to resolve an enquiry without the minimum relevant information.
26. Provider locations and international processing
Apple, Netlify, Cloudflare and Google operate international services. Depending on the service, information may be processed outside the UK or European Economic Area, including in the United States. We do not promise UK-only storage or a single retention period for all provider systems. Their published notices describe their processing locations and transfer arrangements, including adequacy decisions and contractual safeguards where applicable: Apple, Netlify, Cloudflare and Google.
Our support mailbox is consumer Gmail; a Google Workspace data processing agreement must not be assumed to apply. Provider privacy notices are not a statement that STAMPMYSHOT LTD has entered every agreement mentioned in them. Contact admin@stampmyshot.com for information about the arrangements applicable to your enquiry, or to request available information about relevant safeguards. Mandatory data protection obligations and your rights continue to apply.