This application runs locally for review, with an existing Supabase Free development backend. It is not a public launch. For privacy questions, contact the person who invited you. Operator identity and a public contact address will be published before launch.
Planning without an account
Your full postcode is checked against a local England directory, then discarded. It is not saved with your plan. A guest plan stays on your device for up to seven days. Saved plans keep only a broad region and coarse climate reference; dates currently use fixed England windows, not local weather.
If you tap “Use my location”, your phone shares its position once, only after you allow it. We use it to find the nearest England postcode and then discard it: the position is not stored, logged or shared.
What a saved garden contains
Google sign-in supplies your account identity. We keep your bed dimensions, preferences, exact planting amounts, growing profiles, optional variety labels, plan versions, journal checkpoints, structured observations, optional notes, and photos you choose to upload. These are private to your account. There are no public profiles or sharing feeds.
Photos
Please check photos for faces, children, addresses, number plates, and other identifying details before uploading. We re-encode accepted images and remove embedded metadata. This does not remove visible personal information from the image. Photos are stored privately and viewed through access-checked requests.
Service providers
Supabase provides sign-in, the private database, and private photo storage in its London project. Google handles Google sign-in under its own policies. The application runtime is local; no DigitalOcean server has been created for this sprint. Provider operations may involve processing outside the UK; London hosting is not a promise that every provider operation occurs only in the UK.
Cookies, device storage, and logs
Sign-in uses essential session cookies. Device storage holds your guest plan and public app assets. Private gardens and photos are not added to the offline app cache. We do not enable advertising, behavioural analytics, marketing, or model-training use in this local review service. No payments or charges are enabled. Operational logs are limited to service health and safe event metadata; do not put personal details in URLs.
Deleting your account
Account deletion removes access and the saved garden and journal records. Private image deletion is processed by a retryable background job, so physical cleanup may finish shortly afterwards. Backup copies may persist until the provider’s backup retention expires and must not be restored into active use after an erasure request without replaying the deletion record. Staging infrastructure backups are not a separate Supabase database backup.
You can delete your account in the Sowstory app, under Account and then Privacy.
Before public launch
The operator must finalise the public privacy contact, retention schedule, legal basis and provider arrangements before opening registration. This review service must not be used as a public collection channel for personal data.
