Privacy Information for the ARN MCP Summary Version

Version 2026-11-15. This notice describes the limited ARN MCP 1.0.5 search and applies when that version is activated. The candidate covers 175 summaries: the three existing approved 1.0.4 entries and 172 additional hash-bound, individually reviewed versions. Until activation, only the entries active at that time are searchable. Search uses a locally approved index, not ARN’s entire database; user searches do not fetch raw HTML or PDF files.

Who is responsible, and how can you contact us?

Kim Hawaleska, Qysley, is the data controller for Qysley’s processing of personal data. For data protection matters and data subject rights, contact arn-privacy@qysley.se . For support, contact arn-support@qysley.se . You do not need an account to submit a data subject rights request.

Data, sources and purposes

When 1.0.5 is activated, the service searches the three preserved entries and up to 172 additional approved versions. Search uses only the local reviewed index; search terms are not sent to ARN or an external search engine. No raw HTML or PDF is fetched during search. The additional versions are not searchable before activation.

Approved summaries contain the case reference, date of decision, legal issue, necessary facts, assessment and outcome. Names, private contact details and unnecessary individual details are excluded. Combinations of information may nevertheless indirectly identify individuals. We therefore do not describe the summaries as anonymous. Missing information is not invented.

For the three preserved entries and the 172 exact versions within the conditional 1.0.5 decision, Qysley has documented Article 6(1)(f) processing for the limited consumer-information purpose. Safeguards include data minimisation, relevant searches, at most 20 relevance-ranked results per response, source references and the unchanged per-call quota. The additions become searchable only after separately approved deployment gates. The decision does not cover other or changed versions.

When the MCP service is used, a user ID, necessary authorisation and quota status, and the most recent user-initiated activity are also processed for the contracted service under Article 6(1)(b). Subscriptions require the plan, amount, subscription and payment references, and status. Limited necessary security processing relies on Article 6(1)(f). Handling data subject rights requests relies on legal obligations under Article 6(1)(c). Account registration and password processing in Qysley Auth constitute separate processing. OAuth authorisation does not constitute general GDPR consent. Do not enter passwords, tokens, identity documents or unnecessary personal data. Necessary account, authorisation and quota processing is required to access the authenticated service. Access cannot be provided without it. However, parties to ARN cases do not need to register or pay to exercise their rights.

Contracts and withdrawal

When a subscription is prepared, we store the account linkage, plan, subscription reference and creation time, together with copies of the terms, privacy information and withdrawal information shown. Once approval has been verified, we also store the contract confirmation and relevant verification times. This forms part of necessary contract administration under Article 6(1)(b). The information is stored in an access-protected database on the self-hosted server; the contract copies are not generally encrypted in that database.

The withdrawal function receives a name, any contact email address and an account or subscription reference. The request is encrypted for the owner to read and assess manually; a submitted email address alone does not establish identity. Contract confirmations can be sent to the account’s verified address even if the browser has been closed.

The delivery ledger contains delivery references, an account-linked queue position, attempt status and times, but not the recipient’s email address or the complete confirmation text. Separate receipts record SMTP acceptance, not receipt in the mailbox. Uncertain delivery outcomes require manual reconciliation without blind resending.

Information for parties to ARN cases

Information in summaries is obtained indirectly from ARN’s published material. For the three 1.0.4 entries and the 172 exact hash versions in 1.0.5, Qysley has made a conditional decision to rely on Article 14(5)(b). The reviewed versions contain no direct contact details, and the visible ARN pages showed no party-specific contact or forwarding route. Individual notice would require additional identification or collection of contact details that are not needed for the search purpose. The exception is limited to the exactly determined group and applies only once this complete notice is publicly available and the rights, objection, rectification and blocking route is operational. It does not cover new, changed, returned or HOLD entries. Qysley does not need a party’s name to search and compare legal issues and does not create a separate party register solely for GDPR compliance. Article 11 does not remove the Article 14 information obligation or the right to have a request considered.

The public nature of ARN decisions is not, by itself, grounds for an exemption. Our search and delivery functions may make material easier to find and copy. Data minimisation, access and approval controls, justified withdrawal from publication, and the ability to object are therefore required. The decision will be reconsidered if risks, contact possibilities, objections or content change. It does not automatically cover new records. The conditions, including public access to this notice without an account and operational rights/blocking handling, must be met before disclosure. This notice describes the processing but does not itself activate the service; operational activation is controlled separately.

