Nido Privacy Policy

Last updated: 27 October 2026 Controller: Francisco José Fernández Blanco Privacy contact: [email protected]

This policy explains what information Nido processes, why, and what happens when you connect your devices, use optional features or delete an account. It applies to Nido for iOS and Android and the official holanido.app website. The controller is Francisco José Fernández Blanco, an individual established in Spain. You can contact him at [email protected].

1. Your account and shared Nido

You can start using Nido on one device and connect your partner later with an invitation code. For connected features, Nido creates an anonymous technical account in Supabase Auth, with a user ID and session credentials. Creating this account does not require an email address, phone number, personal password or Apple or Google sign-in. Your device keeps the session and a random installation ID. Each person in a connected couple has their own technical account.

An invitation code connects the two members of the same Nido. It can be used once and remains valid until used or replaced by its creator. Each person can generate a personal recovery code. The server stores its cryptographic hash rather than the readable code. Anyone who obtains your recovery code can regain access to your account, so keep it private.

Your device keeps a local copy of progress and content. Creating a cloud Nido, preparing recovery or using features that require that Nido can store its state in Supabase before your partner joins. Not having connected your partner therefore does not mean that all data stays exclusively on your phone. Once they join, they can access shared content according to the rules of each feature. Earlier versions could create an anonymous technical account when opened for initial usage counts. The update that includes “Your age” does not create a new account before checking the age you enter. A technical account is still needed for connected features.

2. Information we process

Depending on the features you use, this includes:

• Account and connection: account ID, session credentials, random device ID, Nido membership, invitations, recovery information and technical information needed to synchronise and protect access.
• Couple information and activity: names you enter, the date and time from which you count your time together, answers to questions and activities, game results and attempts, achievements, coins, activity history and shared decisions. Some answers remain hidden from your partner until you have both finished. They are stored by the service to provide this feature.
• Pet and home: pet type and name, care such as cuddles, food and baths, status and progress, accessories, decoration, coins and each member's actions.
• Content you add: photographs and captions, notes, drawings, comments, memories and plans. Photos are resized and compressed before upload when your Nido is connected. The album supports images, not video uploads. Temporary local or offline copies may be kept to display content and enable synchronisation.
• Plans and calendar: descriptions, optional dates and status of plans, and other dates you enter. Nido has its own calendar and does not request access to your system calendar.
• Historical cycle records, a feature removed from the new version: the new version no longer lets you mark period days or enable cycle recording. Earlier versions stored manually entered dates that were shared with your partner in a connected Nido. The structured date and consent fields have been removed from shared server state and recovery copies. The server discards uploads of those fields from older versions. Copies may remain on devices that have not updated, in exports and in provider technical backups until the relevant deletion process is completed. Removing the button does not confirm that every copy has been deleted. You can request information or erasure at [email protected] without emailing the dates. Nido does not use HealthKit or Health Connect.
• Age in version 1.0.9: you enter your own age in years on your phone to check access from age 18. Only an under-18 or 18-and-over range is kept locally; the exact number and date of birth are not saved. Ranges from an earlier version are read to apply the same restriction and do not grant access to minors. The preference is not included in shared Nido data, exported backups or usage statistics, and is not shown to your partner. Google receives the relevant advertising signals for an eligible adult, not the exact age entered.
• Subscriptions and rewards: purchased product, transaction or subscription IDs and status supplied by Apple or Google, expiry dates, and rewarded-ad viewing and verification records needed to grant coins or extra attempts. Nido does not receive your full payment card details.
• Notifications: if enabled, your permission and preferences, device push token, platform, time zone, display language and the minimum information about the event that triggers the notification. Remote notifications use predefined text and do not contain photos, notes or drawings.
• Third-party technical information: providers involved in connection, advertising and notifications may process IP addresses, device or advertising IDs, ad interactions and diagnostic data according to their technologies and settings. Section 5 gives more detail.
• Basic app usage: Nido counts people opening the app, creating a Nido, tapping to share an invitation, connecting a partner, returning the next day and activating Premium. Reports contain daily totals, not names, photos, answers, messages, invitation codes or device IDs. A pseudonymous fingerprint of the technical account is temporarily stored separately to avoid counting a step twice. You can turn this measurement off in Settings.

