Privacy Policy

1. Controller and contact

The controller determines why and how Rit. processes personal data. The controller is Female Digital, located in Valby, Denmark, with CVR 34402698. You can reach us for privacy and rights requests at info@femaledigital.dk. The complete registered postal address remains to be confirmed before commercial launch, and whether a data-protection officer or representative is required is still under review.

This notice is structured around GDPR Articles 12–14, but missing details and safeguards mean it is not a final compliant notice. See our Terms for service and purchase limitations.

2. Data collected and its sources

You provide your email, profile details, goals, written visions, boards and uploaded images, personalized AI prompts and saved plans, rituals, check-ins, reflection notes, schedules and reminder preferences. Optional entries may include menstrual/period information and wellness metrics such as steps, hydration, nutrition and sleep. Free-text goals and images may also reveal health or other sensitive information.

Authentication supplies account IDs and session information; social sign-in may supply account information authorized with Google or Apple. Technical records can include connection, error and security diagnostics, timestamps and AI quota metadata. Product events record event names and small metadata bags. Subscription status and membership metadata are used for feature access; no purchase provider is configured. If purchases go live, transaction and subscription lifecycle metadata may be received from the chosen store/provider, to be documented then.

Most information comes directly from you or your use of Rit.; sign-in providers and future purchase providers are other potential sources. No unrelated third-party profile enrichment is implemented. Account data is needed to authenticate and save across devices; without it those features cannot work. Optional entries are not required to use the core service. There is no intended solely automated decision with legal or similarly significant effects; you choose whether to save AI suggestions.

3. Purposes and lawful bases

• Account access, cloud saving, your requested boards, rituals, reflection and AI generation: intended basis is performance of contract, Article 6(1)(b), only for processing necessary to those requests.
• Core security, fraud prevention, service reliability and abuse/quota protection: intended basis is legitimate interests, Article 6(1)(f), subject to a documented balancing assessment and your right to object.
• Optional tracking, optional notification permissions and non-essential analytics: consent under Article 6(1)(a), with separate choices and withdrawal where applicable. A device permission alone does not establish consent for every use of data.
• Sensitive health information, including period data and health-revealing notes/images: a separate explicit consent under Article 9(2)(a), alongside Article 6(1)(a), is required before collection for optional tracking. The structured cycle gate is implemented in source: a separate, initially unselected choice records an account-linked version and server timestamp before entering or importing period dates, cycle logs, cycle preferences or guidance edits. Existing data is not implied consent. Web and native saves are checked server-side and by a database guard. Hosted and physical-device verification is pending. This does not establish consent for other health-revealing content or assert full GDPR compliance.
• Future billing records and statutory obligations: performance of contract, Article 6(1)(b), and legal obligation, Article 6(1)(c), only when the relevant purchases and obligations exist.

Do not add sensitive health or intimate photo content while the consent safeguards are unfinished. Product usage analytics are currently disabled: the app sends no product events on web or iPhone, and the server refuses event submissions. No advertising sale or marketing without opt-in is intended; a marketing opt-in system is not configured.

4. AI and recipient categories

When you request an AI Vision, your written prompt is sent through the Lovable AI gateway to the configured Google Gemini Flash model. Saved plans may be stored in your account. Automatic AI image generation is not implemented. The current generator uses written input; do not place unnecessary sensitive details in prompts. We have not verified vendor training, reuse or model-retention terms and make no “not used for training” promise.

Actual integrations include Lovable Cloud for hosting, authentication and account persistence; Lovable AI gateway and Google Gemini for requested generation; Google/Apple for chosen social sign-in; and Google Fonts for font delivery, which can receive connection information when fonts load. Browser speech recognition, if you choose voice input, depends on your browser/device and may use its vendor's service; the exact vendor and processing locations need verification.

Recipient categories include these infrastructure, authentication, AI and device-service providers, authorized operational personnel, and authorities where disclosure is legally required. Error reporting and product analytics also require a processor and necessity audit. Stripe and RevenueCat are not configured; future Apple purchases require an updated recipient notice. No external private-image storage service is configured: new uploaded images are currently stored inline with account data.

