STORIES OF TO · BETA
Your information during the beta.
This explains how Stories of TO uses information during the beta. Please use it for ordinary local stories and feedback, and leave out sensitive personal information.
Accounts and applications
Anyone can browse published neighbourhoods, places, stories and guides without an invitation or account. Clerk handles contributor sign-in with email verification codes or Google. We use your verified account identifier and email to connect your application and contributions. Creating an account does not automatically grant a contributor role; Jos approves applications individually.
Application names, email addresses, neighbourhood interests, answers and decisions are available to the applicant and Jos as site owner. Application information is not a newsletter signup.
Writing, images and public names
Your drafts and uploads are stored in Cloudflare’s database and file storage. You, the site owner and administrators responsible for the neighbourhood can access your neighbourhood draft. Reviewers can access submitted neighbourhood work and its attachments. Private guide drafts are available to their author and the site owner. Private administrator notes and personal owner tasks have separate access restrictions.
Published text, images, credits and your chosen public profile name appear in guides. Published content is visible to anyone and can be shared by link. Your sign-in email is not used as your public byline. Publishing an edit replaces the visible version; saving a draft can leave an earlier published version visible.
Other services and your browser
The map requests tiles, map lettering and icons from OpenFreeMap. Interface fonts are served by Stories of TO. Contributor place searches send the typed place or address to Geoapify. These providers receive the information needed to answer those requests.
Sign-in services use browser storage or cookies to keep you signed in. Saved places are stored on your device and are not synced to your account. Hosting and sign-in providers may retain operational and security logs. We have not added advertising or a newsletter subscription to this test site.
Draft retention plan
We plan to keep beta contributions for the public launch, subject to editorial approval, and remove entries created only for testing after testing ends. We propose keeping rejected applications for 90 days after the decision and our own backup copies for 30 days after creation.
This schedule is awaiting final approval and a checked removal process before the public beta opens. Automatic deletion is not enabled. Provider-managed logs and recovery copies may have different retention periods.
Questions, corrections or removal
Jos monitors hello@storiesofto.ca for feedback, corrections and account-removal requests. You can also contact Jos directly. Use your account email so the request can be verified; never send a verification code or password.
Signing out, removing access or archiving an entry does not automatically erase stored writing, account records or backups. Jos will review removal requests and confirm what can be removed and any remaining copies.