Who receives data, and where is it processed?

An authorised operator may review material and data subject rights requests. When the MCP service is used, your chosen client receives tool results and may store or reuse them independently. The client is not automatically a data processor acting for Qysley.

The library returns only entries whose content hash and runtime approval validate and that are not blocked. When 1.0.5 is activated, the limited search covers the three preserved entries and 172 approved additions; returned, blocked and HOLD versions are not disclosed. Until activation, the additions are not searchable.

The service returns only exactly approved, unblocked entries from the local reviewed index. It does not cover ARN’s entire database and has no live or PDF fallback.

ARN’s separate email addresses use Cloudflare and a self-hosted receiver. Emails are stored in encrypted form and read by the owner on Windows. Providers in the delivery chain may process plaintext before local encryption. This is not end-to-end encryption. Replies and contract confirmations are sent through Brevo, which processes email addresses and content. A standard data processing agreement and subprocessor appendix have been identified. Brevo may use international providers subject to contractual transfer safeguards. The owner has confirmed settings for one month of logs and no previews. This does not prove deletion of every provider copy. PayPal acts as an independent data controller for its payment service. Personal Gmail is not used as the regular mailbox for the separate ARN addresses.

Information about contractual arrangements and applicable transfer safeguards can be requested at arn-privacy@qysley.se . Provider information is available from Cloudflare , Brevo and PayPal .

Retention, rectification and blocking

Approved summaries may be retained only while they remain relevant and legally justified. They are reviewed at least annually and when, for example, an objection is received or a source changes. A justified withdrawal stops further exposure through all six data tools. A control log and separate safeguard record are retained for as long as necessary to prevent reactivation during restoration. This is not the same as deleting the text or copies held by clients.

The following retention periods are approved targets and must be checked against actual operations before being described as implemented: free-tier data after 12 months of inactivity, with no more than 30 days for closure; paid access data during the relationship and no more than 30 days afterwards; operational subscription references normally no more than 90 days after the relationship has ended and payment has been settled. Legal retention exceptions are assessed separately. Full support and data subject rights correspondence has a target retention period of 90 days after final handling, including follow-up. A minimal case log has a target retention period of 12 months after closure. For new, separate ARN logs, the targets are seven days for access logs and 14 days for error and journal logs. Interruptions may cause these periods to be exceeded. Backups and copies have category-specific retention criteria. No general backup retention period or completed deletion is claimed here. Webhook deletion must not compromise replay protection. Physical deletion requires a separate assessment. Actual retention arrangements are subject to post-implementation checks.

For checkout attempts where no contract was concluded, the target is no more than 30 days after verified closure or expiry; uncertain PayPal status or a documented preservation ground blocks a deletion proposal. Contract copies and confirmations follow the approved target for operational subscription records: normally no more than 90 days after the relationship has ended and been settled, subject to separately assessed retention exceptions. Delivery status, receipts and copies must be included in documented copy reconciliation. These are targets and manual review requirements, not a claim of completed erasure or enabled automatic deletion.

Your rights

You may request access, rectification, erasure and restriction of processing, subject to the applicable conditions. Data portability applies where its specific requirements are met, not generally to other people’s ARN material. Email arn-privacy@qysley.se and briefly identify the data or case reference that concerns you. Do not send the full case file or a copy of your identity document unless we make a specific, justified request. We do not collect more verification material than necessary or disclose other people’s data.

Objection to processing based on legitimate interests

You may object on grounds relating to your particular situation. We assess whether processing should cease or be restricted while the objection is considered. Continued processing under Article 21 requires applicable compelling legitimate grounds or grounds relating to legal claims. The general usefulness of the service does not automatically justify rejecting an objection. No account or purchase is required.

We respond without undue delay, normally within one month. Any permitted extension requires notice and reasons within the first month. You may lodge a complaint with the Swedish Authority for Privacy Protection (IMY) and pursue applicable legal remedies. The case-summary library does not make automated decisions about you that produce legal or similarly significant effects.