Privacy,
without the fog.

1. Plain-language summary

• No login, advertising, sale of data, or cross-app tracking.
• A random app identifier syncs mission history without identifying you by name.
• Photo and voice proof files stay on your device and are not uploaded to Daywild.
• Text proof and optional reflection notes are stored with mission history.
• You can delete active history and linked product events from Settings.
• This website uses no advertising cookies or analytics cookies.

2. Who is responsible

Daywild is independently published and operated by Gautam (“Daywild,” “we,” “us,” or “our”). For privacy questions or requests, email govindgautam933@gmail.com.

3. Information we collect

Information you provide

• Mission context: the time available, energy level, social mode, and budget you choose.
• Completion content: text proof and optional reflection notes. For photo or voice proof, we store the proof type and completion status, not the media file itself.
• Support communications: your email address and anything you choose to include when contacting support.

Information created through use

• Anonymous app identifier: a random UUID generated on your device. It is not based on advertising identifiers, your email, or your phone number.
• Mission and product activity: mission IDs, categories, generated, accepted, completed, skipped, rerolled, and share-sheet-opened events, plus timestamps.
• Technical request data: hosting and security providers may process IP address, request timing, user agent, error, and network information to deliver and protect the service. Daywild does not use it for advertising or cross-app tracking.

Device permissions and on-device content

Photo-library and microphone permission are requested only when a proof type needs them. Selected photos, recordings, locally rendered completion cards, preferences, pending sync items, and a local copy of history may be stored on your device under the operating system’s controls.

4. How we use information

We use the information described above to:

• select and lightly personalize an appropriate mission;
• operate timers, proof flows, completion cards, history, statistics, and streaks;
• sync mission status and retry pending submissions;
• calculate anonymous product measures such as first-mission acceptance, completion, seven-day return, and share-sheet-open rate;
• protect the API, limit abuse, diagnose failures, and maintain reliability;
• respond to support, safety, privacy, and deletion requests; and
• comply with applicable law and enforce our Terms.

Depending on applicable law, these activities are performed to provide the service you request, based on your consent, for our legitimate interests in operating and improving Daywild, or to comply with legal obligations.

5. AI processing

When AI personalization is enabled, the Daywild server may send DeepSeek the approved base mission and the context choices you supplied: time, energy, company, and budget. Daywild does not send DeepSeek your anonymous app ID, text proof, reflection, photo, or audio.

The model cannot replace or invent the core mission. Its output is accepted only when it adds a server-approved contextual lead-in and preserves the approved mission verbatim. Missing keys, timeouts, invalid output, and service failures fall back to the original mission.

6. Service providers and disclosure

We use providers acting on our behalf to operate Daywild:

• Render for API hosting and request delivery;
• Neon for the PostgreSQL database;
• DeepSeek for the limited AI processing described above, when enabled;
• Expo to build and deliver mobile releases; and
• Apple and Google to distribute the app and process store-level diagnostics or transactions under their own policies.

We may disclose information when reasonably necessary to comply with law, respond to lawful process, protect users or the service, investigate fraud or security incidents, or complete a business reorganization subject to appropriate safeguards and notice where required.

We do not sell personal information, share it for cross-context behavioural advertising, or provide it to data brokers.

7. International processing

Daywild and its providers may process information in India, the United States, Singapore, and other countries where they operate. Those countries may have privacy rules different from yours. Where required, we rely on recognized transfer mechanisms and contractual or organizational safeguards.

8. Retention, security, and deletion

Active mission history and linked product events are kept until you delete them or they are no longer reasonably needed for the purposes described here. Support communications may be retained as needed to resolve the request, keep an appropriate record, and meet legal obligations.

Using Settings → Clear local history removes matching active history and linked product events from the device and Daywild server. Residual encrypted backups or security logs may remain for a limited provider-managed recovery or legal-retention period, isolated from ordinary use and deleted or overwritten according to provider schedules.

We use HTTPS in production, access controls, rate limits, minimal collection, secret separation, and encrypted managed infrastructure. No system is perfectly secure, and we cannot guarantee absolute security.

9. Your choices and privacy rights

You can:

• deny or revoke photo and microphone permission in device settings;
• choose not to enter text proof or an optional reflection;
• clear active history and linked product events in Daywild Settings;
• stop AI processing by not using the service or by contacting us about available options;
• request access, correction, deletion, restriction, portability, objection, or withdrawal of consent where applicable; and
• complain to your local data-protection authority where that right applies.

Because Daywild does not maintain named accounts, we may need your anonymous app ID or other reasonable information to locate a record while avoiding disclosure to the wrong person. We may retain information where law permits or requires it.

10. Children

Daywild is not directed to children under 13 and we do not knowingly collect personal information from children under 13. If local law requires a higher age for independent consent, a parent or legal guardian should review and authorize use. A parent or guardian who believes a child provided information can contact us for deletion.

11. Third-party destinations

When you voluntarily open the native share sheet, an app store, an email client, or another external service, that third party’s privacy terms govern what happens there. Daywild does not control those services.

12. Changes to this policy

We may update this policy as Daywild, its providers, or applicable requirements change. We will update the date above and provide additional notice when required. Continued use after an effective update is subject to the revised policy.

13. Contact