Nido does not request contacts or system calendar access. Microphone and approximate location access are optional and require your choice and device permission, as described below. You choose which image to share through the photo picker. iOS also declares a camera permission for taking photographs.

3. Purposes and legal bases

We use account, connection, content, activity, pet, plan and purchase data to provide requested features, synchronise your Nido, restore access, verify subscriptions and grant rewards. The ordinary legal basis is performance of the requested service (GDPR Article 6(1)(b)). Technical access and verification data help maintain security and prevent fraud, based on our legitimate interest in protecting users and the service (Article 6(1)(f)). Where a law requires retention or disclosure, the basis is compliance with that legal obligation (Article 6(1)(c)). You can ask about our legitimate-interest balancing assessment.

Usage statistics are optional. In the privacy update, they stay off until an adult chooses to enable them in Settings → Help improve Nido, after reviewing their purpose and retention. Consent is the basis for this optional collection (GDPR Article 6(1)(a)). You do not need to enable statistics to use Nido, buy Premium or watch rewarded ads. You can turn them off in the same setting. Withdrawing consent does not automatically erase data lawfully collected before withdrawal, which remains subject to its retention periods and your erasure rights.

The counts help identify difficulties with general steps, such as opening the app or connecting a Nido. Supabase processes a pseudonymous identifier to avoid duplicate counts. Photos, notes and answers are never sent to these statistics. The update sends no counts for unknown or minor age ranges, and an old enabled preference is not treated as informed consent for the new collection. Earlier versions could carry out limited measurement based on the stated legitimate interest in improving the service. Previously collected data remains subject to retention periods and your rights. The new consent does not apply retroactively.

Notifications are optional and can be disabled in Nido or your device settings. Rewarded ads appear when you choose to watch one for a reward. Nido uses Google's consent management platform where applicable and provides its privacy choices where required. Where consent is necessary (Article 6(1)(a)), it depends on your choices in that form and system permissions. Choosing to watch a rewarded ad does not itself mean consenting to personalised advertising.

In the update that includes “Your age”, the Ads SDK and its consent request are prepared when you choose to view an ad and have entered an eligible age. Adults retain the ordinary consent and system controls: entering 18 or older does not consent to personalized advertising. Google's available advertising privacy options remain accessible without authorizing another ad.

Retirement of cycle recording. Dates from earlier versions may reveal health information. Their collection required an appropriate legal basis and, where GDPR Article 9(2)(a) applied, explicit consent. The new version removes the controls for adding or managing them. The server blocks uploads of those fields from earlier versions, and they have been removed from shared state and recovery copies. When opened, the new version cleans its local copies and pending changes, and prevents imports from restoring those fields. We do not claim that provider technical backups, devices that have not updated or exports outside Nido's control have all been erased. You can withdraw previous consent and request erasure at [email protected]. Exported copies or copies outside Nido's control require separate handling; retiring a feature does not make an earlier unlawful collection lawful.

4. Who can see shared information

Both members of a connected Nido can access shared content and progress: pet, activity, photos, notes, drawings, memories, plans and calendar. If you used the previous cycle recording feature, those dates were also shared between connected members while they remained in the Nido. Some game or question answers are temporarily hidden until both people finish. Nido does not currently offer an Intimacy section. Shared content is not end-to-end encrypted; the service processes it to provide app features.

Do not publish or store information about other people without their permission. Your partner can see photos or text you share and may save copies outside Nido that the app cannot delete.

Stopping sharing and keeping memories

In version 1.0.9, Settings → Privacy and safety → Stop sharing with my partner turns your Nido into a read-only archive for both members. New contributions, invitations and notifications for that Nido are blocked; a notification already handed to the phone notification provider could still arrive. Memories are not automatically split or deleted. Each person retains access to content previously available to them; hidden answers stay hidden. This cannot be undone in the app, does not create another Nido and does not cancel subscriptions.

