Your information, explained.

Privacy overview for this release

Updated 3 November 2026. This overview describes this implementation. Organization contact details and a complete launch policy still need review before a broad public launch.

What the app stores

Projects, community posts, comments, likes, profile display names, account identifiers, timestamps, and lesson completion are stored in the application database. Uploaded community images and their descriptions are stored with the post. Visible community submissions can be read by other visitors who can access this site. Reports, moderator decisions, and account identifiers are retained for review. Deleting a post clears its text and image reference while retaining a tombstone and report/audit metadata. Avoid posting personal or sensitive details.

Administration and activity

Signed-in activity records your account email and name, first and last seen times, current app page, and approximate country/city when provided by the hosting network. We do not store IP addresses or collect GPS location for this dashboard. Anonymous visitors are not added to account activity records. AI chat and voice require a verified account; visitors can browse public pages without signing in. Administrators can review this activity and suspend contribution access. AI request metadata includes a broad topic category, model, response status, reported token counts, and response time, retained for 90 days. Full questions and AI replies are not stored in these analytics. Account location and activity are updated when you revisit. Administrative changes are logged for review.

Conversations and external services

Chat messages are held in this page’s memory. When AI is enabled, recent messages are sent to the configured AI provider to generate a response. Voice recordings are sent to OpenAI for transcription after recording stops. Spoken replies are AI-generated by OpenAI. This app does not store recordings or generated audio in D1 or R2; the provider processes them under its settings and terms. Generated audio can remain in page memory until you leave or play a different reply. Reloading clears the on-page conversation; provider retention is governed by that provider’s settings and terms.

City searches are sent to Open-Meteo. Weather can fall back to MET Norway forecasts. Public city lookup and environmental results are cached in the application database to reduce repeated provider requests. News is retrieved from The Guardian. Welcome emails use Resend after verified sign-in. If you opt in to app update emails, your verified email and subscription status are managed in a dedicated Resend segment; you can opt out in your profile or through the email unsubscribe link. Welcome delivery status and timestamps are stored in our database. Authentication is provided by Supabase. Email/password and Google sign-in use Supabase to verify your account. App records remain in our application database; passwords are handled by Supabase.

Account requests

Self-service deletion and export are not available in this release. A contact channel, retention schedule, and request handling process must be established before public launch.