Information we use.
The read-only wildlife guide does not require an account. When contributor accounts are enabled, Google sign-in through Supabase supplies the account identifier and authentication information required to maintain a session. Authentication email addresses are private and are not part of public profile or gallery queries.
A contributor profile may contain a chosen username, display name and biography. Profiles start private. Only a contributor’s deliberate public-profile choice makes approved profile information visible. We do not ask for a home address, telephone number or exact wildlife coordinates.
Your choices about public information.
Choosing a public profile permits its username, display name and biography to appear on the website. You can change this choice in your dashboard. Published photographs include reviewed captions, species, copyright credit and, when appropriate, a broad region and observation month.
Choose your public name carefully and keep identifying details out of captions. Content already shared publicly may have been copied or cached by other people; we cannot promise to remove those copies.
Private submissions and review.
Submitted originals are held in private staging storage. They are available to their owner and trusted operators, rather than through the public gallery. Approved uploader access and database permissions govern submission access.
Before publication, operators must inspect a photograph, independently re-encode the approved copy, strip metadata, review visual location clues and approve safe public context. This process reduces location-disclosure risk but is not an absolute guarantee that no location can be inferred from an image.
Services and browser storage.
The application uses Cloudflare for hosting, Supabase for database, authentication and media storage, and Google for optional sign-in. These providers process information under their own terms and privacy notices. Browser storage is used for the sign-in session and a controlled return path during authentication.
We do not add advertising trackers or sell contributor information. Hosting and authentication providers may maintain operational and security logs. The website does not collect wildlife incident reports during the pilot.
Retention and deletion.
The pilot retention procedure calls for operators to remove pending or rejected photograph files within 30 days and to record the moderation outcome. This is a manual operational responsibility, not an automatic browser feature. Published material remains until a removal request is resolved or an operator removes it.
Account, profile and publication removal requests require a trusted operator to review ownership and any necessary security or moderation record. We do not promise a fixed account-deletion deadline or automatic deletion of inactive accounts. The operator must document any records retained for a legitimate operational need.
Questions and your rights.
Use the removal-request controls in your own dashboard when available. For privacy, access, correction or account-deletion requests, contact sithumsanjana5433@gmail.com. Include only the details needed to identify your account or public content.
These beta policies require legal review before public contributor launch. They do not claim certification or compliance with a particular privacy law.
Beta policy version: 19 October 2026. Operator and legal review required before public contributor launch.