This is a plain-language pre-launch policy, not legal advice and not a claim that legal or privacy review is complete. Public intake remains closed while the final policy, retention schedule and service providers are confirmed.
Information the platform may hold
The intended service may hold an account email, authentication records, a private identity, a chosen public real name, first name, animal alias or anonymous label, drafts, submitted and released stories, follow-up pages, images, and—if those services are later approved—audio. It also records each separate permission choice, moderation notes, holds, decisions, releases, withdrawals and a limited security and activity history.
Necessary technical information may include session cookies or similar browser storage, IP and device information recorded by hosting or security providers, error information and timestamps. The application does not currently add advertising or marketing trackers. Hosting settings and the final cookie inventory must be verified before launch.
Why it is used
Information is used to create and protect an account, save a contributor’s work, show an exact preview, record permission, support human moderation, publish only an approved and separately released version, honour changes and withdrawals, investigate security problems and operate the service. It must not be sold or used for a purpose that was not clearly explained and permitted.
What becomes public
Only material covered by the contributor’s specific permission and exact-version approval may become public. Submission does not publish anything. Human moderation and a separate release decision are required. Choosing anonymous or an animal alias changes the public byline, but details inside a story may still identify a person.
People and service providers
The founder is currently the human moderator. Future hosting, authentication, database, private-file, email, narration or support providers may process only the information needed for their work under appropriate terms. The final providers, data locations and any processing outside Canada remain open launch decisions and will be disclosed before real intake. Information may also be disclosed when legally required or necessary to address a serious security incident.
Safeguards
Current safeguards include authenticated accounts, contributor and moderator role separation, database row-level security, private drafts, exact-version permissions, human review, separate approval and release steps, withdrawal controls and decision history. No online system can promise perfect security.
Your requests and choices
Contributors are intended to be able to ask for access to, correction of, or an export of their information; change permissions for future use; withdraw a story; and request account deletion. A verified withdrawal immediately makes the affected story unavailable from project-controlled public views. Copies already downloaded, shared or held by others may not be recoverable.
Some limited information may need to remain to honour a withdrawal, protect the service, resolve a dispute or meet a legal obligation. A fixed retention period has not been approved and will not be invented here.
Privacy incidents and questions
A suspected privacy or security incident should be reported through the future verified privacy contact. That contact is not yet publicly available, so the service must not open real intake. Material policy changes will be dated and explained before they apply.
Canadian privacy references
The final assessment must consider Alberta’s Personal Information Protection Act and, where applicable, Canada’s Personal Information Protection and Electronic Documents Act. Read the official guidance from the Government of Alberta and the Office of the Privacy Commissioner of Canada. This page does not decide which law applies in every future circumstance.