The archive remains in Supabase. Account deletion is still available separately and may remove content attributed to the person deleting their account from the archive. When the app receives the block, it keeps a local backup from before blocking to preserve changes that had not yet synchronised. This backup, exports and retained local images may contain data subsequently removed from the server archive; remote erasure of those copies is not guaranteed. Account deletion clears local app data on the device used for deletion, but cannot erase exports or copies held by someone else. Contact [email protected] for information or to exercise your rights.

5. Providers and external services

• Supabase: anonymous authentication, database, real-time synchronisation, server functions and private image storage. Nido checks account identity and Nido membership before granting access to private content. Images are delivered through temporary links. Content is hosted in the infrastructure of Nido's Supabase project. Supabase and its subprocessors may participate in hosting, maintenance and security.
• Google AdMob and User Messaging Platform: optional rewarded ads and advertising consent management. Google's ad SDK may receive IP addresses, device or advertising IDs, app and ad interactions and diagnostic data to serve and measure ads and prevent fraud. The final Android package includes the advertising ID permission. Nido sends an attempt ID to its server and verifies Google's signed confirmation before granting a reward. Nido does not send photos, notes, drawings or cycle dates to AdMob for ad selection.
• Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM): remote notification delivery on iOS and Android when enabled. Android includes Firebase Messaging and the technical installation IDs needed for delivery. Nido does not integrate Firebase Analytics or Crashlytics; Firebase Analytics collection is disabled in its configuration.
• RevenueCat: subscription status management and synchronisation. It receives the technical account ID and purchase information needed to verify and restore Premium, such as products, transactions, expiry and platform. Nido does not send photos, notes, answers or cycle dates to RevenueCat. See RevenueCat's privacy policy.
• Apple App Store and Google Play: purchases and subscriptions are processed on their platforms. Nido receives and verifies the transaction information needed to activate Premium and determine its validity.

On iOS, from version 1.0.7, Nido registers the first opening through Apple's SKAdNetwork for aggregate advertising-install measurement. This does not request tracking permission or send Nido content or account IDs to TikTok. Reports may be delayed or limited in detail.

This integration uses only Apple's aggregate attribution APIs. It does not include TikTok's events SDK, request advertising-ID access or add tracking controls or prompts in Nido. The app does not transmit names, photos, notes, answers, cycle dates, invitation or recovery codes, or account IDs to TikTok. Apple applies SKAdNetwork's attribution conditions, delays and privacy limits. Android does not include this integration in this version.

International transfers

Provider infrastructure and support may involve processing outside the European Economic Area. Where applicable, GDPR Chapter V safeguards must apply, such as adequacy decisions or standard contractual clauses. We do not claim that all data stays exclusively in Spain or the European Union. You can request information about applicable safeguards at [email protected]. See also the data protection terms of Supabase, Google and Apple.

6. Storage, retention and security

App content is stored on your device using local storage and IndexedDB. The security update uses iOS Keychain and Android Keystore-backed encrypted storage for sessions and recovery codes awaiting saving. Earlier versions used the app's private web storage. The old copy is removed when migration to secure storage is confirmed. Widgets may keep a reduced local copy of the photo, drawing or time-together summary you choose to show. Android automatic backup and data transfer are disabled through the configured extraction rules.

Connected content and progress remain in Supabase while the account and Nido remain active, or until deleted through app features. Accounts and memories are not automatically deleted for inactivity. Notification delivery events normally expire after 24 hours. When the notification worker runs, it removes events expired for over seven days; this is not a guaranteed deadline for removing every copy. Transaction, attempt and reward records are kept as needed to verify the service or until the associated account or Nido is deleted, unless legal retention duties apply.

Pseudonymous deduplication fingerprints are deleted after 90 days without activity; daily totals after 180 days. These records do not contain your Nido content.

Supabase communications use HTTPS and the database applies access controls. Photos use private storage and temporary links after membership checks. Recovery codes are stored as cryptographic hashes. No system guarantees absolute security. Keep invitation and especially recovery codes private, and protect access to your device.