5. International transfers and safeguards

EU/EEA processing locations, subprocessor lists and any transfer countries have not been verified. This draft does not promise EU-only storage. Before launch, the controller must document actual destinations, the applicable adequacy decision or other lawful safeguards (such as standard contractual clauses and necessary supplementary measures), and how you can obtain a copy by contacting info@femaledigital.dk. Processor agreements and transfer assessments remain outstanding.

6. Retention and security

Retention should be limited to what is necessary to deliver requested features, maintain account records, meet applicable legal obligations, resolve disputes and protect security. Account content currently persists until changed or reset; in-app deletion is implemented in source, with hosted/device verification and backup-retention handling still unfinished. Logs, AI reservation records, subscription records and backups each need documented retention and deletion criteria. No fixed deletion timeline or immediate removal from backups is promised.

Account-scoped access checks, server-verified permissions and bounded image/AI inputs are implemented, but no system is risk-free. Protect credentials, device access and exported backups. Photos may identify you or others; minimize identifying and health-sensitive content. Notification text can be visible on a lock screen. Cloud export files contain personal information and should be stored safely.

7. Cookies, local storage and analytics

Browser storage is used for sign-in sessions, same-account cached state, temporary pre-account onboarding choices, preferences and reminder deduplication. These support functionality you request; clearing storage can remove unsaved drafts or sign you out. No advertising-cookie integration is configured.

Non-essential analytics or cookies require a valid choice before use where consent is required, and an equally accessible withdrawal option. Rit. currently uses no optional product analytics, so no such choice is offered; if analytics are added later, they will stay off until you opt in. Hosting and authentication providers still keep technical/security logs (for example request and sign-in records), and Google Fonts receives connection information when fonts load; these need separate assessment.

8. Your rights and practical limitations

Subject to applicable conditions, you may request access, correction, erasure, restriction and portability, and object to processing based on legitimate interests. You may withdraw consent at any time without affecting the lawfulness of processing before withdrawal. Responses normally must be provided within one month under GDPR, with any lawful extension explained. Identity verification should be proportionate.

You can edit entries and use Settings → Backups & data → Export data for a copy of available app content; this is not necessarily a complete GDPR access response. Reset cycle data clears structured cycle entries but does not withdraw consent, and Reset all data resets app content; neither deletes your account or guarantees removal of logs or backups.

Settings → Account → Delete account initiates permanent deletion with DELETE confirmation and password verification. It removes your identity and account-owned data from the live service; hosted and physical-device verification is still pending. Backups, security logs and copies on other devices or exported by you are not guaranteed to disappear immediately. For structured cycle tracking, Settings → Cycle → Withdraw cycle consent removes period dates, cycle logs, cycle settings, guidance edits and automatic cycle context in reflections from live account state in the same transaction as withdrawal. Boards, rituals and reflection text remain. A versioned grant/withdrawal history remains until account deletion for consent accountability, subject to a retention policy still being finalized. The current device clears its cycle cache after success; other devices must reconnect and refresh, and exports/backups are not remotely erased. Broader health-data withdrawal safeguards remain unfinished. Do not mistake resetting data, signing out or cancelling a future subscription for account deletion. Rights requests can be sent to info@femaledigital.dk; additional safeguards for other sensitive wellness records, free-text reflections, visions, photos and AI prompts must be completed before launch; these cannot be reliably classified automatically. The provider must explain any lawful grounds for retaining particular records after a request.

You may complain to Datatilsynet, the Danish Data Protection Agency, or the supervisory authority in your place of habitual residence, work or alleged infringement.

9. Minors and updates

Age eligibility and any required parental authorization have not been finalized or technically enforced. Children's privacy and any applicable national consent rules need review before launch.

The date above identifies this draft. Material changes should be clearly notified before taking effect, with new consent where required rather than retroactively changing the purpose of collected data. The finalized notice must complete recipients, transfers and retention criteria.

Reference: GDPR, including Articles 9 and 12–14.