Skip to content
NARZ
ES
Privacy policy Cookie policy Legal notice Terms of use

Privacy policy

Last updated: 15/11/2026

This Privacy Policy explains which personal data NARZ (hereinafter “NARZ” or the “Application”) processes, why, on what legal basis, for how long and what rights the people who use it (the “User” or “Users”) have. It is provided in compliance with Articles 12 and 13 of Regulation (EU) 2016/679, the General Data Protection Regulation (“GDPR”), and Article 11 of Spanish Organic Law 3/2018 on the Protection of Personal Data and the Guarantee of Digital Rights (“LOPDGDD”). It describes how the current version of NARZ actually works. This English version is a translation; in case of discrepancy, the Spanish version prevails. It does not provide legal advice for any other country.

In a nutshell

  • We keep what you need to organise your studies: your account, your subjects, your assignments and exams and your timetable.
  • We do not sell your data, show advertising or use analytics or tracking tools.
  • If you are under 14, your father, mother or guardian must approve your account before you can use it.
  • Your family only sees your week if you give them your code, and you can remove their access (except the person who approved your account if you are under 14).
  • NARZ Boi answers with ready-made texts inside NARZ: it does not send your questions to any artificial intelligence service.
  • You can download your data and delete your account in Settings, and write to us for any other request.
Basic data protection information
Controller[pending: full name] · [pending: email]
Data processedAccount data (name, email address, account type, students’ date of birth and, if provided, phone number), academic content, family account data and technical security data (section 3).
PurposesProviding the academic planner and its features; managing family accounts; checking the age and family approval of students under 14; recovering access; protecting the security of the service; handling requests and rights.
Legal basesDepending on the purpose: performance of the Terms of Use (Art. 6(1)(b) GDPR); consent of the holder of parental authority or guardianship for students under 14 (Arts. 6(1)(a) and 8 GDPR and Art. 7 LOPDGDD); compliance with legal obligations (Art. 6(1)(c) GDPR); legitimate interest in the security of the service (Art. 6(1)(f) GDPR). Details in section 4.
RecipientsData is not disclosed to third parties unless required by law. The database provider processes data on behalf of the Controller, and so will the application hosting provider once NARZ is published (section 10). Within NARZ, the linked family member sees the information described in section 8.
International transfersMay occur if a provider or its sub-processors access the data from outside the European Economic Area, with the safeguards of Chapter V GDPR (section 11).
RetentionWhile the account exists. After deletion, backups and security logs may remain for limited periods (section 12).
RightsAccess, rectification, erasure, objection, restriction, portability and withdrawal of consent, and a complaint to the Spanish Data Protection Agency (section 13).
Contact[pending: email]

Contents

  1. Identity and contact details of the Controller
  2. Definitions
  3. Personal data we process
  4. Purposes, legal bases and retention
  5. Mandatory and optional data
  6. Students who are minors
  7. NARZ Boi and artificial intelligence
  8. Family accounts
  9. Access by the administrator
  10. Recipients and processors
  11. International transfers
  12. Retention and deletion
  13. Your rights and how to exercise them
  14. Automated decisions and profiling
  15. Security and personal data breaches
  16. User obligations
  17. Changes to this Policy

1. Identity and contact details of the Controller

  • Data controller: [pending: full name]
  • Email for any data protection matter: [pending: email]

NARZ is a free service, with no advertising or paid options. The Controller has not appointed a data protection officer because, given the current nature and scale of the processing, none of the cases in Article 37 GDPR or Article 34 LOPDGDD applies. If that changes, one will be appointed and stated in this Policy.

2. Definitions

The terms in this Policy have the meaning given in Article 4 GDPR. In particular:

  • Personal data: any information relating to an identified or identifiable natural person.
  • Processing: any operation on personal data, such as collecting, storing, consulting, disclosing or erasing it.
  • Controller: whoever decides why and how data is processed.
  • Processor: whoever processes data on behalf of the Controller, such as a hosting provider.
  • Student: a User with a student account.
  • Family member: a User with a family account, whether or not linked to one or more students.

