Data Processing Terms
1. Scope and roles
As part of the Terms, these terms govern the processing of the conversation text selected by the User and of the summary requested from it. The User determines their own private task and the submitted content; the Provider handles the content solely to carry out the User's documented instruction, as a data processor. The User's household exemption does not release the Provider from the GDPR obligations that apply to a processor. For its own account-management, contractual, invoicing and other independent operations defined by purpose in the Privacy Notice, the Provider is a data controller. It does not generally reclassify the content operations needed to perform the summarizing as its own data processing. "Content" means: the conversation text uploaded or pasted by the User, the messages processed from it (including the names and messages of other participants), the finished summary and the "Keep" marker. "User" means the natural person using the Service. "Provider" means Varga Fábián György, sole proprietor (registered office: 1148 Budapest, Nagy Lajos király útja 32-34. III/1., e-mail: varga.fabian.gyorgy@gmail.com).
Under the proposed model, we act as a data processor when summarizing the Content and when storing the summary in the User's account. According to points 19-20 of EDPB Opinion 7/2024, a cloud provider can be a processor even alongside the user's household exemption; this is a classification according to the actual operation, not merely a contractual choice. This annex is for the initial private, household use; an institutional or business principal needs different responsibility, legal-basis and contractual terms. [to be finalized by the lawyer: the wording of the roles and the reference to the household exemption] [to be checked: the exact reference to the EDPB opinion]
2. Subject matter, nature, purpose and duration of the processing
- Subject matter and purpose: summarizing the part of the conversation approved by the User and storing, displaying and deleting the result for the User. The Provider does not use the Content for any other purpose.
- Nature: receiving the text, passing it to the AI provider, producing the summary, storing it, displaying it to the User, deleting it.
- Duration: the processing of the raw text in our own system lasts until the task is done; the actual technical copies and the AI provider's separate retention are covered by the sub-processor and deletion rules (see sections 8 and 11). We handle the summary until the expiry shown on the interface, as a rule for 90 days, and on the User's separate extending instruction for at most 1 year; earlier one-by-one deletion or account deletion can be requested. The starting point and exact expiry of the extension are stated identically by the interface and the Privacy Notice. The names of connected groups and the marker of the last processed message do not follow this period: they are kept until the account is deleted (or the platform is disconnected). The retention of own-purpose usage logs and feedback is regulated separately, by purpose; they give no further content-retention permission. [to be finalized by the lawyer: the starting point of the one-year upper limit]
3. Personal data and data subjects
Data: the permitted content may contain participants' names, everyday statements, to-dos, times, places, institutions and links, extending to the necessary children's data. Special-category personal data — including information pointing to health — and criminal-law data are not within the cloud-processing scope permitted in this version; the User must remove them before submitting. When the Provider becomes aware of such content, it applies the restriction under section 4. The group name, if it enters as part of the task, counts as content; logging it separately for cost purposes is a separate purpose. Before submitting, the User declares by ticking a mandatory checkbox that the content contains no health data or other special-category personal data, and no criminal data; the User does not submit a conversation that contains such data. [to be finalized by the lawyer] Data subjects: the participants of the conversation (other parents, teachers, coaches, family members) and third persons mentioned in the conversation, including children. The User's account data is processed under the Privacy Notice, within the Provider's own data processing. [to be finalized by the lawyer: the intake procedure for special-category data and the way of filtering/rejection]
4. The User's instructions
A documented instruction is: processing under the accepted terms and the sub-processor list, submitting the text approved in the preview and starting the summary, and the choice of retention, extension and deletion on the interface. The instruction extends to transfers (also to third countries) to the approved recipients and places of processing. The Provider acts solely within this, except for an operation required by applicable Union or Member State law; it informs the User of the legal requirement in advance, unless the law prohibits this on important grounds of public interest. The Provider immediately informs the User if, in its judgment, an instruction infringes data protection law, and does not carry out the operation concerned until it is lawfully settled. It does not carry out an unlawful instruction. [to be finalized by the lawyer: proof of the instruction on the interface and the suspension procedure]
5. Confidentiality
The Provider treats what it learns about the Content as confidential. Only the Provider and the further processors under section 8 may have access to the Content, to the extent necessary for the processing. The Provider looks at the content of summaries only for troubleshooting or because of a legal obligation. The admin interface does not show the content of summaries. The database is not encrypted at field level, so the Provider has technical access to the summaries stored there. For operational diagnostics there is a limited, read-only access, used with the Provider's permission. [to be checked: the exact scope of the diagnostic access] [to be finalized by the lawyer: how this fact is to be disclosed to the User]
6. Security measures (GDPR Art. 32)
The Provider applies the following measures (as actually in operation):
- The website is available over HTTPS; we store passwords in non-reversible (hash) form.
- The User's access to a summary is tied to login to their own account; no other user and no public link entitles anyone to access. The operator and contributor access needed to do the work is regulated by sections 5 and 8.
- We do not store the raw conversation text and the uploaded file on the server: they are in the server's memory only while the processing lasts.
- The planned retention of the summary is 90 days, and with a "Keep" instruction at most 1 year. The starting point of the one-year upper limit is still to be fixed; the deadline in the active system for one-by-one and account-level deletion, and the final deletion of backup copies, must be set by the completed deletion regime under section 11.
- Database backup: according to the published regime an encrypted backup is made daily (see section 5 of the Privacy Notice); the encrypted file is also synchronized to the Provider's personal OneDrive account, and its key stays with the Provider. Because of the synchronized copy, the recycle bin and versions, the final deletion time of the whole chain is not yet verified. [to be filled in: final deletion time, after measurement — time per copy, starting point, final deletion and restore limit] When a backup is restored, we apply the earlier deletions again.
- Logging: the application's own log lines record only the error type and status code, not conversation text or summaries; the usage log contains only technical data (time, platform, number of units used). [to be checked: the full error trace (traceback) of unhandled errors could in theory contain a fragment of an AI response]
- Abuse protection: request limiting (with a fingerprint of the IP address, for at most 3 days) and bot protection at registration.
- Access: the Provider has access to the server. The server is shared with the Provider's other projects; Chat Digest runs in a separate container. [to be checked: encryption of the server's disk, i.e. whether the live database is unencrypted]
- Hosting: the infrastructure-level measures of Hetzner Online GmbH (physical and electronic access protection, availability), described in Appendix 2 (TOMs, version 1.2, February 17, 2026) of Hetzner's data processing agreement and in the report of TUEV Rheinland i-sec GmbH of February 19, 2026 (data centers in Helsinki, Nuremberg, Falkenstein).
7. Personal data breach
The Provider notifies the User without undue delay after becoming aware of a personal data breach affecting the processed personal data, at the contact address of the account. According to the information available, it states the nature, the categories of data subjects and data, approximate numbers, the contact point, the likely consequences and the measures taken or planned. It provides missing information in phases, also without undue delay. It documents the event and its handling. For a breach affecting its own controller operations, it fulfils its obligations under GDPR Art. 33-34 itself; this does not automatically pass an official notification duty to a User covered by the household exemption. [to be finalized by the lawyer]
8. Further processors (sub-processors)
Before the first content operation, the User gives general written authorization for the further processors determined in the completed list below. The Provider notifies the User by e-mail at least 30 days in advance of an addition or replacement, stating the new party's name, task, location and the way to object. In reply to the notice the User may object within this period. The Provider examines the objection and looks for a suitable alternative; until then it does not hand this User's content to the new party concerned. Failing a solution, the User may terminate the service concerned free of charge, with the prepaid, unperformed part settled. The new party may act only after the authorization and a suitable written contract; the Provider imposes the same data protection obligations and is liable for the further processor's performance under GDPR Art. 28(4). [to be finalized by the lawyer: the 30-day period, the objection procedure]
Further processors that receive the Content:
- Anthropic Ireland, Limited (6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland) — AI processing (Claude API): making the summary. Data received: the whole input (conversation text, including the data of others and of children) and the output. Location: the place of processing is still open; it may also take place in the United States [to be checked: actual place of processing, access from the USA; to be filled in: countries and safeguards]. Contract: Anthropic's data processing terms (Data Processing Addendum, effective 2025-02-24), which are part of its commercial terms (Commercial Terms, effective 2025-06-17): anthropic.com/legal/data-processing-addendum; their sub-processor list: anthropic.com/subprocessors. Clause I.1 of the DPA incorporates SCC Module Two and/or Three; the module that fits the actual role, the country list and the safeguards are still to be verified. Schedule 1 B.3 of the DPA says "None" for special categories: health data is not covered. Section B of Anthropic's public Commercial Terms excludes model training on content sent into the service [to be checked: exact source]; whether the applicable contract version matches the actual product is still to be verified. API data is deleted under the basic rule within 30 days, subject to product, model, safety and legal exceptions — this is not an unconditional 30-day maximum; content flagged as violating the rules may be kept for up to 2 years [to be checked: exact source, the actual retention setting]. [to be finalized by the lawyer: the role discrepancy — clause B.1 of the DPA names the customer as controller, whereas the Provider is a processor here]
- Hetzner Online GmbH (Industriestr. 25, 91710 Gunzenhausen, Germany) — hosting: the server, the database and the server-side backups. Data received: the content of the database (accounts, summaries) and the backups. Location: Germany, European Union (Nuremberg). Contract: the Provider concluded Hetzner's data processing agreement (Article 28 GDPR, version 1.2, February 16, 2026) on October 27, 2026; the TOMs (Appendix 2) and the TUEV Rheinland i-sec GmbH report of February 19, 2026 are Hetzner's documents. [to be checked: whether the agreement fits Hetzner acting as the Provider's further processor]
- Microsoft Ireland Operations Limited (Microsoft OneDrive) [to be checked: company data, registered office] — external storage of the password-encrypted (AES-256) whole database backup (so the Content too) in the Provider's personal OneDrive storage. Data received: the encrypted backup; Microsoft cannot access the content without the key, and does not receive the password. Location: [to be checked: the OneDrive data storage region]. Contract: personal (consumer) Microsoft account; the contractual chain is not verified. [open: a suitable contract or stopping the synchronization] [to be finalized by the lawyer: whether it is a further processor if it stores only an encrypted file without the key]
The Provider's other contributors (e-mail sending, payment, Google sign-in, bot protection) do not receive the Content; they belong to the Provider's own-purpose data processing and are listed in section 3 of the Privacy Notice. Számlázz.hu (it receives invoicing data) and Telegram (operator alerts) are not further processors in the content task, provided no user content reaches them; the content of the Telegram alerts must be proven by a technical inventory [to be checked]. Before the Brevo e-mail sending is switched on, it must be verified that the e-mails contain no summary.
9. Transfer to third countries
The Provider transfers the Content outside the European Economic Area (United States) only with appropriate safeguards. The contracting party of the AI provider is Anthropic Ireland, Limited. [to be checked: the transfer mechanism applied (standard contractual clauses in the DPA) and the actual place of processing] [to be finalized by the lawyer: the legal basis of the transfer]
10. Data subject requests, assistance and risk assessment
- Data subject requests: the Provider receives and records a request concerning the Content confidentially and, after the necessary verification of role, identity and representation, involves the principal User without undue delay. It does not unnecessarily forward a whole conversation, children's data or the requester's contact details to the User. With the means available it helps to identify the data concerned and to carry out the lawful reply, rectification, deletion or restriction. The processor's assistance cannot automatically wait for a month. Requests concerning its own data processing are decided by the Provider itself under GDPR Art. 12. It does not assert automatic GDPR Art. 12-22 obligations against a purely household User; even in this scope of use it provides a contractual complaint and settlement channel, preserving the mandatory legal measures. See also section 7 of the Privacy Notice. [to be finalized by the lawyer]
- Assistance and risk assessment: according to the information available to it and the nature of the processing, the Provider assists a principal controller covered by the GDPR with the security, breach, impact assessment and prior consultation tasks under Art. 32-36. It documents and manages the risks of its own operations and of the product's content processing. From the User's household exemption it does not derive provider immunity from security duties, or the impact assessment that a parent must necessarily prepare. [to be finalized by the lawyer]
11. End of the processing, deletion
At the end of the service the User may choose the return or the deletion of the Content handled; on return, the Provider makes the personal data available to the User in a secure, usable electronic form, and then deletes the copies. It does not promise the return of data that was already deleted earlier because of the stated expiry or a deletion instruction. Deleting the account or a summary is an instruction to delete the corresponding Content. The final deadline for deleting the active system and the accesses, and for the copies in backups and at further processors, is determined by the actually verified deletion regime [to be filled in: final deletion time, after measurement]. Backup copies cannot be restored for ordinary use; on an operational recovery, the earlier deletions must be applied again before access is restored. An exception for the mandatory legal retention of a copy of the Content under Union or Member State law must be tied to a specific law, data scope and time. Independent retention of invoicing documents gives no right to retain the whole conversation. On request the Provider gives a confirmation of the execution. The effects of account deletion and the lawful retention exceptions are also in section 5 of the Privacy Notice. [to be finalized by the lawyer]
12. Audit, evidence and prohibition of own-purpose use
- Audit: the Provider makes available the information necessary to demonstrate compliance under GDPR Art. 28, and allows and facilitates audits by the User or an auditor mandated by the User, including on-site inspection. Prior arrangement, confidentiality and the protection of other customers' data regulate the execution without substantive restriction. They may not rule out the necessary audit or the authority's rights, and may not make the exercise of rights dependent on a disproportionate fee.
- No own-purpose use: the Provider does not use the Content and the summary for advertising, building personal profiles, commercial analysis, or training or developing its own or a third party's model. Except for the permitted further processors needed to perform the task and cases required by applicable law, it does not pass them on; section 4 governs mandatory legal deviation. Section B of Anthropic's public Commercial Terms excludes model training on content sent into the service; whether the applicable contract version matches the actual product is still to be verified. For its own purposes it processes only technical data independent of the Content (usage log: time, platform, number of units used; daily aggregate counts).
13. The User's obligations
The User (a) provides only conversations in which the User is a participant and to which the User has lawful access; (b) uses the Service for private use under section 5 of the Terms; (c) removes special-category and criminal-law data before submitting and declares this with a checkbox at submission; (d) handles the summary with care and checks the recipient's entitlement before passing it on; (e) complies with the applicable platform terms when extracting the conversation. These undertakings do not replace the Provider's own obligations.
14. Amendment, effect, acceptance
The User receives these terms in a retainable electronic form and accepts them before the first content processing. The version and the acceptance can be proven. They are amended under the lawful amendment procedure of the Terms, and for a new further processor section 8 also applies; no retroactive new purpose or general data-use permission arises for earlier content. The terms bind the Provider until the processing of the Content concerned and its copies ends. In case of a discrepancy between the Terms and this annex, this annex governs the processing of the Content. [to be finalized by the lawyer: building data processing terms into a consumer contract]