Providers' physical storage and technical backups may follow their own deletion cycles. Exported copies and copies another person saves outside Nido are not controlled by the app.

7. Deleting accounts and data

Go to Us → Settings → My account and recovery → Delete my account, including before connecting a partner. Deletion requires written confirmation. It removes your Supabase technical account, access and data identified as yours, including your notes and photos. If your partner remains, they keep their own content and shared memories not attributed to the deleted account. Certain shared activities reset; any historical cycle dates and consents remaining in the shared calendar are also removed. If you are the last member, the entire Nido is deleted and deletion of its private files is requested. The app also clears local data and disables widgets on the device performing the deletion.

Deletion includes requesting removal of the associated RevenueCat profile and previous recovery identifiers. If a provider does not respond, the request waits for a retry. This does not remove purchases from your Apple or Google history.

Deleting an account does not automatically cancel an active Apple or Google subscription. You can delete the account even with a subscription active. Manage the subscription separately in the relevant store to prevent later renewals. Purchases may remain in store records and legally required minimum records. Private files may need a later cleanup task if the provider does not respond immediately. Pending requests are processed by a scheduled task and do not depend on your partner deleting their account. For an active Nido, after receiving updated state, the app removes images no longer in the Nido from its cache. Offline devices may retain copies until they synchronise again. Archived Nidos and protective local backups follow the retention explained under “Stopping sharing and keeping memories”; synchronisation is not promised to erase those copies.

Without app access: visit our account deletion page. Anonymous accounts have no associated email, so we must securely verify ownership before acting on requests made outside the app. Do not email your recovery code. Delete any Nido backups you exported from wherever you stored them.

8. Your rights and preferences

You can view and change some information in the app, export a Nido backup in Settings, and request access, correction, deletion, restriction, objection or portability where applicable. Withdrawing consent does not affect processing performed before withdrawal. We respond within applicable legal deadlines. Under the GDPR, the general deadline is one month after receipt. Different or shorter deadlines under your country’s law and for the right you exercise still apply. If complexity or request volume permits an extension, we will tell you within that first month. We do not routinely demand identity documents. Contact [email protected]; we may ask for proportionate proof that you control the account or Nido involved. You may also complain to a competent data protection authority, such as Spain's AEPD.

You can disable notifications in the app or operating system and review advertising privacy choices when Google's consent platform offers them. Disabling a feature alone does not delete stored information. Use deletion controls or contact us.

9. Minimum age and minors

Nido is intended for people aged 18 and over. Version 1.0.9 asks for your own age when creating or joining a Nido and when needed to recover access. Existing users who have not provided an age are asked before continuing with ordinary features, without repeating the full onboarding. An existing adult age range allows continued access. The number is converted locally into under 18 or 18 and over. The exact age is not saved, and no date of birth is requested. You can view the range in Settings → Your age.

Entering an age under 18, or having an earlier underage range recorded, blocks creating or connecting a Nido and ordinary use in that version. Account deletion management and support remain accessible. If the age was entered incorrectly, ask the privacy contact to review it. Self-declaration does not verify identity. Do not add information about minors or images of other people without the authorization required for that situation.

Earlier versions may have different controls and ratings. This change does not mean historical data has all been erased or make an earlier collection lawful retroactively. If you are under 18 and already have an account, or act for a minor whose information is processed, contact [email protected] to review access and exercise applicable rights; do not send private codes or unnecessary identity documents. We will review the case and, where appropriate, arrange deletion. The content rating calculated by each store may differ from the service’s minimum age.

10. Website and support communications

The website has no ads or advertising pixels. Website and tool measurement is optional and is explained in the privacy choices section at the end of this page. Contact links open your email app; sending depends on your email provider. If you write to [email protected], we process your email address, message and files you choose to send to answer your question, manage an issue or handle your rights. Hostinger provides the professional mailbox separately from anonymous app accounts. Do not send recovery codes, passwords, intimate photos or unnecessary cycle information. Correspondence is retained while handling the request and as needed for applicable duties or liabilities. Nido's code does not set an automatic deletion period for this mailbox. Cloudflare Pages hosts the official website. Cloudflare may process IP addresses and request details to serve and protect the site; we do not use them to build advertising profiles.

