Prototype note

This is a developing support tool. It can help someone keep a plan, journal, resources, and calming tools close by, but it does not monitor someone or replace professional judgement, safeguarding processes, or urgent local support.

What is stored

Your plan, suggestions, contacts, journal entries and drafts, worksheets, message templates, home pins, and attached pin media may be saved in this browser. The browser may also hold cached app files.

Settings such as an optional access PIN, discreet mode, appearance, night check-in dismissal, saved resources, skill notes, feedback, and temporary collaboration or launch details may also be stored on this device.

The optional access PIN is a screen lock for this app on this browser. It is not encryption and does not make the stored plan unreadable to someone who can inspect the device or browser data.

Ordinary plans stay in this browser. Only confirming Collaborate uploads a temporary copy of the current plan, including its contact details, attached photos and voice notes, to Supabase. Journal entries, toolbar pins, worksheets and device settings are not part of that copy. If shared editing is unavailable, no sharing link is created.

Anyone with the sharing QR or link can read and edit that plan. Both devices receive changes while the link is active. Access ends after 24 hours; expired active copies are scheduled for deletion within a minute. Provider backups follow the provider's retention policy. This is temporary collaboration, not a permanent cloud backup. A stopped link retains only its random ID and hashed access keys until its original expiry, so a delayed request cannot reopen it.

To limit abuse of shared editing, an unreadable, keyed hash of the network address is kept separately for up to an hour (plus the next scheduled cleanup). It is not put in your plan, and no name or device identifier is added to this rate-limit record.

The feedback page saves a copy in this browser. When cloud feedback storage is available, choosing Send feedback also sends the form to Supabase. Optional contact details are included only when you consent to contact. The stored feedback record does not include a browser user-agent or device identifier. The hosting service may process ordinary connection data such as an IP address and user-agent, and an IP-derived value is used briefly to limit repeated submissions; it is not added to the feedback record.

Phone loss and transfer

Anything saved only on this device may be lost if the phone is lost, reset, or the browser data is cleared. Cloud restore is still being refined while testing continues.

Cookies and similar storage

This app uses browser storage, IndexedDB, Cache Storage, and one appearance cookie to provide its features. It does not use advertising cookies or tracking cookies.

If analytics or marketing tools are added later, consent should be requested before they run.

Your controls

This removes Tap My Safety Plan data from this browser, including the current and legacy plans, contacts, journal content and drafts, pins and their media, worksheets, message templates, skill records, settings, temporary session data, and Tap app caches. It does not delete browser history, downloaded or printed copies, messages or location already shared, a cloud plan, or feedback already submitted to cloud storage. To ask about submitted feedback, contact info@tapmysafetyplanapp.com.

Cloud records

Choose Stop sharing on the device that created the QR to revoke access and delete its active cloud copy immediately. Do this before deleting device data if you want to end an active share: clearing browser data removes your temporary sharing credentials, but does not revoke the cloud link. Copies someone already saved, downloaded, printed or photographed cannot be recalled.

Older cloud records from the earlier sharing prototype cannot be safely identified from a predictable plan identifier. The service operator must use an authenticated administrative process to review those records; this browser cannot prove who owns a cloud plan from that older prototype.

An earlier sign-in prototype may also have created passkey credential or challenge records. The current public app no longer exposes that sign-in flow and cannot safely identify or delete those records. An authorised service operator should review and remove them in the cloud administration system when appropriate.