APP INFORMATION
ShotDyno app privacy policy
Version 2026-10-08.2 ยท Updated October 8, 2026
ShotDyno LLC provides ShotDyno for private recordkeeping and optional Community sharing. Contact shotdyno6520@gmail.com about privacy, support or access.
Your device and offline use
Your logbook, catalog entries, drafts, measurements and retained photographs are saved on your device. Local recordkeeping and bundled OCR can work without an account or internet. Anyone using your unlocked device can open the local logbook. Signing out does not erase or hide it. App settings and Terms acceptance are saved on this device.
Camera, photographs and OCR
Camera access is optional and used when you choose to photograph a package or target. You can import a supported image or enter details manually instead. Imported images are normalized into bounded pixels, removing original file metadata from the retained app image. Bundled OCR processes image text on your device. Capture does not send the image or recognized text to an OCR server. If you later connect private sync, retained catalog/target photographs and evidence can be included in your private synced logbook. Profile or Community photographs are uploaded only through their selected account/publication workflows.
Accounts and private cloud sync
Creating an account sends your email and authentication information to our Supabase authentication service. Saved sign-in tokens use the device's protected credential storage and are separate from logbook backups. Passwords entered for sign-in, recovery or deletion are sent over HTTPS for authentication; the app does not save those password fields as logbook data. After you confirm ownership and connect sync, the selected private logbook and its supported photographs are sent to Supabase for access by your own account/devices. Automatic sync can be turned off. Sync pauses during editing and when saved copies conflict; it does not publish records to Community.
Community
You choose what to publish. Published posts, comments, profile information and selected photographs are visible to eligible signed-in members. Reports and moderation cases may retain content and context for authorized reviewers. Blocking changes what you see; it does not remove another person's copy. Other people may retain material they have already viewed or copied. Keep personal or sensitive information out of public content.
You may attach one optional target photograph to a discussion or performance post. The app removes original metadata and converts it to a JPEG of at most 256 KiB and 1600 pixels on its longest side before you review and confirm it. A draft photograph stays private until publication. Removing or replacing a photograph changes the current post; authorized moderation cases may retain the exact previously reported photograph while a case is open, with scheduled deletion 30 days after it closes. Account deletion removes owned photographs and associated evidence. The in-app Replies inbox uses published comments and their existing public author information to show replies to your posts or comments; the service saves a per-account read marker when you open a reply. This feature sends no push or email alerts. Following and blocking affect which conversations are available to your account.
Service providers and current app features
Supabase processes account, private-sync and Community information needed to provide those services. Hosting and authentication providers may process connection/security information, including IP addresses. The current app contains no advertising SDK or in-app purchases. Product OCR does not perform an online barcode lookup in this version. If those features change, the policy and applicable choices must be updated before they are enabled.
Retention, recovery and deletion
Local records remain until you deliberately remove or replace them. Portable exports are private, unencrypted files you control; keep them in a protected location. Cloud records remain while your account is active unless you remove them or complete account deletion. In Account & Sync, Delete account verifies your identity and requests automatic cloud-account/data removal without waiting for approval from ShotDyno's owner. This covers private synced logbook/history/photos, owned Community post/comment/profile content and photographs, and authored report/moderation content with associated evidence. Other members' content remains. Hidden, ownerless technical placeholders may preserve references to removed content. The service can report pending while cleanup finishes; only a confirmed receipt establishes completion. A deletion receipt for checking or continuing only this request is kept in protected credential storage so you can resume an interrupted request even after sign-in is removed. The server retains a pseudonymous deletion marker, request reference, receipt hash and timestamps for status and to prevent restored provider backups from reviving deleted accounts. This marker contains no email, password or user-authored content. Temporary provider backups and connection logs have separate provider retention; they are not accessible as an active logbook. The deletion marker supports removing deleted data again before any restored provider backup returns to service. Copies on other devices, your exported files and copies retained by other people are outside that cloud deletion operation.
Deleting a cloud account keeps this device's local logbook by default. Automatic sync is stopped and the deleted account is signed out after completion. Portable backups are bound to the original account identity. Deleting that cloud account can prevent restoring those backups on a new device or with a new account, even though the existing local logbook is kept. No new account is silently assigned to your existing logbook. For help with local records or an interrupted request, contact shotdyno6520@gmail.com and share the displayed safe request reference; never email a password or verification code.
Deletion status and backup protection
A completed confirmation saved in the app records completion already confirmed on that device; completed request-status lookups are supported for 30 days after completion. Pending cleanup does not expire under this completed-status window. After that window, the service may no longer verify the saved receipt. Separate, access-restricted technical markers in an independent Supabase recovery service help prevent a deleted account from returning after a backup restore. They contain a request reference, keyed account and receipt hashes, and technical dates, with no raw account identifier, email, password, user-authored content or photographs. These recovery markers have no automatic deletion deadline; they remain protected while any retained backup or export may restore the deleted account or its data. Status expiry does not erase that backup protection. Retained recovery copies must stay out of service until ordinary account, API and photograph access is isolated, current deletion markers are checked, and deleted data is removed again before access resumes.
Your choices
Use the app offline, decline camera access, stop automatic sync, edit or remove your own Community content, export your records, or request account deletion. Review this policy under App settings or Account & Sync. Changes to material data practices will be reflected in an updated policy.