3. Personal data we process

Data is provided by the User or generated when using NARZ. NARZ does not obtain data from other sources or buy it from third parties.

3.1. Account data

  • Name and email address. The email identifies the account for signing in.
  • Phone number, only if the User chooses to provide it. NARZ does not currently send text messages, so it is not used to send messages.
  • Password, stored only after being transformed with a key derivation function (scrypt). Nobody, including the Controller, can work out the original password from what is stored.
  • Account type (student, family or administration), preferred language, status (active or disabled) and sign-up date.
  • Date of birth, for student accounts only, to check whether family approval is needed.
  • The student’s family code and its expiry date.

3.2. Academic content

  • Subjects: name, colour and, if entered, the teacher’s name.
  • Assignments and exams: title, subject, type, date and time, priority, status and free-text notes. NARZ does not record grades.
  • Study sessions: assignments created from an exam to prepare for it.
  • Timetable: day of the week, start and end time, subject and room.
  • Saved reviews from the former AI Review feature, currently disabled (section 7), if the User generated any.

3.3. Family account data

  • The link between the family member and the student, and the date it was created.
  • Family approval for students under 14: which account gave it, on what date and at what time, and which version of the text was accepted.
  • Family member’s diary: date, mood (one of four options) and text. The diary contains information about the student written by the family member.

3.4. Technical and security data

  • Open sessions: a summary of the browser and operating system (for example, “Chrome · Windows”), the start date and the date of last use. The session identifier is stored only as an encrypted code (HMAC); neither the full browser string nor the IP address is stored.
  • Password recovery codes: stored as an encrypted code (HMAC), with their channel, number of attempts and expiry.
  • Audit log: records sensitive operations (account creation and deletion, password changes, links, family approvals, data exports and administrator actions) with the date, the numeric identifier of the acting account and of the affected one, the type of operation, its result and a request identifier. It does not store names, emails, passwords, codes or texts. Although it only contains numbers, it is personal data because it refers to specific accounts.
  • IP address: the application uses it in the server’s memory, for up to one hour, to limit attempts at signing in, signing up, password recovery, linking and questions to NARZ Boi. The application does not store it in the database. The hosting provider may record connection data, such as the IP address, in its own technical logs (section 10).
  • Error logs: when an error occurs, the server records the requested path, the method and a request identifier so it can be fixed.
  • Preferences stored in your browser: described in the Cookie Policy.

3.5. Special categories of data

NARZ does not ask for data in the special categories of Article 9 GDPR (for example, health, beliefs, religion or ethnic origin) or for location data. Please do not write this kind of information in free-text fields such as notes or the diary. The diary’s mood is a general rating and must not be used to record health information.

4. Purposes, legal bases and retention

Each processing operation has a specific purpose and its own legal basis (Art. 5(1)(b) GDPR):

