Choose DeepL's privacy-first policy today – it erzeugt klare Regeln für personenbezogene Daten auf deinem webauftritt. laut den geltenden Bestimmungen schützt dieser Ansatz Ihre Daten, legt die dauer der Aufbewahrung fest und ermöglicht Benutzern, ihre Einwilligungen einfach zu verwalten. Diese Richtlinien unterstützen bewerbung Prozesse und Kundengespräche mit klaren Datenpfaden.
We cooperate with trusted anbieter to enforce data minimization, strict access controls, and strong encryption, so personenbezogener Daten stay within the boundaries described in dieses policy. glauben that clarity about data usage and retention helps, und weitere controls for consent management are provided.
For bewerbung workflows, the policy provides safeguards that keep your information safe, with explicit rights for individuals to access, rectify, or delete personenbezogene data. It also outlines die purposes of processing and the steps to exercise diese rights, with straightforward notices about handling and data subject rights.
On your webauftritt, the policy explains what data sich interacts with DeepL services, what is erzeugt by usage, and how long data remains stored (dauer). laut policy, you can review data categories and request deletions, and adjust consent preferences easily for allgemeinen teams across regions.
Start today with dieses privacy approach to reinforce user trust, provide clear notices, and ensure your webauftritt aligns with expectations across languages and markets.
Definition and scope: when restriction of processing applies under DeepL
Apply the restriction when a data subject exercises rights under dsgvo. The restriction limits verarbeiten to storage and to activities necessary to determine the data subject's rights; this is described nachfolgend in the policy, where steps are written in clear terms (beschrieben) and tied to gesetz and bestimmungen. If the data includes videos or other media, restricting processing prevents further disclosure or use until the matter is resolved, ensuring schätzen korrekt schützen (schützen) the data.
- Accuracy dispute: when the data subject contests the accuracy of personal data, verarbeiten is restricted to verification and storage only; no weiterverarbeitung, no disclosure to drittunternehmen, no imports to third-party systems (google, third-party-cookies) until accuracy is confirmed; nachfolgend actions proceed only to resolve the issue.
- Unlawful processing or widerruf of consent: if processing is unlawful or the data subject withdraws consent (widerruf), restriction applies to storage and to processing necessary to exercise rights or defend legal claims; dadurch wird verhindert, dass weitere schädliche oder nicht autorisierte verarbeiten erfolgt, until lawful grounds are restored.
- Legal claims or public interests: where processing must be halted to prepare, defend, or enforce Rechte, the restriction remains in place (öffentlichen Interessen) until determinations are made according to bestimmungen and the sitz of the organization is consulted withaufsichtsbehörde as needed.
- Data not needed for the declared purpose: when the data subject objects or when the data is no longer necessary for the ursprünglichen Zweck, the restriction can be applied to halt verarbeiten pending resolution of rights; daten bleiben gespeichert (storage) but are not weiterverarbeitet, unless required to protect Rechte or to comply with gesetzliche Verpflichtungen.
In all cases, DeepL ensures that restricted data remains isolated from active processing pipelines, and that any activities described durchführung avoid unnecessary exposure to drittunternehmen and andere external services. The sitz of DeepL and its verarbeitungslauf are kept consistent with dsgvo bestimmungen and the standorte of executives and aufsichtsbehörde oversight.
- Mark the affected records as restricted in the data stores, classifying them clearly as restricted (noting denoted purpose and rechtsgrund).
- Pause all non-essential verarbeiten, including any use in analytics, profiling, or third-party integrations (google, third-party-cookies) until the restriction is lifted or resolved.
- Limit disclosure: ensure no weitergabe to drittunternehmen or öffentlich zugänglichen systems occurs during restriction, and restrict access to only those employees who need it to verify or defend the data subject's rights (handelt in line with gesetz und bestimmungen).
- Document rationale: record the basis (gesetz, dsgvo, widerruf, accuracy concerns) and the expected duration, so aufsichtsbehörde or internal audits can review complying conduct.
- Communicate status: inform the data subject about the restriction, its scope (verarbeitet or verarbeiten nur storage), and the expected timeline for resolution, and provide instructions to einzuholen additional information if needed.
Proceedings follow the nächste steps nachfolgend to ensure compliance, including alignment with sitz, geplante durchführung, and any required coordination with aufsichtsbehörde. When restriction is no longer necessary, the data may be processed again in accordance with dsgvo und bestimmungen, and the data subject can exercise widerruf or other rights as appropriate.
Step-by-step guide to submitting a restriction request to DeepL
Submit the restriction request directly from your DeepL account to ensure tracking and a fast response.
- Sign in, open the Privacy section, and locate the restriction option oben.
- In the scope field, restrict processing of the data of personen, including nutzerverhaltens data; this restriction umfasst diese data categories and keeps your control tight.
- State a concise rationale and indicate that you may require berichtigung if any data is inaccurate; include enough detail so the team versteht your intent without exposing unnecessary information.
- Attach all relevant anliegens documents, ensuring you provide vollständigen and fehlerfreien information; if you have supporting files such as bewerbungsunterlagen for identity verification, add them here.
- Specify the results you want: restrict access, pause processing, and suspend new data treament unless necessary for vertragserfüllung obligations; mention dessen responsibilities and your rights as the data subject.
- Review the submission and confirm that the request keine extraneous data; the form should be clear about which records are affected and which remain accessible.
- After submission, monitor the status updates jeweils in the dashboard; you will see notifications at each step, and the communication remains visible oben until the process completes.
- If you also plan to kündigen the subscription, do so only after confirming the restriction actions; this kündigen step affects vertragserfüllung but does not cancel the restriction itself, helping you keep control of your datenfluss durch diese Beziehung dessen Klarstellung.
- Be aware that the restriction does not erase records automatically; some data may bleiben in systems to fulfill legal obligations; you can request braucht später eine Berichtigung oder Löschung, sofern zulässig, und vermeiden unnötige Aufnahme von weiteren Daten.
What data can be restricted and what remains processed
Recommendation: Restrict non-essential data collection and storage; ensure only data necessary for service operation is processed.
Data that can be restricted
Restrict erhobenen data tied to websitebesucher by shortening retention, and by turning off non-essential übersendung to analytics providers. Use austragung options to prevent automatic gesendet of non-critical data. For wordpress sites with embedded videos, disable non-essential data sharing by the video player and plugins. Minimize permanente Speicherung by keeping only critical identifiers for the lowest necessary period and avoid speichern of data beyond that. Limit übermittlung of personal data through forms and disable automatic data export unless the user submits explicitly. The berichtigung path remains available, and sitzungscookie usage should be limited to the current session.
Data that remains processed
Essential authentication, session integrity, and security-related data stays processed. The eu-kommission allows this processing under transparency and consent rules, provided you offer clear berichtigung pathways and easy opt-out where feasible. Data that remains may include anonymized or aggregated metrics to improve the service, while keeping individual records minimally exposed. If a user requests berichtigung, the system must respond to that request (darauf) and update the records accordingly. Sitzungscookie data is stored only for the active session or a short specified period, and longer retention requires explicit consent.
What data cannot be restricted and how exceptions are handled
Restrict only what law and policy require, and clearly mark non-restrictable data. Übereinkommen set the framework for user rights; Durchführung evaluates each exception to ensure compliance. If a user provides einverstanden, we apply the exception within the defined scope. The following datenverarbeitungen cannot be restricted: security logs, system configurations, audit trails, and legally mandated records that support Rechte and Verfugung. These items erzeugt by the service are used for Nutzung and system integrity, damit the platform remains reliable. Access is restricted to authorized roles, with strict logging, and Browserversion plus Einstellungen explainers show what is affected. The non-restrictable data are essential to detect misuse and to demonstrate compliance to regulators, including in erfurt jurisdictions.
Data that cannot be restricted
The categories above cannot be restricted in bulk because removing access would impair safety, legal compliance, or operational integrity. Security logs, configuration data, audit trails, and legally required records are erzeugt to support investigations, rights verification, and verfgung handling; access is limited to approved roles and governed by zwingende retention periods. These datenverarbeitungen are managed jointly (gemeinsam) within our governance framework, with clear austragung rules and documented consent where applicable. The Browserversion and Einstellungen tools help users inspect the current status and understand where restrictions apply.
Handling of exceptions
Exceptions follow a formal, time-bound workflow. A privacy or compliance owner drafts eine klare Begründung (folgendem) detailing the datenverarbeitungen involved, the Zweck, and the exact retention window. Approvals (angeklickt) are recorded with the approver and timestamp. The exception is narrowly scoped and einbinden into the overall data governance to preserve controls. The data involved is genutzt only for the stated purpose, and access is limited to need-to-know roles. User notices appear in Browserversion and Einstellungen so users understand the impact and can exercise Rechte; if a user requests Austragung or correction, we process it within the constraints of the exception terms and applicable laws. All actions are auditable, and erfasst daten (erzeugt) are monitored to ensure the exception does not undermine privacy or security, including in erfurt contexts.
Verification requirements: documents and identity needed for a restriction request
To initiate a restriction request, your account verfügt over identity verification and the required datei attachments. Follow these steps to ensure a smooth review.
Required documents
We offer auswahlmöglichkeiten that cover common scenarios. обязательно auch include these items to strengthen the case: a government‑issued ID, a university card when applicable, and proof of address. These checks rely on the universität credential when available, and you may submit additional files as needed in diese process.
| Document type | Purpose | Notes |
|---|---|---|
| Passport or national ID | Identity verification | Upload as datei; readable scan; accepted formats include PDF, JPG, PNG |
| University-issued ID (universität) or official student card | Affiliation proof | Attach as datei; name should match account; if tied to academia, this speeds review |
| Proof of address (Straße, number, city) | Residence verification | Clear scan of latest document; include street name; temporär use; avoid exposing diese data on öffentlich platforms |
| External e-mail-adresse verification | External contact validation | Attach confirmation from the external address; ensure the address is verifiziert |
| Vimeo account (vimeo-account) link | Additional ownership check | Provide URL if connected; used to corroborate identity where applicable |
We handle datenverarbeitung with a focus on vertraulich storage and restricted weitergabe to datenempfänger who need it for verification. betragen this process, we keep the data confined to internal systems and avoid public exposure.
Submission steps
Proceed on the restrictions page by choosing die vielfältigen auswahlmöglichkeiten to categorize each attachment. In diesen steps, decide (entscheiden) which files to attach, and provide a current e-mail-adresse for confirmations. During submission, the browsertyp and websitebesucher signals help spot anomalies, while temporär session-cookies maintain a secure session; these details stay within datenempfänger scope and are not exposed on öffentlich sites. You decide which documents to share, and we will not proceed without your explicit confirmation.
Timeline and expected responses for restriction requests
Submit the restriction request through your account dashboard; we acknowledge within 24 hours and begin a targeted review of the data we hold, including internetbrowser logs, seitenaufrufe, fonts, and die Durchführung of the restriction in relation to your eigene bewerbungsunterlagen and die übermittelten data. We verify which items sind vorhanden and which Fälle require restriction, in line with vertrags constraints and our privacy policy, jedoch ohne dass andere Daten verarbeiten werden. This step dient dem Schutz Ihrer Daten and ist sehr straightforward; you will receive gesendet updates as we progress.
Timeline
Acknowledgement within 24 hours, followed by an initial assessment within 3-5 business days. If the scope includes large volumes of seitenaufrufe or internetbrowser zugriffe, we provide interim updates within 7-10 business days. The final decision arrives within 30 days; Extensions to 90 days may be granted with a clear justification, and you will be notified. All actions are logged in your account and affect only restricted data, not other data unless required by law or vertrags obligations.
Possible responses
Restriction granted in full: we set flags to limit Zugriffen, Nutzung, and weitere Verarbeitung of the restricted data; the data remain stored (verarbeitet) but are not used for processing or display, and gesendet confirmation appears in your account. Restriction granted partially: we specify the exact scope (e.g., bestimmter datasets wie bewerbungsunterlagen or bestimmten seitenaufrufen); other data remain available. Denied: we provide a justification citing vertrags constraints, legal obligations, or safety concerns; we propose alternatives such as minimization or anonymisierung; gesendet rationale is provided and logged. This process is sehr transparent and aims to minimize Auswirkungen auf andere Dienste.
Impact of a restriction on service functionality and user rights after application
Notify the nutzer immediately when a restriction is applied and provide a concise, user-friendly explanation of which service functionality is affected, the rechtliche basis, and how dieser vertrag in deutschland governs the change. This notice stellt the nutzer with clear expectations about the blocked features and the estimated restoration timeline, and it includes steps for benötigten actions. The communication should be accessible in the UI and archived for audit purposes immer.
When a restriction is in effect, we limit datenverarbeitungsvorgänge to what is strictly necessary to support the remaining actions. We specify which personenbezogener data may be abgefragt to verify eligibility, and we clarify that session-cookies are used to maintain state during the restricted window. If any drittunternehmen are involved to support solchen processing activities, we name them and present safeguards. This approach aligns mit dem vertrag and follows rechtliche standards in deutschland, ensuring that such processing remains proportional and transparent.
The nutzer retains core rights after application: access to data, correction of inaccuracies, and the right to erasure where lawful. We explain how to exercise these rights through unserem support channel, including identity verification steps, and provide a dedicated process for requests. The rechtliche basis in diesem vertrag remains applicable in deutschland, and beschäftigungsverhäntnisses related data may trigger a separate review; The status befindet within the policy and we communicate updates promptly. If any drittunternehmen are involved, we apply safeguards and limit data sharing to what is necessary.
To lift the restriction, the system will re-evaluate the underlying issue and stellen a status update in the user dashboard. The process requires a verification step by the responsible team; Once resolved, access is restored for all users, and a confirmation is sent via the channel the user prefers. Session-cookies are updated to reflect the new state, and datenverarbeitungsvorgänge return to standard levels. We keep records for audit and ensure that no additional data flows occur.
If you have questions about these steps, contact our support team via the in-app contact form or unserem contact channel. We remain committed to protecting nutzer data and to transparency in jedes Beschäftigungsverhäntnisses and vertrag.
