Privacy Notice
KR ECAMPUS / WEBSITE AND LEARNING PLATFORM
Privacy information for the website and the entire eCampus tool offered to customers outside the EU.
1. Controller and contact
For the German and EU offering, the controller is KR Krisensicher Risikoberatung GmbH, Hauptstraße 3/4, 15907 Lübben, Germany, represented by managing director Rico Kerstan. Contact post@krisensicher-werden.de, telephone +49 151 555 303 512.
KR International Services LLC is the provider for customers outside the EU. A domain or language choice alone does not determine the contracting company. A company acts as processor only for services performed exclusively on documented instructions under an appropriate agreement; that role does not follow automatically from hosting or company affiliation.
2. Public website, contact form and optional statistics
The homepage announces learning topics. Online purchases and payments are not yet enabled here. Fonts, images and scripts are served from our hosting.
Contact form
We process your name, email address, enquiry category, message and optional organization to answer your enquiry. An acknowledgement is sent to your email address. Hosting, the delivery queue and email delivery use STRATO. Where the GDPR applies, processing is based on Article 6(1)(b) for your own contract enquiry or Article 6(1)(f) for business contacts and other enquiries (interest: handling correspondence). Random form tokens and a daily, domain-specific HMAC identifier derived from IP address and date protect the form from abuse under Article 6(1)(f). The raw IP address is not retained for this purpose.
Form tokens expire after 15 minutes and rate-limit data after ten minutes. Technical message copies are erased seven days after both emails have been sent, or at the latest 30 days after receipt if delivery remains incomplete. Minimal queue metadata is erased after 30 days. Correspondence handled in our mailbox is generally erased six months after the matter is closed; legally required business correspondence and records follow the periods below.
Our own optional usage statistics
Statistics start only after you select “Allow statistics” in the footer. Where applicable, the legal basis is your consent under Article 6(1)(a) GDPR and Section 25(1) TDDDG for access to device information. You can withdraw consent there at any time for the future. DNT and Global Privacy Control are respected. Declining does not affect access to the website.
We collect the page path without query parameters, language, referring domain without the full URL, time, active reading duration and scroll depth. The IP address is used immediately to derive a daily, domain-specific HMAC identifier and, optionally, to determine a country using a local database; it is not stored in the statistics. Browser identifiers, form contents and eCampus learning accounts are not combined with these statistics. There are no advertising profiles or external analytics services. Raw statistical events including the pseudonymous daily identifier are erased after 30 days; daily aggregates without that identifier after 13 months. These are operational maximum periods, not legal minimum periods. Data is hosted at STRATO.
Local browser storage holds only your statistics choice under ecampus_statistics_consent until you change it or clear browser storage. This entry preserves the setting you requested and contains no visitor identifier; where applicable, Section 25(2)(2) TDDDG applies.
3. Information used by the actual service
| Category and source | Examples and purposes | Who may receive it |
|---|---|---|
| Technical information from your browser and the service | IP address, time, requested page, browser/system details, connection status and security events, to deliver and protect the service | Authorized operations staff and necessary hosting/network providers |
| Information you or your purchasing organization provide | Name, email, organization, billing country/address, chosen course and transaction references, to handle inquiries and course contracts | Authorized customer administration, accounting and the selected payment service where actually used |
| Account and learning activity | Account verification, roles, enrollments, module progress, answers, attempts, scores, flashcards and optional notes/reflections | You and the instructors/administrators authorized for the relevant purpose |
| Live participation and shared content | Pseudonyms, guest identifiers, group assignments, polls, chat, audio/video, screen/whiteboard content and submitted files | People in the appropriate room/group and authorized instructors or moderators |
| Assessment and qualification records | Eligibility, evidence, reviews, final decisions, certificate reference, recipient name and validity status | Authorized assessors and issuing staff; limited certificate verification where enabled and appropriately disclosed |
| Support and optional feedback | Your issue description, relevant technical context, voluntary screenshot or review | Authorized support; a review’s stated public audience only when publication is properly authorized |
We do not request government identity numbers, payment-card security codes, health information or other sensitive personal information through this public homepage. Do not include credentials or unnecessary sensitive information in a message, learning example, uploaded file or help request.
4. Why information is processed
The relevant purposes are providing the website, responding to inquiries, administering course contracts and access, delivering learning activities and feedback, conducting the assessment you select, supplying requested materials, resolving support issues, maintaining security, and meeting applicable recordkeeping or legal obligations.
Information supplied by an employer may identify you as a participant or eligible user. An employer’s purchase does not automatically entitle it to all raw answers, private reflections or assessment details. Any agreed organizational reporting must have its own defined scope and lawful basis. Where participant information is obtained from another organization, its source and the relevant use must be explained to the participant.
5. Learning, assessment and live participation
An account may contain verification status, password verification data, permissions, optional profile information and course activity. Guest participation can use a random identifier, pseudonym and avatar. A pseudonym does not make participation anonymous. Private work, group work and content deliberately released for presentation or a workbook have different visibility rules.
The documented group-assignment function can use a derived check value for a known organizational email domain to help distribute people from the same organization across groups. This is not a marketing profile. Requested materials may require name, email and a confirmation link; a marketing opt-in is not a condition of the documented material-access function.
Where transfer follow-ups are enabled, the service can retain your action plan, reflections, scheduled follow-up and deliberately requested external feedback. Inviting a feedback giver uses their necessary contact details and the limited information designated for the invitation; it does not release your entire learning record. The invited person must receive the relevant information about the source and purpose. Course/role administration and authorized reports support delivery, not unrestricted employer monitoring.
Assessment functions may maintain evidence, reviews, a final result and certificate status. The reviewed workflow includes human final responsibility; a practice score is not by itself an exclusively automated legally significant qualification decision. A material change to automated assessment requires a fresh explanation and legal assessment.
6. Audio, video, rooms and recordings
If conferencing is provided, it processes your enabled media, shared content, room assignment and necessary connection/moderation events. The reviewed architecture uses a self-operated LiveKit media server; using that software is not evidence that LiveKit Cloud is used. Media and participation visibility depend on room membership and authorized moderation functions.
Some events may have a disclosed camera rule. The implementation can check receipt of a small number of camera frames and process limited activity or attendance-confirmation events. It does not establish a person’s identity through biometric recognition. The need for the rule and available participation arrangements must be explained for the actual event. Browser permission is a device control, not blanket legal consent for every subsequent use.
The reviewed recording feature deliberately records only the presenter’s own local microphone track. It is not a room mix, does not automatically upload to a server, and does not include a participant download function. Other people’s speech in the presenter’s physical environment may still be audible; recording requires an appropriate basis and notice. The presenter controls downloaded files and separate backups. The platform cannot centrally promise their deletion.
The documented text chat is held in memory and cleared at session end. Saved whiteboard material and deliberately released results have a different lifecycle.
7. Integrated interface help using OpenAI
The eCampus interface help uses the OpenAI API. When you request assistance, your question, limited conversation context where needed, and relevant product, role and page information are processed to provide an answer. The public homepage does not itself send AI requests.
This help explains platform functions. It does not operate your account or make assessment decisions. Do not enter passwords, health information, confidential case files or unnecessary information about other people.
For processing within GDPR scope, the legal basis for user-requested interface assistance is Article 6(1)(f): our legitimate interest in understandable and accessible assistance. Additional AI learning activities are separate functions with their own purpose and legal basis.
OpenAI states that API data is not used for training by default without an explicit opt-in. Abuse monitoring logs may normally be retained for up to 30 days, subject to legal or security exceptions. Feature-specific application state may involve additional retention. We do not promise zero retention or exclusively European processing. See OpenAI API Data Controls.
Our internal retention requirements specify store=false, no training opt-in and no persistent KR content logs for this help. These requirements do not mean that KR can immediately delete all provider-held information. Actual project settings and contractual arrangements determine provider processing. Contact us for information about applicable safeguards.
9. Cookies and browser storage
The public homepage does not set cookies or persist a cart. The connected learning platform can use necessary sign-in, challenge, live-participation and material-access cookies. It can also retain selected display preferences or local work drafts in browser storage.
Examples in the reviewed implementation include ECAMPUS_SESSION, ECAMPUS_LOGIN_CHALLENGE and function-bound live/material access, plus local preferences for collapsed navigation, reduced motion and camera background blur. A local-storage preference can remain until you reset it or clear browser data. The complete enabled storage inventory and actual token lifetimes need to match the production version.
Where applicable law requires prior consent for a storage use, that requirement must be implemented before the use starts. The statistics preference and withdrawal control are described in section 2.
10. How long information is kept
Retention depends on the purpose and record type. Short-lived access tokens are distinct from active course content, assessment/certificate records, accounting documents and backups. Inquiry data is needed to resolve the request and for any justified subsequent evidence period. Learning data supports the agreed access and learning activity; after those purposes end it must not remain indefinitely without another valid reason.
Accounting and business records may be subject to applicable retention obligations. Assessment records can be needed for decisions, challenges and certificate verification. Account deletion therefore does not necessarily erase every required invoice or qualification record at the same moment. Specific target periods and starting events for logs, materials, support, assessment/certificates, email and backups are now documented in the processing record. Their production implementation still needs to be verified; a written schedule does not prove that deletion has occurred.
The documented text-chat lifecycle clears in-memory chat when the session ends; deliberately saved learning/whiteboard content is separate. Stripe and OpenAI can have their own storage obligations and arrangements for the processing they perform. Provider retention depends on the API endpoint, settings and applicable exceptions.
Backups must expire appropriately and deletion/restriction requirements must be reapplied after restoration. Downloads and local presenter recordings are separately controlled by their device/file owner.
11. Security
The reviewed platform includes role- and session-bound access checks, restricted storage paths, TLS at its public boundary, protected sessions, short-lived access links and controlled backup/restore procedures. These are implementation characteristics, not a certification of an unverified production deployment. No method of storage or transmission is perfectly secure.
Where a security incident affects personal information, applicable investigation, cooperation and notification duties must be followed. Wyoming breach-notification requirements can apply to covered incidents involving Wyoming residents; other jurisdictions may impose additional requirements. We do not apply a blanket Wyoming-only notification rule to all users.
12. Your rights and contact
You may request access, rectification, erasure, restriction and portability under the conditions of the GDPR. You may object to processing based on legitimate interests and withdraw consent with future effect. Legal retention obligations and the rights of others may limit deletion. Contact post@krisensicher-werden.de. We verify identity only as necessary and respond within the applicable legal periods.
You may complain to a supervisory authority, including at your place of residence or work. For the German provider: Die Landesbeauftragte für den Datenschutz und für das Recht auf Akteneinsicht Brandenburg, Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany; www.lda.brandenburg.de.
13. Where European data protection law applies
A non-EU offering or Wyoming business address does not by itself exclude the GDPR. For user-requested interface help, we rely on Article 6(1)(f), with the interest of providing understandable and accessible assistance; a documented balancing assessment and a valid transfer basis remain necessary. If processing falls within its scope, the relevant legal grounds are contract-related processing under Article 6(1)(b), appropriate legitimate interests under Article 6(1)(f), legal obligations under Article 6(1)(c), or valid consent for a genuinely optional use under Article 6(1)(a). A contact acting for a business is not automatically the individual contracting customer.
Relevant rights can include access, correction, erasure, restriction, portability, objection and withdrawal of consent, subject to their legal conditions. You may complain to a competent supervisory authority, including where you live or work. For the German provider: Die Landesbeauftragte für den Datenschutz und für das Recht auf Akteneinsicht Brandenburg, Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany; www.lda.brandenburg.de. Required information about an EU representative or data protection officer must be added if a relevant appointment is required; no appointment is assumed in this notice.
Where Chapter V of the GDPR applies, transfers to recipients outside the EEA, including remote access from the United States, need a valid transfer basis and any required supplementary measures. This notice does not assert an existing Data Privacy Framework certification or signed standard contractual clauses. Information about actual safeguards must be made available for the processing concerned.
14. International processing
eCampus uses STRATO hosting. Stripe payments and OpenAI assistance can involve international processing. German hosting does not mean that every processing operation remains in Germany.
Where GDPR Chapter V applies, a valid transfer basis and any required supplementary safeguards are necessary. We do not infer completed contracts, Data Privacy Framework certification or an EU-only project configuration from a provider’s public website. Contact us for information about the safeguards applicable to your processing.
15. Children
This offering is for professional education and is not directed to children under 13. We do not seek children’s personal information through this website. If you believe such information has been provided, contact us so that we can investigate and take the steps required by applicable law. A children’s offering would require a separate assessment and appropriate notices and controls before launch.
16. Scope and changes
This notice covers the public eCampus website and the entire eCampus tool, including accounts, learning, live participation, conferencing, materials, assessment, support, payment and OpenAI help, when the relevant function is used. We update this notice when processing changes.
Version: October 24, 2026