PurposeDataLegal basisRetention
Creating the account, signing in and managing itAccount data, sessionsPerformance of the Terms of Use (Art. 6(1)(b) GDPR). For students under 14, also approval by the holder of parental authority or guardianship (section 6)While the account exists
Academic planner: subjects, assignments, exams, study sessions, calendar and timetableAcademic contentPerformance of the Terms of Use (Art. 6(1)(b) GDPR)Until the User deletes it or deletes the account
Reminders on the device, if the User turns them onUpcoming or overdue assignments and examsPerformance of the Terms of Use (Art. 6(1)(b) GDPR); they require the browser’s notification permission, which the User can withdrawNothing additional is stored on the server
Family accounts: linking, viewing the week and diaryLink, the student’s academic content, diaryPerformance of the Terms of Use at the request of the student, who decides to share their code (Art. 6(1)(b) GDPR); for students under 14, consent of the holder of parental authority or guardianship (Arts. 6(1)(a) and 8 GDPR and Art. 7 LOPDGDD)While the link lasts; the diary, until its author deletes it or their account or the student’s account is deleted
Checking age, requesting family approval and being able to prove itDate of birth, approval recordCompliance with legal obligations (Art. 6(1)(c) GDPR, in connection with Arts. 7(1) and 8(2) GDPR and Art. 7 LOPDGDD)While the account exists; the audit log record, as described in section 12
Recovering access to the accountEmail address, recovery codePerformance of the Terms of Use (Art. 6(1)(b) GDPR)The code is valid for 15 minutes and a single use
Answering questions asked to NARZ BoiQuestion text, language, account type and section of the applicationPerformance of the Terms of Use (Art. 6(1)(b) GDPR); for visitors without an account, legitimate interest in answering their query (Art. 6(1)(f) GDPR)The question is not stored
Security of the service, abuse prevention and logging of sensitive operationsIP address (in memory), sessions, audit log, error logsLegitimate interest in protecting the service and its Users (Art. 6(1)(f) and Recital 49 GDPR)IP address: up to one hour. Everything else: section 12
Support, maintenance and management of NARZ’s public contentWhatever is needed in each case (section 9)Performance of the Terms of Use (Art. 6(1)(b) GDPR) and legitimate interest in maintaining the service (Art. 6(1)(f) GDPR)As long as needed for each action
Backups to restore the service after incidentsDatabase contentsLegitimate interest in the availability and integrity of the service (Art. 6(1)(f) GDPR, in connection with Art. 32 GDPR)According to the backup cycle (section 12)
Handling requests and the exercise of rights, and complying with legal obligationsWhatever is provided in the requestCompliance with legal obligations (Art. 6(1)(c) GDPR)As long as needed to handle them and prove it

Processing based on legitimate interest is limited to what is needed for the security and continuity of the service and is not used for other purposes. You can object to it on grounds relating to your particular situation (section 13).

5. Mandatory and optional data

To create an account, the name, email address, password and account type are mandatory, as is the date of birth for student accounts. Without them the service cannot be provided. Other data (phone number, teacher, notes, room and other fields not marked as mandatory) is optional.

6. Students who are minors

If you are under 14

  • You can create your account, but you will not be able to use the planner until your father, mother or guardian approves it.
  • To do this, give them your family code. That person creates a family account, adds you with the code and accepts the approval text.
  • While you wait, you can only use Settings, your family code and NARZ Boi.
  • The person who approved your account can withdraw the approval. Your account then goes back to waiting, but your data is not deleted.

6.1. Students under 14

Article 7 LOPDGDD provides that processing the data of a minor under 14 based on consent is only lawful with the consent of the holder of parental authority or guardianship. NARZ applies this requirement to the whole student account, as follows:

  1. The student enters their date of birth when signing up or, if missing, at their next visit. NARZ calculates the age on every request.
  2. If the student is under 14, the Application limits use to Settings (including downloading their data and deleting the account), their family code and NARZ Boi, until approval is recorded.
  3. An adult creates a family account, links the student with their code and expressly ticks the box of the approval text, in which they declare that they are the student’s father, mother or legal guardian. NARZ stores which account gave the approval, on what date and at what time and which version of the text was accepted.
  4. The approval can be withdrawn at any time by whoever gave it. It is also withdrawn if that person unlinks or deletes their account. In that case, the minor’s account goes back to waiting and their data is not deleted. The minor cannot remove the access of the person who approved their account.
  5. When the student turns 14, approval is no longer needed and the limitation ends.

Limits of the check. Linking an account with the student’s code shows that the student shared that code, not that the person approving holds parental authority or guardianship. NARZ does not ask for identity documents or carry out identity verification: it relies on the express declaration of the person approving, who is responsible for its truthfulness. If you learn that an approval was given by someone without that status, or that a minor under 14 is using NARZ without approval, you can report it to [pending: email]. The Controller will review it and, where appropriate, put the account on hold or delete it.

Correcting the date of birth. While approval is pending, the student can correct their date of birth once only, within 24 hours of entering it. After that, only the administrator can change it, at the request of the data subject or their family and after confirming the error. This prevents the approval from being bypassed by changing the date.

