Hatch Track stores only the information needed to provide incubation, flock, photo, cloud-sync, and optional sensor features.
Account identifiers, hatch and flock records, settings, photos you choose to upload, and optional sensor readings. Device-local data may remain on your device when you are signed out.
Uploaded photos are compressed by the app before cloud storage. This recompression removes ordinary camera metadata such as embedded GPS from the uploaded copy.
Detailed sensor readings are retained for up to 90 days. Hourly summaries may be retained longer so historical trends remain useful without storing every raw reading indefinitely.
Hatch Track currently uses Vercel for website hosting and Supabase for authentication, database, file storage, and backend functions. Reusable breed-reference images may be delivered from Wikimedia Commons and retain source/license attribution.
You can export your Hatch Track data. Signed-in users can permanently delete their Hatch Track cloud account and associated cloud data from Settings.
Cloud traffic uses HTTPS. Database rows and private photo storage use account-based access controls. No security system can guarantee absolute protection.
This policy may be updated as Hatch Track gains new features or service providers. Material changes should be reflected here before those features are broadly released.