Privacy Policy

Last updated: 22 August 2026

Working draft for test operation. Before launch, the final legal form, service address, competent data protection authority and specific retention periods must be added and the text must undergo legal review.

1. Controller

The controller is RED – Regenerative Ecosystem Development (company being established), represented by Alexander Maier. The service address and final legal form will be added before live operation.

Contact: info@red-regeneration.org · Telephone: +34 603 218 450

2. Hosting and server logs

The website is hosted by ALL-INKL.COM – Neue Medien Münnich. When pages are requested, technically necessary log data may be processed, including IP address, date and time, requested file, amount of data, referrer, browser and operating system. This supports secure, stable operation and error analysis under Article 6(1)(f) GDPR.

Logs are retained only as long as required for security and operation. The regular period will be specified before launch based on the final hosting configuration.

3. Cookies and local storage

RED uses strictly necessary cookies for sessions, sign-in, security and language choice. Where information is stored on or read from a device, this is limited to functions strictly necessary to provide the requested service; subsequent processing relies on Article 6(1)(b) or (f) GDPR as appropriate.

Analytics, marketing or comparable optional technologies will be used only with prior consent. The current test version does not provide for such optional cookies.

4. Contact and email

When a person contacts RED, RED processes the information provided, typically name, email address, subject, message and, if supplied, telephone number. Processing serves to answer the request. The legal basis is Article 6(1)(b) GDPR for contractual or pre-contractual communication and otherwise Article 6(1)(f) GDPR.

5. Registration and subscription account

Account data includes email address, password hash, form of address, name, date of birth, country of residence, postal address and optional telephone and mobile numbers. RED also processes verification, login, payment and subscription status and preferred language. Plain-text passwords are not stored.

Processing is necessary for registration, contract preparation, access control, billing, support and subscription administration under Article 6(1)(b) GDPR. Billing records subject to statutory retention are additionally processed under Article 6(1)(c) GDPR.

6. Payments through Stripe

RED uses Stripe for secure checkout. Data needed to process and match a payment may be transmitted, such as email address, customer and session identifiers, amount, currency and payment status. Card, bank or PayPal details are entered directly in Stripe Checkout and are not stored on the RED server.

Processing relies on Article 6(1)(b) GDPR and statutory retention on Article 6(1)(c) GDPR. Stripe also processes data under its own responsibility; see the Stripe Privacy Policy. No real payment is collected in the clearly marked test environment.

7. Telegram group and RED bot

Access to the private Telegram group is an optional part of Premium. If used, RED processes the data needed for invitations and access administration, including Telegram user or chat ID, display name or username, invitation and membership status, commands and service messages sent to the RED bot.

This is required to provide and protect the subscribed access under Article 6(1)(b) and (f) GDPR. Telegram processes data under its own terms; information sent to a bot may also be available to the bot operator. See the Telegram Privacy Policy. Telegram remains optional and does not affect access to protected website content.

8. Comments and ratings

Signed-in subscribers can post comments and ratings. The selected display name, currently first name plus family-name initial, rating, text and publication time are shown publicly. Account, IP and technical assignment data may be processed internally for moderation and prevention of abuse.

The legal bases are Article 6(1)(b) GDPR for the requested function and Article 6(1)(f) GDPR for platform safety and moderation.

9. Newsletter

If a newsletter is activated and requested, RED processes the email address, language, registration and confirmation times and delivery and withdrawal status. Delivery is based on voluntary consent under Article 6(1)(a) GDPR, which can be withdrawn at any time for the future. Until full activation, the existing form merely forwards a contact request.

10. Recipients and processors

Recipients may include hosting and email providers, Stripe, Telegram when voluntarily used, technical maintenance providers and tax or legal advisers. Authorities receive data only where required by law. Providers receive only the data required for their task and are contractually bound where necessary.

11. International transfers

Stripe, Telegram or technical services may process data outside the European Economic Area. RED then relies on a GDPR-compliant transfer mechanism, such as an adequacy decision, EU Standard Contractual Clauses or another permitted safeguard. Residual risks arising from foreign public-authority access cannot be fully excluded.

12. Retention

Data is deleted or anonymised once the purpose ends and no statutory retention or evidence obligation remains. Account data is generally retained for the contractual relationship and until payment, withdrawal and legal matters are concluded. Billing records remain for statutory periods. Contact requests are removed after completion and necessary evidence periods. Public contributions remain until deletion, anonymisation or a legitimate need to preserve the discussion.

13. Individual rights

Subject to the GDPR, individuals have rights of access, rectification, erasure, restriction, portability and objection. Consent may be withdrawn at any time for the future. A complaint may be filed with a competent supervisory authority; the lead authority will be named after the seat and legal form are final.

Requests can be sent to info@red-regeneration.org.

14. Security, automated decisions and updates

RED uses appropriate safeguards, including encrypted transmission, password hashing, role-based access, session and CSRF protection and separated configuration data. RED does not carry out solely automated decision-making with legal or similarly significant effects or related profiling.

This policy will be updated when functions, providers or RED's legal organisation change. The published version applies.