Exercising rights. The rights of minors under 14 can be exercised by their parents or guardians, without prejudice to the minor also being able to contact the Controller.

6.2. Students aged 14 to 17

From the age of 14, students can consent to the processing of their data themselves (Art. 7(1) LOPDGDD) and do not need family approval to use NARZ. This does not mean they have full capacity for any contract: the use of NARZ, which is free and part of a student’s everyday life, is governed by the Terms of Use. Their family can only see their information if the student gives them their code, and the student can remove that access at any time.

7. NARZ Boi and artificial intelligence

7.1. NARZ Boi

NARZ Boi is NARZ’s help assistant. It runs on NARZ’s own server with a set of answers prepared in advance: it identifies the topic of the question using rules and returns the corresponding answer. It is not a generative artificial intelligence system and it does not send questions to any external service.

  • To answer, it uses the question text, the language, the account type and the section of the application the question is asked from. It does not read subjects, assignments or any other account data.
  • The question text is not stored. The server only records the recognised topic, without the text, to help improve the answers.
  • A per-minute question limit applies to prevent abuse.

Do not write personal data in your questions, especially about other people.

7.2. AI Review

The AI Review feature, which generated study material using Google’s Gemini service, is disabled. While it remains so, NARZ does not offer that feature and does not send any content to Google or any other artificial intelligence provider. Reviews generated before are kept in the account until the User deletes it.

7.3. Future features

If a feature using artificial intelligence or external services is added in the future, before it is turned on this Policy and the Terms of Use will be updated, its legal basis, age conditions and providers involved will be reviewed and, where necessary, the corresponding consent will be requested.

8. Family accounts

  • Linking. The student gets an 8-character code in their account, valid for a limited time (currently 7 days), which they can renew whenever they want; once renewed, the previous one stops working. The family member enters it in their family account to link up.
  • What the family member sees. The student’s name, how many assignments are pending and overdue and, week by week, their classes (subject, day, times and room) and their assignments and exams (title, subject, type, date and time, priority and status). If the student is under 14, they only see this after giving approval.
  • Assignment notes. The free-text notes the student writes in their assignments are private: NARZ does not send them to the family account.
  • What they cannot do. The family member cannot create, modify or delete the student’s data. They do not see the student’s date of birth, email address or open sessions.
  • Diary. The family member can write a diary about each linked student. Only its author sees it: neither the student nor the administrator can read it in the Application. If the link ends, the entries are no longer shown and are kept until their author deletes them or their account or the student’s account is deleted. The student can exercise their rights over the information concerning them (section 13); each request will be assessed taking the author’s rights into account as well.
  • Removing access. The student can remove the access of any family member in Settings, except, if they are under 14, the person who approved their account. The family member can unlink at any time.

9. Access by the administrator

NARZ has administration accounts, managed by the Controller, to provide support and maintain the service. From them it is possible to:

  • view and correct account data (name, email, phone, type, status, language and date of birth), disable accounts, delete them and assign them a new password;
  • view, create, modify and delete subjects, assignments (with their notes) and timetable classes;
  • view and close an account’s open sessions;
  • edit and publish NARZ’s public content, such as the home page texts. Which administration account made each change is recorded.

The administrator cannot see passwords, the text of diaries or the content of saved reviews; they only see how many exist. Access to an account’s data is limited to what is needed to resolve incidents, handle the data subject’s requests, comply with legal obligations or prevent misuse, and the administrator’s actions are recorded in the audit log.

10. Recipients and processors

Data is not disclosed to third parties for commercial purposes. The following providers process or will process data on behalf of the Controller, as processors and under their data processing terms (Art. 28 GDPR):

ProviderServiceDataLocation
Aiven Oy (Finland)Managed MySQL databaseAll data stored by NARZ[pending: server provider and country]
Render Services, Inc. (United States)Hosting of the web application server. Planned: it will process data once NARZ is published on this providerData passing through the application and the server’s technical logsServer in the Frankfurt region (Germany)