11. Changes and contact

We will update this policy when relevant processing, providers or features change, showing a new date and giving appropriate notice where required. For privacy questions or rights requests, contact Francisco José Fernández Blanco at [email protected].

12. Additional information about data sources and safety

We may receive information about you from your partner, such as the name they enter, your relationship date or memories they share. We also receive technical device data and purchase verification from the stores and RevenueCat. You can ask what information we hold, where it came from, and request correction or erasure even if you do not yet use Nido. When inviting someone, share this policy and do not enter sensitive information about them without a valid basis.

The new version asks you to accept the usage rules before creating, connecting or publishing to a shared Nido. It stores the rules version, acceptance date and user association locally. This does not authorise advertising or statistics. If you decline, support, recovery and account deletion remain accessible.

When handling an abuse report, we may review the information strictly necessary to locate and assess the content. Confirmed image removal can remove references from the Nido and its recovery copies and block uploads of identical files. We retain a SHA-256 fingerprint, case reference, file identifiers and dates for this purpose; the block record does not contain the photograph. These records do not expire automatically: their continued necessity must be reviewed so that only information needed to prevent reappearance or address legal responsibilities is retained. You can request a review. This is not facial recognition or automatic detection of every variant. Offline devices, older versions, screenshots and exports may retain copies. Stopping sharing is not the same as removing an image.

The main Supabase database is in Frankfurt, Germany. Supabase Pte. Ltd. is based in Singapore and its group includes support in the United States; the main location does not constrain every support access. RevenueCat, Inc. stores customer data in AWS data centres in the United States. We send it technical identifiers and subscription information when verifying or restoring Premium, not the couple's memories. Transfers use encrypted internet connections when you use a feature or its status is checked. Each feature's categories, purposes and retention are described in this policy; providers may have their own log and technical backup cycles. These known locations are not an exhaustive list of every subprocessor country.

Where your local law provides rights concerning sale, sharing or targeted advertising, you can exercise them through the Google advertising privacy options offered in the app and contact the controller. Exercising a right does not penalise ordinary use. We do not claim that every advertising disclosure falls outside local definitions of sale or sharing. You may request a review of our response to a privacy request; applicable rights and deadlines depend on your place of residence. A translation or Nido's technical availability does not replace each country's legal requirements.

13. Apple age check

Update 1.0.9 adds a check of Apple's regional age requirements on iPhone. When the system says it is required, Nido requests the age range associated with the Apple Account; the system may show its own notice. Nido uses the response only to control access to the service, not for advertising or analytics. This feature does not request or receive identity documents or a date of birth. Apple's response stays in memory during the check; it is not added to the shared Nido or stored in Supabase. If adult access cannot be confirmed, you can retry and still access deletion and support options, without deleting your memories. Older systems that do not provide the regional check retain the declared-age control; this is not presented as Apple verification. The response is an age signal, not a guarantee of identity. Where Apple requires acknowledgment of an important update, its change notice is shown before you can continue. Only an acknowledgment marker is stored on this device, linked by a hash to the app installation transaction and the change version. It contains no age and is not shared with your partner, advertisers or Supabase. The marker does not replace a fresh access check.

14. Advertising partners

Google may work with other advertising partners to serve or measure ads and prevent fraud. The list and purposes shown in the consent manager may change; you can consult providers’ policies there and manage the available choices. Inclusion in the partner list does not mean every partner receives data about every user. This list is separate from the providers that store Nido’s private memories.

15. Support email

We handle [email protected] directly in Hostinger Email, with no forwarding configured to another provider. Hostinger confirmed that mailbox content and backups are stored in France and Germany. This does not guarantee that all technical access takes place within the European Economic Area. The service is covered by Hostinger’s data processing addendum; we have asked its privacy team for details of access countries and service-specific subprocessors. Do not send passwords, recovery codes or unnecessary copies of intimate images to support.