YIDL.io / Private access
Privacy notice
Draft — outstanding provider and privacy details must be confirmed before publication.
1. Controller and contact
mediaphony., proprietor Andrew Kopp, Lavendelweg 14, 45770 Marl, Germany. For privacy enquiries: info@yidl.io, telephone +49 2365 986521. Any requirement to appoint a data protection officer must be clarified before publication.
2. Hosting
The website is intended to run on IONOS hosting. The host processes technical connection data, including IP address, request time, requested file and browser/server information, to deliver and secure the site and analyse errors. The specific IONOS contracting entity, processing agreement, storage locations, actual log retention and any international transfers must be confirmed before publication.
3. Approved email addresses and one-time codes
Authorised administrators store email addresses, roles and access status in the CMS. Code requests process the entered email address and technical request data to verify eligibility. IONOS SMTP sends codes from noreply@yidl.io. Code verification values are hashed. Codes expire after 10 minutes and become unusable after use or five failed attempts. Request limits use SHA-256 values of IP and entered email addresses; hashing does not make these data anonymous. Expired code and rate-limit records are cleaned on subsequent code requests or by the planned maintenance task.
4. Sessions and theme preference
The yidl_session cookie associates login status, language and form protection with the session. Access expires at most one hour after login or upon sign-out; disabling a user also revokes existing access. A manually selected theme is stored locally in the browser as yidl-theme until changed or deleted in browser settings. Otherwise the theme follows the system setting.
5. CMS and audit records
The CMS stores email addresses, roles, active status and a session version. Changes to users and page content are logged with time, administrator email, action and target. The maintenance command removes audit records after 90 days and must be scheduled daily on the host. Accounts remain until administratively deleted; binding deletion rules remain to be defined. Disabling an account does not delete it. Content, page structure and release metadata also retain revisions with author and time. These are kept for traceability; a binding retention policy must be set before launch.
6. Purposes, legal bases and recipients
Processing supports controlled access to the preview, delivery of approved trial files and abuse prevention. Article 6(1)(f) GDPR is a provisional basis for necessary delivery and security processing, with the interest of operating a secure private preview. Article 6(1)(b) may apply to actual pre-contract enquiries. The basis for each activity and the assessment of browser storage under section 25 TDDDG must be confirmed before publication. Role-authorised operator staff and the contracted hosting/email provider receive necessary access. The current application includes no analytics, advertising or externally embedded media services; additional hosting services must still be checked.
7. Your rights
Subject to applicable conditions, you have rights of access, rectification, erasure, restriction and data portability, and may object to processing based on legitimate interests. Where consent applies, it may be withdrawn for the future. Contact info@yidl.io. You may complain to a data protection supervisory authority; the authority for private operators in North Rhine-Westphalia may be the LDI NRW.
8. Further information
An approved email address is needed for portal access. The application does not use profiling or make automated decisions within Article 22 GDPR. Portal access grants no product licence. This notice describes the development state; marked hosting, retention and legal-basis details must be completed before launch.
mediaphony., proprietor Andrew Kopp, Lavendelweg 14, 45770 Marl, Germany. For privacy enquiries: info@yidl.io, telephone +49 2365 986521. Any requirement to appoint a data protection officer must be clarified before publication.
2. Hosting
The website is intended to run on IONOS hosting. The host processes technical connection data, including IP address, request time, requested file and browser/server information, to deliver and secure the site and analyse errors. The specific IONOS contracting entity, processing agreement, storage locations, actual log retention and any international transfers must be confirmed before publication.
3. Approved email addresses and one-time codes
Authorised administrators store email addresses, roles and access status in the CMS. Code requests process the entered email address and technical request data to verify eligibility. IONOS SMTP sends codes from noreply@yidl.io. Code verification values are hashed. Codes expire after 10 minutes and become unusable after use or five failed attempts. Request limits use SHA-256 values of IP and entered email addresses; hashing does not make these data anonymous. Expired code and rate-limit records are cleaned on subsequent code requests or by the planned maintenance task.
4. Sessions and theme preference
The yidl_session cookie associates login status, language and form protection with the session. Access expires at most one hour after login or upon sign-out; disabling a user also revokes existing access. A manually selected theme is stored locally in the browser as yidl-theme until changed or deleted in browser settings. Otherwise the theme follows the system setting.
5. CMS and audit records
The CMS stores email addresses, roles, active status and a session version. Changes to users and page content are logged with time, administrator email, action and target. The maintenance command removes audit records after 90 days and must be scheduled daily on the host. Accounts remain until administratively deleted; binding deletion rules remain to be defined. Disabling an account does not delete it. Content, page structure and release metadata also retain revisions with author and time. These are kept for traceability; a binding retention policy must be set before launch.
6. Purposes, legal bases and recipients
Processing supports controlled access to the preview, delivery of approved trial files and abuse prevention. Article 6(1)(f) GDPR is a provisional basis for necessary delivery and security processing, with the interest of operating a secure private preview. Article 6(1)(b) may apply to actual pre-contract enquiries. The basis for each activity and the assessment of browser storage under section 25 TDDDG must be confirmed before publication. Role-authorised operator staff and the contracted hosting/email provider receive necessary access. The current application includes no analytics, advertising or externally embedded media services; additional hosting services must still be checked.
7. Your rights
Subject to applicable conditions, you have rights of access, rectification, erasure, restriction and data portability, and may object to processing based on legitimate interests. Where consent applies, it may be withdrawn for the future. Contact info@yidl.io. You may complain to a data protection supervisory authority; the authority for private operators in North Rhine-Westphalia may be the LDI NRW.
8. Further information
An approved email address is needed for portal access. The application does not use profiling or make automated decisions within Article 22 GDPR. Portal access grants no product licence. This notice describes the development state; marked hosting, retention and legal-basis details must be completed before launch.