Services not in use. The email sending provider is pending configuration, so NARZ does not send emails yet. NARZ does not use any text message provider, Google sign-in or Google Gemini either. If any of them is turned on, it will be added to this table, with the data it receives and its safeguards, before it starts being used.

Other recipients. Data may be disclosed to courts, the Public Prosecutor’s Office, law enforcement and other authorities where there is a legal obligation. Within NARZ, the linked family member accesses the information described in section 8.

Fonts, icons, images and code libraries are served from NARZ’s own server. Browsing NARZ does not connect to third-party services.

11. International transfers

A server being located in the European Union does not by itself rule out international transfers: they may occur if a provider or its sub-processors access the data from outside the European Economic Area, for example to provide technical support. This will be the case of Render Services, Inc., based in the United States, once it is used for hosting, and may be the case of the sub-processors of the providers in the table above.

Such transfers only take place with the Chapter V GDPR safeguards offered by the providers in their data processing terms: an adequacy decision, such as Commission Implementing Decision (EU) 2023/1795 on the EU-U.S. Data Privacy Framework where the recipient is certified (Art. 45 GDPR), or the standard contractual clauses adopted by the European Commission (Art. 46(2)(c) GDPR). You can ask for information about these safeguards at [pending: email].

12. Retention and deletion

  • Active data. Account data and academic content are kept while the account exists. NARZ does not automatically delete unused accounts; you can delete yours or ask for it at any time.
  • Items you delete. A subject, assignment, class or diary entry that you delete is removed from the database at that moment.
  • Account deletion. When deleted in Settings or by the administrator, the account and its associated data are removed from the database at that moment: subjects, assignments, timetable, saved reviews, sessions, recovery codes, family links, diary entries written by that account and those a family member had written about it. If it was the account that approved a minor under 14, the minor’s account goes back to waiting.
  • Accounts disabled by the administrator: kept, unusable, until they are reactivated or deleted.
  • Accounts of minors under 14 awaiting approval: kept on hold until approval is given or the account is deleted.
  • Sessions: stop being valid on signing out, when the password is changed or after 14 days without use. Expired ones are removed from the database when a new session is started with the same account or when it is deleted.
  • Recovery codes: valid for 15 minutes and a single use. Their encrypted record is removed when another code is requested after one day or when the account is deleted.
  • Family code: stops working when it expires (currently after 7 days) or is renewed.
  • IP address in the server’s memory: one hour at most.
  • Audit log: also kept after the account is deleted, with numeric identifiers only, for as long as needed to investigate security incidents and prove compliance, and never beyond the limitation periods of the liabilities it may serve.
  • Server technical and error logs: kept for the limited period set by the hosting provider for its service.
  • Backups: the database service makes automatic backups and the Controller keeps encrypted backups outside NARZ’s servers. Deleted data may remain in those backups until they are replaced or deleted according to their cycle. Backups are only used to restore the service after an incident; if one had to be restored, deletions made since the date of the backup would be applied again.

Where the law requires data to be kept after rectification or erasure, it will be kept blocked in accordance with Article 32 LOPDGDD: only available to judges and courts, the Public Prosecutor’s Office or the competent public authorities to deal with possible liabilities arising from the processing, during their limitation period, and deleted afterwards.

13. Your rights and how to exercise them

Under Articles 15 to 22 GDPR, you can exercise the following rights free of charge:

  • Access (Art. 15): find out whether we process your data and obtain a copy and information about the processing.
  • Rectification (Art. 16): correct inaccurate data or complete incomplete data.
  • Erasure (Art. 17): ask for your data to be deleted when, among other cases, it is no longer needed.
  • Restriction (Art. 18): ask for it to be kept but not used, in the cases provided for by law.
  • Portability (Art. 20): receive the data you have provided to us, processed on the basis of consent or the performance of the Terms, in a structured, commonly used and machine-readable format, and have it transmitted to another controller where technically feasible.
  • Objection (Art. 21): object to processing based on legitimate interest, on grounds relating to your particular situation.
  • Withdrawal of consent (Art. 7(3)), at any time and without affecting the lawfulness of earlier processing.

