Privacy policy

This model explains the standard processing of FT-Welt under the GDPR for an operator established in Germany. Before publication, complete every marked field and adapt the text to the actual hosting, mail services, purposes and deletion practices. Empty operator fields do not replace mandatory information.

Controller and data protection contact

Item	Details
Controller	FT-Welt UG (haftungsbeschränkt)
Street and house number	Droysenstr. 5
Postal code and city	10629 Berlin
Country	Germany
Data protection officer, if appointed	Demo Privacy Officer (fictional)
E-mail
Phone
WhatsApp, if offered

Electronic contact details are delivered in masked form to reduce automated harvesting and displayed by JavaScript after the page loads. [TO COMPLETE IF APPLICABLE: contact details of any appointed data protection officer.]

Hosting and server logs

To deliver this website and protect it against attacks, the infrastructure processes connection data, including the IP address, request method, requested path, response status and technical timing information. The address recorded in logs may be a proxy's connection address or a visitor address, depending on the deployment. IP processing is not automatically anonymous. The actual log fields and deletion periods are specified below.

The legal basis is Article 6(1)(f) GDPR: our interest in operating a secure, reliable website. The standard access-log format omits query parameters; additional hosting, error and security logs depend on the actual environment.

Item	Details
Hosting provider	Demo Hosting
Hosting country	Germany
Actual logs, data fields and retention	[TO COMPLETE: each log destination, collected fields, justified retention and deletion procedure.]

Cookies and local storage

The standard application stores the following information for preferences or authorised access. Section 25 TDDDG applies to local storage as well as cookies. Access strictly necessary for an expressly requested function can fall under section 25(2) no. 2 TDDDG; otherwise prior consent is required. Whether the exception covers a particular persistent preference must be assessed for the actual service and storage period. No blanket exemption from consent follows from the absence of advertising.

Name	Purpose and trigger	Storage period
bx_scheme	Appearance selected by the visitor	1 year
bx_theme	Colour theme selected by the visitor	1 year
bx_lang	Website language selected by the visitor	1 year
__Host-bx_session	Secure first-party session for sign-in and authorised account access	Session cookie without a fixed expiry; server-side idle limit of 12 hours
bx_admin_lang	Manually selected admin language in local storage	Until removed or browser storage is cleared
bx_admin_sidebar	Collapsed admin navigation selected by the user, in local storage	Until the setting is removed or browser storage is cleared

[TO COMPLETE: document the applicable storage exception or obtain consent before any storage that requires it; include additional cookies and storage from project extensions.] You can remove or restrict storage through your browser. Blocking necessary cookies can prevent sign-in; blocking preference storage can prevent choices being remembered. Necessary personal-data processing is based on Article 6(1)(f), or Article 6(1)(b) where required for your contract; consent-based processing uses Article 6(1)(a).

Fonts and additional services

The standard application delivers its fonts from this website and includes no advertising trackers or audience-measurement service. Hosting-level services and project extensions must be described separately if used. [TO COMPLETE IF APPLICABLE: actual analytics, embedded services and their consent and recipient information.]

Contact requests and communication

When you use the contact form or other offered channels, we process the information you provide, including your name, contact address, subject, message, language and any additional form fields, to handle the request and reply. Fields marked as required are needed for that channel; without them the form cannot be submitted. Other information is voluntary. Avoid sending sensitive information without first agreeing a suitable channel.

For requests necessary for a contract with you or steps you request before a contract, the basis is Article 6(1)(b). For other enquiries, Article 6(1)(f) applies to our interest in answering communications. Statutory preservation duties, where applicable, use Article 6(1)(c). Messages can be stored in the application and transmitted to the responsible team through our mail service. An optional confirmation may be sent if enabled. Deleting a record from the application does not itself delete copies in mailboxes or backups.

Protection against spam and misuse

To limit automated submissions, duplicate messages and unauthorised sign-ins, we process connection data, request timings, form tokens, counters and keyed hash values derived from client and message data. Such hash values are not automatically anonymous. Security checks may limit, reject or hold a request for review. If a legitimate message cannot be sent, use another contact channel above. The basis is Article 6(1)(f), protecting availability, accounts and recipients against abuse.

