Itzuna · Legal information
Itzuna Privacy Policy
Version: 2.1 · Last updated: 18 October 2026
This policy explains how we process personal data in the Itzuna app, its website and when you request access to and take part in its beta. It also applies if you take part in a group by invitation without creating your own account with an email address.
It is available at itzuna.com/privacidad/. Privacy information is provided separately from the Terms: being aware of this policy does not amount to giving general consent.
1. Controller and contact
Controller: Raúl Victoria Martín, owner of Itzuna
Tax ID (NIF): 50203238B
Address: Paseo de la Florida 24, 28008 Madrid (Madrid), Spain
Email for privacy, support and incidents: privacidad@itzuna.com
You can use this email address even if you have left a group, your account is suspended or you can no longer access the app.
2. What data we process and where it comes from
App and groups
| Data | Source |
|---|---|
| Name or nickname, icon, image and member profile within the group | Entered by you or by the person who creates or manages your profile. |
| Email address and account identifier; access and session data | Provided by you when creating or using your account, or generated by the authentication service. |
| Google name, email address, identifier and photo, if you choose that sign-in | Shared by Google as part of the identification you request. |
| Group, role and permissions, invitations and the link between an account and a profile | Generated by the creation, invitation and administration features. |
| Tasks, assignments, dates, completion marks and who records them | Provided by authorised members and through use of the app. |
| Photos or texts provided as proof | Uploaded by the person who records the proof. |
| Points, streaks, cards, wildcards, rewards and redemptions | The group’s settings and activity. |
| Absences, language and other group settings | Entered by authorised people. |
| Notification preferences and device token for notifications | Your settings and the notification system. |
| Version and date of the accepted Terms, language and means of acceptance | Your actions in the acceptance procedure. |
| Historical declarations of being of legal age or of who created a group, where made under earlier versions | The actions taken at the time. They are kept with their original meaning; version 1.1 of the Terms does not ask for those declarations. |
| Version of the privacy notice shown and, where applicable, of the group rules | The information and participation process. |
We do not routinely ask for an identity document, date of birth, phone number or address to take part in a group. A sign-in provider, such as Google, may share a fuller name than a nickname. Providing additional data in a task, image or message is the responsibility of whoever enters it; avoid information that is not necessary, especially health data, identity documents or intimate images.
A guest session has a technical identifier and can be linked to a profile and its activity. Although it is internally called “anonymous”, that does not mean the associated data are anonymous or impossible to relate to a person.
Website and beta
When you request access to the beta, we process your email address, mobile platform, type of group, approximate size if you provide it, language, dates, request status and version of the privacy notice. After confirmation, we may process the beta account identifier, activation status and attempts, and technical error codes.
The confirmation and unsubscribe links and the receipt used to check that access is ready use technical identifiers, which are stored as a cryptographic hash. That receipt verifies a technical process; it does not prove consent or acceptance of the Terms.
The form does not collect UTM parameters or where the visit came from in new requests. We do not add the IP address to the request records. The connection to the website and its security services does share technical data, including the IP address, with the providers that deliver and protect it.
Support, security and rights
If you contact us, we process your reply address, the necessary content of your query and the data needed to locate the problem or handle the request. In an incident or suspension we may record its reference, the account or group affected, the reason, the measure, dates, the review and the outcome.
Technical services may generate access, session, email delivery, error and security logs, such as IP address, browser, dates and technical identifiers. The absence of the IP address in the form or in the contractual receipt does not mean that no provider processes it.
3. What we use the data for and on what basis
| Purpose | Legal basis |
|---|---|
| Managing the account of the person who contracts, their access and the features requested; proving acceptance during the relationship | Performance of the contract, Article 6(1)(b) GDPR. |
| Processing a beta request, confirming the email address, preparing access and communicating matters necessary to take part | Pre-contractual steps requested and, when taking part, provision of the service, Article 6(1)(b). Does not include advertising or newsletters. |
| Allowing invited people who do not contract to take part, maintaining their profiles and the shared activity | Legitimate interest in facilitating the organisation of the group requested by its members and keeping its activity consistent, Article 6(1)(f), balanced against the rights of the people affected and with particular attention to minors. |
| Delivering functional notices about tasks and activity, according to the chosen settings | Legitimate interest in making the requested service useful, Article 6(1)(f). The device permission enables the channel and can be withdrawn; it does not authorise advertising. |
| Protecting accounts and groups, preventing fraud or abuse, investigating incidents and managing proportionate restrictions | Legitimate interest in the security of the service and its users, Article 6(1)(f); legal obligation where there is a specific requirement or duty, Article 6(1)(c). |
| Providing support | Performance of the contract where it concerns the service of the person who contracts; legitimate interest in assisting participants and resolving incidents in other cases. |
| Keeping limited technical metrics on the website’s operation and performance | Legitimate interest in maintaining and improving its operation, Article 6(1)(f), to the extent that personal data are processed. |
| Handling rights requests and meeting legal obligations | Compliance with the specific applicable obligation, Article 6(1)(c). |
| Keeping minimum proof of the relationship and handling claims | Legitimate interest in establishing, exercising or defending claims, Article 6(1)(f); legal obligation to retain or block data where applicable. |
Legitimate interest does not allow your rights to be ignored. You can object on grounds relating to your particular situation. We will assess the request and stop processing the data unless there are compelling legitimate grounds that override it or the data are needed for claims, in accordance with the law.
Where other processing requires consent, it will be requested specifically and can be withdrawn without affecting the lawfulness of earlier processing. We do not treat acceptance of the Terms, the creation of a group, historical declarations or reading this notice as general consent.
The data needed for a feature are used to be able to provide it: without an email address we cannot process a beta request that way; without the minimum data of a profile that participation cannot be maintained. Profile photos and other optional content can be left out. If a group task requires proof, that condition is set by its configuration.
4. Local groups, cloud and who can see the information
Local use and sync
If you keep a group only on the device, its content is stored there and we do not receive that content unless you use a feature that sends it, such as uploading it to the cloud or sharing it. This does not mean that all other app features are independent of network services: authentication, updates or features you turn on may need a connection and their own technical data.
In a cloud group, the information needed to sync it and to enable access by authorised people is processed.
Visibility within the group
Participants can see shared information, such as names, icons, tasks, activity and points, according to the features and permissions. Photos and texts provided as proof have more limited access: the person who provides them and the people who manage the group, according to the permissions of the service.
Administrators can manage profiles and grant access through invitations. Whoever joins an existing profile accesses the information that profile holds according to their permissions. If another person joins, a new profile must be created. Changing a name or unlinking an account does not make the history anonymous.
Anyone who provides information about another person or grants access must be entitled to do so, respect that person’s rights and consider who will be able to view that information. Managing a group does not make a person the legal representative of its members.
A person with access may keep or share information through the available features, screenshots or other means. That possibility does not authorise disclosing it or using it unlawfully. Each participant must safeguard the information they obtain and respect the rights of others.
Itzuna has no practical control over a copy that another person has saved or sent outside the service and cannot guarantee its deletion on other people’s devices. This does not limit its obligations regarding the data it processes, the security of the app and the action legally required in response to an incident. You can report misuse to privacidad@itzuna.com.
Access to provide the service
The owner and authorised people may access the data needed to provide support, maintain security, resolve incidents, handle rights requests or meet obligations. There is no general monitoring of family life or of whether tasks have actually been done properly.
5. Minors
The Itzuna Terms allow people aged 14 and over to create their own account and to create and manage groups for ordinary use of the service. Not every group has to be managed by an adult. Children under 14 may take part by invitation in accordance with section 06.4 of the Terms; that participation is not the same as creating their own account or, on its own, entering into a separate contract.
A minor’s information may come from the minor, from whoever creates or manages their profile and from the activity of the group’s authorised people. Only the necessary data and age-appropriate rules should be used, avoiding exposure of the minor’s private life. Anyone who provides data or grants access must be entitled to do so; managing the group does not give them legal representation over the others.
For a person’s own account, the data needed to provide the contracted service are processed on the contractual basis described in section 3. Participation by invitation of someone who does not contract is based on the legitimate interest explained there, with particular attention to the rights, expectations and protection of the minor. It is not automatically covered by another person’s contract or by a consent checkbox. If, in a specific case, the minor’s rights prevail, that basis does not allow the processing to continue on the same terms.
Where a specific processing requires consent, in Spain it may be given from the age of 14, except in the cases where the law requires the assistance of those holding parental authority or guardianship. Under the age of 14, processing based on consent will require the consent of whoever holds parental authority or guardianship and its verification as legally required. If other mandatory age or representation rules apply, they will be respected. This does not make consent the basis for all the processing described in this policy.
If an act or processing requires the authorisation or involvement of a legal representative, this must be resolved before carrying it out. Receiving an invitation, reading this policy, accepting the Terms or creating a group does not, on its own, prove that authorisation. Itzuna’s own obligations are not transferred to the group administrator.
The minor and those entitled to represent them can exercise their rights. If you believe that a participation, content or access is harming a minor, contact privacidad@itzuna.com.
6. Providers, recipients and international transfers
We use providers for the functions the service needs. When they act on our behalf, they must process the data in accordance with the corresponding data processing agreement and their security obligations.
| Provider or recipient | Function and related data |
|---|---|
| Supabase | Database, authentication, file storage and server functions. Processes the necessary account and group data and technical logs. The main region configured for the database, authentication and files is Frankfurt, European Union. |
| Cloudflare | Hosting, delivery and security of the website; storage of beta requests in D1; bot protection with Turnstile and metrics with Web Analytics. May receive connection and browser data for these functions. |
| Brevo | Delivery of access and confirmation emails and contact management for the necessary beta communications. Receives the addresses and the necessary content of those emails and generates delivery data. |
| Expo and Google Firebase Cloud Messaging | Delivery of remote notifications on the platforms where they are enabled, currently Android. They receive the delivery identifiers and the content of the notices. |
| Google, if you choose to sign in with Google | Identification through its sign-in service. Google also processes data under its own policy as the provider of that account. |
| App stores you use | Distribution and management of their own services under their terms and policies. If payments are added, the corresponding processing will be explained before purchase. |
Turnstile processes signals such as the IP address and technical characteristics of the connection and the browser to detect abuse. Cloudflare acts on our behalf when protecting the site and also describes its own processing to improve its detection capability, in accordance with its Turnstile Privacy Policy.
The fact that the main base is in the European Union does not mean that all processing is limited to it. Global infrastructure, support and sub-processors, and in particular notification delivery, may involve processing outside the European Economic Area, including the United States.
For transfers that require them, the safeguards provided for in the GDPR apply: adequacy decisions, including the EU–US framework where the entity and the processing are covered, or standard contractual clauses and the corresponding supplementary measures. You can request information about the applicable safeguards and a copy of or reference to them by writing to the privacy email address, subject to the limitations needed to protect confidential information.
We may also share the strictly necessary information with authorities, courts or advisers where there is an obligation or a legitimate need related to a claim. We do not sell your data or use it for personalised advertising.
7. Notifications, storage and website metrics
Notifications
Notices may contain the name of a person or group and references to a task, reward or activity. In a remote notification, that content passes through the delivery providers. It may also appear on the device’s lock screen depending on its settings.
You can turn off categories from the app and block notifications or their previews from the device’s system settings. Not using notifications does not delete the information that remains within the group. Local reminders are scheduled on the device itself; remote notifications use the corresponding delivery service.
Necessary storage and analytics
The app uses local storage to keep the data, settings and sessions needed for its features. Access and security processes may require technical session or verification technologies.
The website uses Cloudflare Web Analytics to obtain limited visit and performance metrics. According to the provider’s documentation, this tool does not use cookies or local storage for those metrics and does not individually identify visitors. This description refers to that tool, not to a complete absence of technical data in all connection or security services.
We record operational events for requests, confirmation, activation and download without adding the email address or tokens to the analytics event. Checking a download may, however, use the receipt linked to the request, described in section 2.
We do not use these metrics for behavioural advertising. If non-essential technologies requiring consent are added, you will be informed and asked before they are turned on.
8. How long we keep data
The following are the ordinary criteria. A rights request, a legal obligation or a specific claim may require different action, which will be limited to what is necessary.
| Data | Ordinary retention |
|---|---|
| Own account | For as long as you keep the account, until it is deleted, with the limited exceptions indicated for records and claims. |
| Profile, tasks and group activity | For as long as the group exists and they are needed for its operation and history. Removing or unlinking a profile does not automatically delete its activity. Rights can be exercised earlier. |
| Photo and text of a task proof | 30 days from when they are provided. Their content is then deleted by the automatic clean-up; a mark that the task was completed with proof may remain. |
| Invitations | Usable for 14 days, unless accepted or revoked earlier. Expired records are deleted by the daily clean-up, with a technical margin of one day after expiry. |
| Shared packs | One year from creation, unless withdrawn or erased earlier where appropriate. Their life cycle is independent of the deletion of the source group. |
| Unlinked technical guest sessions | Purged when they have no links or dependencies with groups and 30 days have passed without use. A guest who is still linked to a group is not deleted for mere inactivity. |
| Beta request from someone who does not join | Up to six months from the request or until the end of the beta, whichever comes first. Resending a confirmation does not restart that period. |
| Unconfirmed beta request | The confirmation link expires after 48 hours; clean-up of the request is scheduled 30 days after that expiry, without exceeding the general limit above. |
| Request from someone who joins the beta | Only for as long as their data are needed to manage access and participation. Unsubscribing the request or its communications does not, on its own, delete an app account already in use. |
| Technical beta access receipt | At most seven days from its generation, or until its final check is completed or the download is validated, if that happens earlier. |
| Record of acceptance of the Terms, including declarations of legal age linked to earlier acceptances where they exist | During the relationship and, when it ends, five years as the ordinary period for keeping minimum proof of the contractual relationship. |
| Historical declarations of who created a group, where collected under earlier versions | For as long as the corresponding relationship lasts; after it ends through deletion of the account or the group, five years as the ordinary minimum proof period. The update does not restart this period or change the meaning of the declaration. |
| Status of a suspension | While it is in force and needs to be applied, subject to review; once lifted, the minimum record is kept for twelve months. |
| Incident details and attachments | While they are being resolved; unnecessary items are deleted and, ordinarily, no later than 90 days after closure. The minimum record of the resolution is kept for up to twelve months. |
Technical authentication, delivery, error and security logs are kept for the operational window needed to provide and diagnose the service, according to the configuration applicable to the provider. If a log needs to be added to an incident, it is then kept only to the extent and for the period needed for that case. They are not used as a permanent archive of family activity.
Technical backups have their own rotation and recovery cycle. Deleting active data does not mean that it disappears at that instant from all of the provider’s backups or technical logs. These copies have restricted access and remain only during their recovery window or for the necessary retention; they are not used to reactivate deleted data in ordinary use. If a backup is restored, erasures already processed must be respected.
Clean-ups run periodically, usually daily. If a deletion fails, it is retried and the incident is handled. When a beta request is unsubscribed, a deletion failure at a provider may require temporarily keeping the minimum information needed to complete that deletion. A technical failure does not authorise keeping data longer than necessary or breaching the legal deadlines for handling rights.
Where a legal obligation, claim or proceeding requires data to be kept for longer, only what is strictly necessary will be separated or blocked, with limited access and for the applicable period. The entire content of a group is not kept for that reason. The five years of contractual proof and the incident periods are retention criteria; they do not mean that any data must always be kept for those periods.
9. What happens when you leave, remove a profile or delete
Leaving a group or removing a profile: the corresponding access link is removed. The profile may remain archived with its name, history and balance. That information may still identify you even though it is no longer associated with your account. It is kept for the continuity of shared activity where justified, without excluding a request for erasure or an objection.
Restoring a profile: allows its history and balance to be used again. For an account to access it, a new invitation is needed; the previous link is not automatically restored.
Deleting your account: removes access and the link to groups. If you own groups, they are deleted for all of their members. Their personal accounts remain. In other people’s groups, the profile and activity may be kept as described above; the proof you provided is no longer linked to your account and remains subject to the ordinary 30-day period.
Deleting a group: deletes its active information and requests the deletion of its files. Files are normally deleted when the operation is processed; if this fails, it is retried by the periodic clean-up. There is no recycle bin or undo feature for deleting a group.
Packs and copies: a shared pack is not automatically deleted with the source group. A copy downloaded by another person does not disappear from their device as a result of that operation either.
File links: temporary links issued for images and those included in exports may be valid for up to seven days from issue. Revoking access or suspending an account or group does not guarantee that a link issued earlier will stop working immediately. It may remain usable until it expires, unless the file is deleted or the link becomes unavailable earlier. Avoid sharing those links; downloading them does not extend how long the file is kept in Itzuna.
A suspension is not the same as a deletion order and does not stop the ordinary expiry of data. You can exercise your rights during it through the privacy email address.
10. Your rights and how to exercise them
You can request access to your data, its rectification, erasure or restriction, and object to processing based on legitimate interest. You can request portability in the cases provided by law, especially for data you have provided and that we process by automated means based on consent or contract. If processing depends on your consent, you can withdraw it.
Write to privacidad@itzuna.com. Say what you need and give the minimum data that allows us to locate your account or participation. If it concerns an unlinked profile, it helps to give the group and the name the profile had. Do not send passwords or a copy of your identity document on your own initiative.
We will verify identity or representation proportionately. We will only ask for additional information when it is necessary to resolve reasonable doubts or locate the data. We do not routinely require an identity document.
We will generally reply within one month of receipt. If the complexity or number of requests makes it necessary, this period may be extended by up to two further months, and you will be informed of this and the reasons within the first month. Exercising your rights is free of charge, subject to the legal exceptions for manifestly unfounded or excessive requests.
Rights do not give indiscriminate access to other members’ data, nor do they require the deletion of information that must legitimately be kept. If a request cannot be met in full or in part, the reasons and the ways to complain will be explained.
You can lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos) or with the competent supervisory authority under the GDPR. You do not have to complain to Itzuna first.
11. Tools available in the app
Depending on your role and the available features, you can edit your profile data, leave a group, manage notifications, delete your account or export information from the account and privacy options.
“My data” is also available to participants without an email address. It includes the data linked to your account and current profiles, activity, points, rewards and other available records of your own, as well as your contractual records where they exist. It may include links to files, with the exact expiry date shown in the export.
It also includes the proof you provided to groups you have since left, as long as it is still kept and associated with you as its author. However, a profile and its history that are no longer linked to your account may not be located automatically. You can request that information by email, giving the group and the name of the profile.
The full copy of your own groups and the export of personal data serve different purposes. A copy of a group may include information about its other members and must be safeguarded and used with respect for their rights.
The limitations of a tool, losing a session or a suspension do not remove your rights. You can use the privacy email address without having to create a new account.
12. Automated decisions and security
We do not use points or streaks to make automated decisions with legal or similarly significant effects on people. They are organisational and game calculations within the group. Suspension measures and their review are handled by the owner or authorised people, without prejudice to automatic technical controls against invalid access or abuse.
We apply access controls per account and group, differentiated permissions and technical and organisational measures to protect information. No system can guarantee zero risk. You must protect your devices, sessions, invitations, exports and file links.
You can report a security incident to the same contact email address, providing only the information needed to investigate it.
13. Changes to this policy
We will identify changes with a new version and date. Significant changes will be communicated through appropriate means before new processing is applied, where required.
An update to this policy does not turn processing into consented processing, nor does it replace any specific information or authorisation that may be needed. The version of the privacy notice is independent of the version of the Terms and of each group’s rules.