Privacy
Privacy policy preparation.
Final privacy wording must match the actual public deployment: hosting provider, server logs, map providers, account workflows, API traffic, contact channels, and analytics or monitoring if used.
Maps and E-Codes Disclaimer acceptance
We use a session cookie to recognize your guest acceptance across Maps and E-Codes. Guest permission expires after 30 minutes of inactivity or 12 hours after confirmation, whichever comes first. We record the accepted Disclaimer and dialog versions and text, confirmation time, language and service used.
When you accept while signed in, we associate the record with your personal user account. If you create a new account during a valid guest session, we save your earlier acceptance to that account and notify you after registration. This is separate from any marketing or optional-cookie consent.
Acceptance records do not add IP addresses, device fingerprints or location data. Account-linked records are deleted with the user account. Guest permission expiry does not itself delete the stored confirmation record. The final privacy policy must specify evidence-retention periods before public launch.
Data surfaces
Public launch wording should cover page visits, API requests, generated SRLs, saved account state, map interactions, contact requests, and operational logs.
Third parties
Any map tiles, hosting, monitoring, email, analytics, or support tooling must be reflected here before removing the preview gate.
User control
Account deletion, stored reference handling, retention periods, and contact-data handling should be stated in the final policy.