
DAWNSIDE PTY LTD (“we”, “our”, or “us”) built Florra as a fitness-focused mobile game that turns your real-world steps into in-game rewards. This Privacy Policy explains how we collect, use, and store your data when you use Florra.
We collect only the data needed to provide core gameplay features, subscriptions, and app stability.
Data We Collect:
Health & Derived Data: We read your step count from Apple HealthKit on-device. We never store raw HealthKit data on our servers. If you opt in to weekly challenges/leaderboards, we store derived gameplay metrics (e.g., participation flag, weekly points, rank, and display name) on our servers to run the feature.
Gameplay Data: In-game progress (e.g., Plants, Plots, Pets, Eggs, Coins) stored locally and on our cloud servers (Supabase) to enable account recovery and sync across devices.
Crash Logs: Anonymous crash data for stability improvements (via Apple services).
Analytics (Anonymous Events via PostHog): We capture only basic, anonymous gameplay events—like seed purchases or egg hatching times—using PostHog in anonymous mode. No PII (e.g. email, IP, name) is collected, and PostHog does not create person profiles for these events.
Purchase Data: Subscription and purchase status managed by RevenueCat.
Notifications (Device Tokens): If you enable notifications, Apple provides a device token so we can send challenge reminders (e.g., when a new week starts). We do not use device tokens for advertising.
We do not collect personally identifiable information like your name, email, or contact details inside the app.
Health Data
Raw step counts remain on your device
Derived challenge/leaderboard data (e.g., weekly points and rank) is stored in our cloud database if you opt in, so the feature works across devices.
Gameplay Data
Stored locally and in Supabase (cloud backup servers located in Supabase's hosting regions). If you opt in to leaderboards, your weekly challenge data is stored with your gameplay data.
Crash Logs & Analytics
Handled by Apple and PostHog (not directly stored by us)
Subscription Status
Managed through RevenueCat, not directly stored by us
Florra integrates with the following services:
Apple HealthKit: To track steps for gameplay.
Supabase: For cloud save of your gameplay data (Plants, Pets, Coins, etc.)
RevenueCat: For in-app purchase and subscription management.
Apple (App Store / Crash Reporting): For app analytics and crash logs.
PostHog: To track anonymous gameplay events (e.g. seed purchases, egg hatching).
• What we store: week identifier, your participation status, points/score, rank, and your chosen display name.
• Visibility: Your display name, score, and rank are visible to other players in the leaderboard. You can choose an anonymous display name.
• No Ads: We do not use health-derived data for advertising or marketing.
• Opt-in only: This feature is optional and off by default.
If you are located in the European Union (EU) or other regions with data rights laws (like GDPR):
You have the right to access, correct, or request deletion of your cloud-stored gameplay data (e.g., your saved farm and pet data in Supabase).
Florra does not collect personal identifiers like your name or email inside the app.
If you opt-in to future cloud backup, you’ll have the option to request deletion via support@dawnside.io.
Florra is not directed at children under 13 (or under 16 in certain regions).We do not knowingly collect personal information from children.
We may update this Privacy Policy in the future. If we do, we’ll notify users inside the Florra app.
For privacy-related questions or data deletion requests:
Email: support@dawnside.io
If you’re located outside Australia (including the EU):
Your gameplay data (when stored in Supabase) may be processed in Australia, the United States, or other countries where our service providers operate.
We rely on legitimate interest and user consent (for cloud features) as our lawful bases for processing under GDPR.
At Florra, we believe in privacy-first design. Your step count powers gameplay; progress is safely stored; your personal identity is never required or shared.