In the Application

  • Settings: change your name, phone number, language and password; view and close your open sessions; view and remove your family members’ access; download your data; delete your account.
  • Family: unlink from a student and give or withdraw approval for a minor under 14.
  • Download my data generates a JSON file with your profile, subjects, assignments and timetable and, for family accounts, your diary. It makes access and portability easier, but does not replace those rights: if you need a complete copy or more information, you can request it by email.
  • To change your email address, write to us.

By request

For any right, write to [pending: email], preferably from your account’s email address, stating which right you want to exercise. Requests are handled personally by the Controller; they are not resolved automatically. If there are reasonable doubts about the identity of the person making the request, the minimum additional information needed to confirm it may be requested (Art. 12(6) GDPR).

A reply will be given within one month of receiving the request. That period may be extended by two further months if the request is complex or there are many, and you will be informed of this within the first month (Art. 12(3) GDPR). If you believe your rights have not been respected, you can lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos, C/ Jorge Juan, 6, 28001 Madrid · www.aepd.es).

14. Automated decisions and profiling

NARZ does not take decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR), and does not build profiles for commercial purposes. The Application’s automatic operations, such as sorting assignments, showing reminders or choosing NARZ Boi’s answer, are part of the service. Limiting the accounts of minors under 14 without approval applies a legal requirement based on the date of birth entered; if you believe it has been applied by mistake, you can ask for it to be reviewed at [pending: email].

15. Security and personal data breaches

In accordance with Article 32 GDPR, the Controller applies technical and organisational measures appropriate to the risk, including:

  • An encrypted connection (HTTPS) between the browser and NARZ and, in production, the HSTS header, which tells the browser to always use HTTPS. The connection to the database is also encrypted (TLS) and the server’s certificate is verified.
  • Passwords stored with the scrypt function, and session tokens and recovery codes stored as HMAC-SHA256 codes.
  • Sessions checked on the server on every request, invalidated on signing out and, when the password is changed, on other devices.
  • A signed session cookie with the HttpOnly and SameSite=Lax attributes and, in production, Secure.
  • Protection against request forgery (CSRF) for all operations that modify data, and a content security policy (CSP) that only allows resources from NARZ’s own server.
  • Attempt limits on signing in, signing up, password recovery, family linking and NARZ Boi.
  • Access control on every query: each account only accesses its own data, family members only that of linked students, and the administration panel only active administration accounts.
  • An audit log the application can only add to: the database prevents its entries from being modified and the user the application runs as has no permission to delete them.
  • Separate development and production environments, with different databases and credentials, and checks that prevent the development environment from connecting to the real database.
  • Service keys kept only on the server, and encrypted backups.

No measure removes risk entirely. If you find a vulnerability, report it confidentially to [pending: email].

Personal data breaches

Not every technical incident affects personal data. When a personal data breach occurs (an unauthorised destruction, loss, alteration, disclosure or access), the Controller will document it with its effects and the measures taken (Art. 33(5) GDPR) and assess its risk. Unless it is unlikely to result in a risk to people’s rights and freedoms, it will notify the Spanish Data Protection Agency without undue delay and, where feasible, within 72 hours of becoming aware of it (Art. 33(1) GDPR). When it is likely to result in a high risk, it will also inform the people affected without undue delay, except in the cases of Article 34(3) GDPR.

16. User obligations

  • Provide true data and keep it up to date, especially the date of birth.
  • Do not enter other people’s personal data beyond what is needed to organise academic activity (for example, a teacher’s name). Anyone who does so must be entitled to.
  • Keep your password confidential and sign out on shared devices.

17. Changes to this Policy

This Policy may be updated because of changes to NARZ or to the law. The date of the last update appears at the top. Minor wording changes will be published directly. Significant changes, such as new purposes, new providers or new processing operations, will be announced before they apply by appropriate means, such as a notice in the Application, and, if they require consent, it will be requested before they apply.

© 2026 NARZ Privacy policy Cookie policy Legal notice Terms of use