Invited accounts, sign-in and password checks

For invited users we process account identifiers, names, work contact details, permissions, account status, session data and security events. Initial details may come from an authorised administrator or the organisation inviting you, rather than from you directly. Invitation and password-reset messages are sent to the account address. Passwords and link tokens are stored as hashes; the session identifies an authorised user.

The account-related basis depends on the actual relationship: Article 6(1)(b) where necessary for a contract with the person, applicable employment law where relevant, and Article 6(1)(f) for securing and administering authorised access. [TO COMPLETE: the applicable relationship, exact account-processing basis, source organisation and retention; provide invitation recipients with the information required by Article 14.]

When a password is set or changed, the default password check queries Pwned Passwords, operated by Superlative Enterprises Pty Ltd, Australia. Our server sends only the first five characters of a password hash, not the password, full hash or account e-mail. The provider receives the server request and its connection metadata; this is not a direct connection from your browser. The purpose is protecting accounts against known compromised passwords, on Article 6(1)(f). [TO COMPLETE: actual service configuration, provider processing locations and any applicable international-transfer safeguards.] Provider information: Pwned Passwords privacy information.

Recipients and international processing

Recipients may include authorised staff, hosting and mail providers and the password-check provider described above. Where a provider acts as a processor, an agreement under Article 28 is required. A disclosure required by law is assessed separately. If you use an offered third-party messenger, that service also processes your data; e-mail or the contact form are alternatives.

[TO COMPLETE: identify the actual mail provider and other recipients, their purposes and processing locations, including any offered messenger. For each transfer of personal data outside the EEA, state the applicable adequacy decision or other lawful mechanism, such as applicable Article 46 safeguards, and how to obtain a copy. Do not assume that a provider's use of hashing or an EU hosting address rules out international processing.]

Retention and deletion

Retention depends on the purpose, outstanding correspondence, legal preservation duties and the need to establish, exercise or defend claims. The following schedule also covers mailbox copies and restricted backup retention. [TO COMPLETE: establish, justify and implement the actual periods before publication.]

Data	Period or deletion criterion
Access, error and security logs	[TO COMPLETE: actual periods and deletion.]
Ordinary contact requests and correspondence	[TO COMPLETE: period after final resolution; identify any applicable preservation duty and restricted further storage.]
Quarantined spam	Scheduled deletion after 30 days from receipt. [TO COMPLETE: confirm that the scheduler worker runs in this deployment and establish the actual cleanup interval.]
Failed mail queue records	Scheduled deletion after 90 days from creation; this does not cover accepted mail or mailbox copies. [TO COMPLETE: confirm that the scheduler worker runs in this deployment and establish the actual cleanup interval.]
Accounts, invitations and reset records	[TO COMPLETE: account lifecycle and deletion of used, expired or revoked records; link expiry alone is not deletion.]
Sessions, mailboxes and backups	[TO COMPLETE: server-side cleanup, mailbox periods, backup rotation and handling of restored deleted data.]

Your rights

Subject to the applicable conditions, you may request access, rectification, erasure and restriction under Articles 15 to 18 GDPR. Article 20 provides data portability for relevant automated processing based on consent or contract. Where processing uses consent, you may withdraw it for the future without affecting the lawfulness of earlier processing. Contact the controller using the channels above; requests are generally answered within one month, with a reasoned extension where Article 12 allows it.

Right to object: under Article 21, you may object on grounds relating to your particular situation to processing based on legitimate interests. We then stop that processing unless the statutory grounds for continuing it apply, including overriding compelling grounds or legal claims.

Complaints and automated decisions

You may complain to a data protection authority under Article 77, particularly in the Member State of your habitual residence, place of work or the alleged infringement. [TO COMPLETE: competent authority's name and website.] This does not require first contacting us.

[OPERATOR TO CONFIRM: the functions in this deployment do not make solely automated decisions producing legal or similarly significant effects under Article 22.] Abuse filters and password checks make technical security decisions; project-specific profiling or significant automated decisions require a separate assessment and additional information. Review this notice whenever the services or processing change.