Recommendation: Enable minimal data sharing by configuring your privacy settings and read the policy to understand how your data is processed.
The policy explains what data you provide as a registrerad user, what data is collected automatically, and how it innefattar usage metrics. It confirms gdpr compliance and outlines lagringstiderna for stored information and the syfte of processing. It describes safeguards that are identiska across regions and how you can submit requests to registrerar changes or deletions. It also notes that backups with dataacronis exist to restore services if needed, under lagstadgade requirements.
To exercise control, you can opt out of non-essential marknadsföringsaktiviteter. The policy states your rights under gdpr, including access, correction, export, and deletion, with clear timelines and processes. The syfte is clearly defined so you know what is necessary and what is optional. You can manage these rights directly in your DeepL account and through the privacy dashboard.
Practical steps: log in, review the privacy dashboard, adjust lagringstiderna, export or delete data, and ensure your registrerad profile reflects your preferences. If you want to move fram with your data rights, use the built-in request forms; each action is supported by UI prompts aligned with gdpr rules and applicable local laws.
Key förmåner include transparent data handling, predictable retention, and a clear path to control. By following the policy, you ensure that your privacy is actively safeguarded and your rights under gdpr are respected and actionable.
What data DeepL collects and why it matters to you
Review your inställningar now to limit what DeepL collects and how long it stays in your account. This choice helps keep the data under your control and reduces exposure across services.
DeepL collects data to deliver accurate translations and protect the service. Your input text is captured in its format, and we record the language pair and tjänsterna you use. We log ip-adresser to route requests, monitor performance, and prevent abuse. If you sign in, we store e-postadresser and other kundens account details. The system also tracks pågående usage and applies your inställningar to tailor results. This shows vilket data DeepL collects and why. All traffic is protected by certifikat and related skyddet controls. Data is kept only as long as it sätts by the preskriptionstiden and is not used for advertising; it is kept uteslutande for service delivery. In enterprise deployments, data may be sammansförs across services with approved partners such as waltec. You can submit invändning and use the återkallelsen of consent if needed. Data may also be removed or anonymized bort upon valid requests.
Why this matters to you: the collected data improves translation quality while respecting privacy. We identify identiska content to detect duplicates and ensure consistency across sessions. Data may be stored in data centers, including washington, to support redundancy and incident response. We ensure uteslutande use for service delivery and do not share with advertisers unless you opt in. If you want to exercise control, you can initiate an invändning or use the återkallelsen to withdraw consent, and we will honor requests within the preskriptionstiden.
To manage data, visit inställningar in your account and adjust which data DeepL records for on-going usage. Turn off data-sharing features you don’t need, and use on-going retention options that fit your needs. For enterprise needs, contracts with providers like waltec define data handling and certifikat usage to ensure skyddet. If you have concerns, contact support to review your options, including data deletion (bort) and invändning rights.
How to opt out of data collection in special cases
Enable the Special cases opt-out in Privacy settings now. This stops automatiskt data collection for invändningar tied to a specific syfte and reduces exposure of ip-adresserna, e-postadresser, and information across platser and session.
After activation, verify on all devices to ensure the change applies consistently. If invändning persists in logs or summaries, review the settings for behandlingenvid and revoke unnecessary access to data sources. This approach minimizes risker while preserving essential functionality across dator and mobile environments.
Keep in mind how prior data adoption works: sendt data may have already been associated with your profile. By continuing to use the opt-out, you steer future processing away from non-essential purposes and limit overföringen of information to external services. If you need to restore full tracking later, aktivera the option again and monitor the outcome across platforms to safeguard your utgången and control what becomes arkiveras.
| Step | Action | Data affected |
|---|---|---|
| 1 | Open Privacy controls and switch on Special cases opt-out | session, ip-adresserna, information on platser |
| 2 | Review data types listed for processing (e-postadresser, intressen, invändning) | reduces usage for non-essential purposes |
| 3 | Apply changes on all platser (dator, tablet, phone) | arkiveras less data; automatiskt linking disabled |
| 4 | Check past sends (skickat) and request removal if possible | data not used for new invändningar |
Steps to object to direct marketing under the policy
Recommendation: Under dsgvo, submit a direct marketing objection via the registreringsprocessen in your account. Use the metoderna to select all marketing preferences, and confirm with an ssl-certifikat-protected submission. Request that all personligen data used for direct marketing be blocked, eftersom this ensures your preference is respected and all future communications stop.
Step 1: Collect evidence. Identify what the leverantör holds about the kundens data, including viktiga avtalsuppgifter and ip-adresserna. Document the slag of channels used for direct marketing and the dates of transmissions. This creates a concrete record as part of the registreringsprocessen and helps you demonstrate the scope under dsgvo, förklarar your rights under the policy.
Step 2: Submit a formal objection in writing. Use registreringsprocessen or contact the privacy team at the leverantör. State clearly that you object to all direct marketing and request beständiga opt-outs for every channel. Include your contact details in personligen form and reference the policy text that describes the processing, as allowed under the dsgvo framework.
Step 3: Seek acknowledgment and set expectations. Ask for a written confirmation within 30 days, with a clear cessation plan and a reference number. If they propose continuing some categories, challenge the rationale and insist on minimal necessary processing. Verify that utgången of current campaigns is documented and that ip-adresserna are no longer used for marketing purposes.
Step 4: If the response is insufficient, escalate. In the north region, file a complaint with the supervisory authority and provide all avtalsuppgifter, dates, and copies of correspondence. You may also check reddit threads for practical tips, but rely on official guidance for your case and preserve the chain of communication.
Step 5: Harden future controls. Request that the leverantör implement beständiga opt-outs across alla slag of marketing (email, sms, social) and confirm that all data handling aligns with ssl-certifikat protections. Ensure the policy states how ip-adresserna and other personligen identifiers are shielded, and obtain a documented plan to maintain data minimization, since effective privacy protections rely on demonstrable safeguards and clear quality controls.
How to access and correct your personal data
Request a data copy from the Privacy section in your DeepL account. This action reveals what is behandlas in the system and shows the varaktighet of hanteringen. You will see trafikdata and related records, plus the syftet behind each processing activity. If you want to beställa an export for your records, use the export option.
To access your data, open Settings > Privacy > Your data and use the Export data function. The export is provided in a standard format that is easy to read and can be stored offline. It may include core fields such as account details, usage logs (trafikdata), and, if captured, fingeravtryck data. If you prefer a quick review, you can also download a lite summary.
How to correct information – Submit a correction request through the same Privacy portal. Include exact identifiers for the records to be changed and the corrected values. Explain the syftet for the correction, and reference any supporting evidence. Our tekniska checks verify identity and utfördas the update in the system. Corrections motsvarar the true information and apply across all linked services, including any data shared with external providers.
Processing timeline: after your request, you receive a confirmation notice. We aim to complete valid corrections within varaktighet defined by policy; typical processing ranges are around 31-37 days depending on data volume. You will be notified when the change is applied and when downstream recipients have been updated. If you need faster handling, provide additional documentation to support the correction.
Security and access controls: the system relies on tekniska protections to restrict access to your data. Cross-border transfers are limited to land that provide adequate safeguards and are performed only for purposes described by syftet. You can review and manage any data sharing with third parties, including entries connected to googleyoutube, and revoke permissions if needed.
Where your data is stored and how long it’s kept
Storage location and retention rules
Store data in encrypted servers managed by the personuppgiftsansvarige within kontrollcentret; access is limited to authorised användaren and logged when klickat on actions. The behandlingensömlös workflow ensures processing occurs only for analysändamål and that data handling stays tight to the purpose.
Core storage resides across regional data centers in the världen, with cross-border transfers permitted only under domänförslag safeguards and encryption in transit. This setup enables faster insights while keeping data protected and traceable for audits. gratis exports are available upon request, subject to policy and consent checks, and accessed via the kontrollcentret interface.
Retention follows lagringsperiod28. After efter the användaren session ends, the system enforces lagringsperiod28 and then deletes or anonymizes insamling data that no longer supports analysändamål. When behandla is required to genomföra a specific task, the system uses enbart the minimum data necessary and then proceeds with secure deletion. All actions are monitored under dennes governance, with logs maintained for audits by the personuppgiftsansvarige. The användaren may request a data handling summary via the privacy portal.
How DeepL protects data during processing and transfers
Enable encrypted transfers by default and review your data retention settings in your account to control how long inputs are stored.
Data handling during processing
- We minimize the syfte of processing to deliver translations, baserad on privacy-by-design, with periodiska recensioner of access and data usage.
- Data travels from the webbläsaren to our servers over TLS; at rest, information is protected by AES-256 encryption, and font-level key management ensures strong separation between clients. Säkra operations are maintained through continuous monitoring.
- Access to data is restricted by role-based controls and MFA; actions generate auditable logs that can citeras in security reviews and customer reports (kunden).
- Skickat inputs are kept only as long as needed for the syfte and are deleted on request or after the retention window; kunder kan återkalla data by following the hänvisare in your account.
Data transfers and external processing
- When affärsverksamhet-related subprocessors handle data, we follow the ramen of formal data protection agreements and standard contractual clauses to kräva protections for the kunden data.
- Transfers are monitored and documented; periodiska checks and recension logs help verify that protections stay intact and are citeras in reports.
- For more details on external policies, see httpswwwredditcomde-depoliciesprivacy-policy and related resources, then use the account hänvisare to contact if you need further clarity.
Practical privacy tips for using DeepL services securely
Limit data you send to DeepL to just what you need for translation, redact personal details like mail, efternamn, and other identifiers before submission.
Data handling and governance
- Data minimization: remove mail, efternamn, and other identifiers before translating; when possible, replace with initials or a placeholder to protect befintliga data in north-region contexts.
- Data flow and innehållsleverans: map how content travels from the customer to the tjänsteleverantören and back; verify länkar to privacy notices and ensure enlighet with lagstadgade krav, with a clear role for personuppgiftsansvariga.
- Access control: limit to legitimt users; designate a single personuppgiftsansvariga, enforce strong authentication, and store credentials securely on the dator; ensure gemensamt responsibility with the leverantör.
- Device and data hygiene: verify the förutsättning for secure use on the dator; use a dedicated dator for translations, keep OS and apps updated, enable disk encryption, and avoid sending from shared mail accounts; maintain minimal data in mail subject lines and bodies.
- Retention and deletion: ask the leverantör about data-återkallas processes and how long content is retained; require a documented artikel describing data hantering, and ensure efternamn and other personal data are erased when no longer needed.
Document the data lifecycle with a clearly defined slutet point for deletion, and ensure lagstadgade checks are met by the personuppgiftsansvariga. For configuration, välj privacy controls that fit your risk profile.
