Privacy Policy
Last updated: February 24, 2026
We handle your data responsibly.
You can participate in this online summit largely anonymously — you may use a pseudonym if you wish. However, you have the option to enter your correct details if you require an invoice. Below we have set out everything as clearly as possible. You can of course have your data deleted, and you can also have your account permanently deleted upon request.
We want this online summit to be genuinely helpful and to offer you an excellent learning experience. At the same time, we want to ensure that access to the platform and your data are kept secure in a responsible manner. The following is our official Privacy Policy, which also includes elements we are currently implementing. Further below, we have provided a transparent overview of the database fields used by the platform, including their purpose and how data is handled. We hope this gives you the clearest possible picture of how your data is managed responsibly.
---
Privacy Policy
Controller:
World Full of Solutions is an online summit brand of
One Healthy Future LLC, 1209 Mountain Road PL NE STE E, Albuquerque, New Mexico 87110, United States of America
Email: info (at) worldfullofsolutions.com
Website: https://worldfullofsolutions.com
This notice explains how we process personal data on this website and the connected services listed below.
Categories of Data & Sources
- Registration data: first name, email address, optional last name, address details (for invoicing only).
- Usage data: IP address, device/browser type, pages viewed, timestamps, referrers.
- Communication data: messages sent via forms or email.
- Newsletter/summit data: email address, double-opt-in (DOI) timestamp, engagement data (opens/clicks).
- Account data: login credentials, user role, activity status, video progress logs.
- Payment/order data: processed via Digistore24 (see below); we receive only booking confirmation, not full payment details.
Purposes & Legal Bases (GDPR)
- Operating the platform & security (server logs, essential cookies) – Art. 6(1)(f) GDPR
- Consent-based features (non-essential cookies, embedded media, analytics if activated) – Art. 6(1)(a) GDPR
- Summit registration & user account (providing the service) – Art. 6(1)(b) GDPR
- Newsletter (DOI, delivery, measuring opens/clicks) – Art. 6(1)(a) GDPR; withdraw anytime via unsubscribe link
- Contract / pre-contract (purchases, All-Access Pass) – Art. 6(1)(b) GDPR
- Legal obligations (tax, retention) – Art. 6(1)(c) GDPR
Website Hosting (All-Inkl.com)
This website is hosted by ALL-INKL.COM (Neue Medien Münnich), Germany. When you access the site, the provider processes server logs (IP address, timestamp, requested file, user agent, referrer) for stability and security. Logs are kept briefly and are then deleted. We have a data processing agreement (Art. 28 GDPR). Legal basis: Art. 6(1)(f) GDPR.
Summit Platform Software (TDB – Teile Deine Botschaft)
The software powering this online summit is provided by TDB – Teile Deine Botschaft, a brand of Elevation Group G.N.D LTD., Antoni Azina Street, Regina Gardens 1, B09, M06, 8015 Paphos, Cyprus, EU. TDB provides the platform software for user accounts, content access, and voucher management. TDB operates as a data processor on our behalf under a data processing agreement (Art. 28 GDPR). Note: user registration emails are handled directly via our own Brevo account (see below), meaning registrants are added to our email list, not TDB's.
Video Delivery (Bunny.net)
Summit interview videos are delivered via Bunny.net (EU-based provider with global CDN). For efficient delivery, your IP address and request metadata are processed; content may be cached at edge locations. Where data leaves the EEA, transfers rely on Standard Contractual Clauses (SCCs) or other appropriate safeguards. Legal basis: Art. 6(1)(f) GDPR.
Newsletter & Email Communications (Brevo)
Summit registration emails and newsletter communications are sent via Brevo with double opt-in. Brevo stores your email address and records your consent. Our communications may measure opens and link clicks to improve relevance. You can unsubscribe at any time (withdrawal of consent). Brevo acts as our processor under a Data Processing Agreement (Art. 28 GDPR); where processing involves countries outside the EEA, transfers rely on SCCs and appropriate safeguards. Legal basis: Art. 6(1)(a) GDPR.
Payment Processing (Digistore24)
For paid summit access (e.g., All-Access Pass), we use Digistore24 GmbH, St.-Godehard-Straße 32, 31139 Hildesheim, Germany, as our payment provider. Digistore24 processes the data necessary to complete payment transactions. We receive only a booking confirmation — we do not receive or store your full payment details (card numbers, bank details). Digistore24 may set cookies to track the origin of transactions. Legal basis: Art. 6(1)(b) GDPR (contract performance). For further details on Digistore24's data use, please see their privacy policy.
Summit Registration & User Account
When you register for the summit, you create a user account. The required fields are communicated during registration and are processed on the basis of Art. 6(1)(b) GDPR to provide summit access. User accounts are not public and cannot be indexed by search engines. When you delete your account, your data will be deleted subject to any statutory retention obligations. It is your responsibility to save any data you wish to keep before account deletion.
During registration and subsequent logins, we store your IP address and the timestamp of relevant actions, on the basis of our legitimate interests in protecting against misuse and unauthorized access. IP addresses are anonymized or deleted within 7 days.
Newsletter – Performance Measurement
Our summit and newsletter emails may contain a tracking pixel — a small file that is retrieved when you open the email. This retrieval provides technical information such as browser type, device, IP address, and time of access. This information is used to improve our communications and understand reading behavior (e.g., whether emails are opened, and which links are clicked). A separate opt-out from performance measurement is not possible; in this case the entire subscription must be cancelled.
Google Analytics
This platform may use Google Analytics, a web analytics service provided by Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Google Analytics uses cookies to analyze how users interact with the platform. The information generated (including your IP address, truncated to anonymize it) is transmitted to and stored on Google servers. Google will use this information to evaluate platform usage, compile reports on activity, and provide related services. We use Google Analytics only with IP anonymization activated, meaning your IP address is truncated within the EEA before transmission. The data generated is used for statistical purposes only and is deleted or anonymized after 14 months. Legal basis: Art. 6(1)(f) GDPR. You can prevent Google Analytics tracking by installing the Google Analytics Opt-out Browser Add-on. For further information on Google's data use, see Google's Privacy Policy and Google's ad settings.
Social Media Pages
We maintain pages on the following platforms. When you follow those links, the respective providers process data under their own policies. We do not embed social plugins that set cookies without your action.
- Instagram (Meta Platforms Ireland Ltd.) — Privacy Policy
- Facebook (Meta Platforms Ireland Ltd.) — Privacy Policy
- YouTube (Google LLC) — Privacy Policy
This summit also features outbound links to speaker websites and profiles on various platforms. Those third-party sites operate under their own privacy policies, for which we take no responsibility. Please review each site's policy individually.
Recipients & Processors
We share data with service providers strictly as necessary to operate the platform (hosting/TDB, video delivery/Bunny.net, email/Brevo, payments/Digistore24). These providers act under Art. 28 GDPR agreements.
International Transfers
Where processing involves countries outside the EEA, we implement safeguards such as SCCs and, where applicable, the EU–U.S. Data Privacy Framework, plus supplementary measures.
Retention
We retain personal data only as long as needed for each purpose. Newsletter data is retained until you unsubscribe. Account data is retained for the duration of your account, then deleted subject to statutory retention. Statutory retention periods (e.g., for invoicing and tax records) apply where legally required.
Security
We use appropriate technical and organizational measures including TLS encryption, access controls, and least-privilege principles to protect your data.
Your Rights (Art. 15–21 GDPR)
You have the right to request access, rectification, erasure, restriction, data portability, and to object to processing where applicable. You may withdraw consent at any time with future effect. You also have the right to lodge a complaint with a supervisory authority.
Updates
We may update this policy to reflect changes in our services or legal requirements. The current version is always published on this page.
Contact: info (at) worldfullofsolutions.com
---
Cookies
We use functional cookies necessary to operate the platform (session management, login status, language settings). Non-essential cookies (analytics, marketing) are only set after your consent via our cookie banner. You can manage or withdraw your cookie consent at any time via the cookie settings link in the page footer. Disabling cookies may affect platform functionality.
---
Transparent Database Field Overview
For complete transparency regarding how the TDB summit platform stores and processes your personal data in accordance with GDPR, we provide the following overview of database fields that contain or relate to personal data. We have translated and explained each field as clearly as possible. Please contact us if you have any questions — you can reference the item numbers below.
No. 01 | Table: Users
Field: Customer ID
Purpose: A unique identification number is assigned to each user to enable unambiguous identification.
Notes: Generated automatically upon registration.
Retention: Maximum 10 years after last update.
No. 02 | Table: Users
Field: Email
Purpose: The email address is required for registration and login. It is the primary identifier for a new registration.
Notes: Mandatory field. Must be confirmed during the registration process.
Retention: Maximum 10 years after last update.
No. 03 | Table: Users
Field: Password
Purpose: The password is part of the registration and login process. The combination of email and password enables identification as an authorized user.
Notes: Mandatory field. Stored encrypted to current standards. Can be changed at any time.
Retention: Maximum 10 years after last update.
No. 04 | Table: Users
Field: Remember Token
Purpose: This token is not used for authentication, but solely to detect and identify malicious software activity.
Notes: Security measure against malware.
Retention: Maximum 10 years after last update.
No. 05 | Table: Users
Field: Email Verification Token
Purpose: We store an email verification token to enable and secure the two-step registration process.
Notes: The token is sent to the user's email and also stored in the system; it is compared during email address validation.
Retention: Maximum 10 years after last update.
No. 06 | Table: Users
Field: Confirmed Status
Purpose: We store a status indicating whether an email has been verified. This is part of the background registration/login process.
Notes: Default value is 0; set to 1 upon email validation. Once verified, the verification prompt disappears on login.
Retention: Maximum 10 years after last update.
No. 07 | Table: Users
Field: User Role
Purpose: We assign user roles to registered individuals to manage access rights and permission levels. This role is also used in connection with the payment function.
Notes: Roles include Administrator, standard User, and Test User. Test Users have limited access, e.g. for trial or marketing purposes.
Retention: Maximum 10 years after last update.
No. 08 | Table: Users
Field: IP Address
Purpose: We store IP addresses to support identification and, in particular, to enable us to trace abusive or unlawful comments.
Notes: IP addresses are stored only in anonymized or truncated form in accordance with GDPR requirements.
Retention: Maximum 10 years after last update.
No. 09 | Table: Users
Field: Activity Status
Purpose: We store a status indicating whether a user, test user, or administrator is active or inactive. This allows temporary or permanent deactivation without deleting data — for example in the event of a failed payment or returned purchase.
Notes: Activation occurs automatically upon registration. Deactivation or re-activation can be carried out by the platform operator or administrator.
Retention: Maximum 10 years after last update.
No. 10 | Table: Users
Field: Referred-By Status
Purpose: This field supports the referral/recommendation function. It stores when a user was referred by another user, enabling recognition and potential rewards for successful referrals.
Notes: Part of the platform's referral functionality.
Retention: Maximum 10 years after last update.
No. 11 | Table: Users
Field: Deactivated At
Purpose: A timestamp recording when a user account was deactivated, to document this process.
Notes: Soft-delete: this is a deactivation, not a deletion of data.
Retention: Maximum 10 years after last update.
No. 12 | Table: Users
Field: Created At
Purpose: A timestamp recording when a user registered. Used for functions such as time-released content that becomes available at specific intervals after registration.
Notes: Created automatically at first registration.
Retention: Maximum 10 years after last update.
No. 13 | Table: Users
Field: Updated At
Purpose: A timestamp recording the time of the most recent change to a user record, for traceability.
Notes: Updated automatically whenever changes are saved.
Retention: Maximum 10 years after last update.
No. 14 | Table: User Meta Information
Field: First Name
Purpose: Collected during registration for personalized communication (e.g., personalized email greetings).
Notes: Used to address users individually in emails and other communications.
Retention: Maximum 10 years after last update.
No. 15 | Table: User Meta Information
Field: Last Name
Purpose: Optional field. Required only if the user wishes to receive an invoice.
Notes: Voluntary. Not required if no invoice is needed.
Retention: Maximum 10 years after last update.
No. 16 | Table: User Meta Information
Field: Company
Purpose: Optional field. Required only for invoicing purposes.
Notes: Voluntary. Can be left blank.
Retention: Maximum 10 years after last update.
No. 17 | Table: User Meta Information
Field: Phone Number
Purpose: Optional field. Required only if the user wishes to be contacted by phone for service matters.
Notes: Voluntary. Can be left blank.
Retention: Maximum 10 years after last update.
No. 18 | Table: User Meta Information
Field: Date of Birth
Purpose: Only activated on platforms where age verification (legal adult status) is required to access content.
Notes: Whether this field is mandatory depends on the content of the specific platform. Where not required, it is disabled in accordance with GDPR.
Retention: Maximum 10 years after last update.
No. 19 | Table: User Meta Information
Field: Address
Purpose: Optional field. Required only for invoicing purposes.
Notes: Voluntary. Can be left blank.
Retention: Maximum 10 years after last update.
No. 20 | Table: User Meta Information
Field: Postal Code
Purpose: Optional field. Required only for invoicing purposes.
Notes: Voluntary. Can be left blank.
Retention: Maximum 10 years after last update.
No. 21 | Table: User Meta Information
Field: City
Purpose: Optional field. Required only for invoicing purposes.
Notes: Voluntary. Can be left blank.
Retention: Maximum 10 years after last update.
No. 22 | Table: User Meta Information
Field: Country
Purpose: Optional field. Required only for invoicing purposes.
Notes: Voluntary. Can be left blank.
Retention: Maximum 10 years after last update.
No. 23 | Table: User Meta Information
Field: Login Counter
Purpose: The platform stores the number of logins to enable analysis of platform usage and to optimize the learning experience.
Notes: Incremented by one with each login.
Retention: Maximum 10 years after last update.
No. 24 | Table: User Referrals
Field: ID
Purpose: An automatic identification number for each referral, enabling the referral process to be traced and any rewards to be processed.
Notes: Part of the referral functionality.
Retention: Maximum 10 years after last update.
No. 25 | Table: User Referrals
Field: First Name
Purpose: The first name of the referred person is collected so they can be addressed personally.
Notes: Part of the referral functionality.
Retention: Maximum 10 years after last update.
No. 26 | Table: User Referrals
Field: Last Name
Purpose: The last name of the referred person is collected to ensure uniqueness and avoid duplicate referrals.
Notes: Part of the referral functionality.
Retention: Maximum 10 years after last update.
No. 27 | Table: User Referrals
Field: Email
Purpose: The email address of the referred person is collected so they can be contacted as part of the referral process.
Notes: Part of the referral functionality.
Retention: Maximum 10 years after last update.
No. 28 | Table: User Referrals
Field: Access Token
Purpose: A token is generated and stored server-side, then sent to the referred new user, granting them a test or trial access to the platform before deciding whether to purchase.
Notes: Part of the referral functionality.
Retention: Maximum 10 years after last update.
No. 29 | Table: User Referrals
Field: Referral Accepted Token
Purpose: A token recording whether a referral was successfully redeemed, enabling any rewards to the referring user to be triggered.
Notes: Part of the referral functionality.
Retention: Maximum 10 years after last update.
No. 30 | Table: User Video Logs
Field: User ID
Purpose: The User ID is automatically associated with each video lesson accessed, enabling tracking of which user accessed which content.
Notes: Core functionality for video lesson access.
Retention: Maximum 10 years after last update.
No. 31 | Table: User Video Logs
Field: Chapter ID
Purpose: The chapter (first level of content structure) a user has viewed is stored to improve the learning experience — for example, to resume from the same point on next login, and to show progress indicators.
Notes: Content is structured into chapters, lessons, and modules.
Retention: Maximum 10 years after last update.
No. 32 | Table: User Video Logs
Field: Lesson ID
Purpose: The lesson (second level of structure) a user has viewed is stored for the same purposes as the Chapter ID.
Notes: Part of the core video lesson functionality.
Retention: Maximum 10 years after last update.
No. 33 | Table: User Video Logs
Field: Module ID
Purpose: The module (third level of structure) a user has viewed is stored for the same purposes as the Chapter and Lesson IDs.
Notes: Part of the core video lesson functionality.
Retention: Maximum 10 years after last update.
No. 34 | Table: User Video Logs
Field: Is Completed
Purpose: This field records whether a user has watched a lesson or module video in full, enabling a completion indicator (green checkmark) to be displayed, giving users a quick overview of what they have and have not yet watched.
Notes: Part of the progress-marking functionality.
Retention: Maximum 10 years after last update.
No. 35 | Table: User Video Logs
Field: Current Time
Purpose: The current playback position within a video is stored to enable resume functionality and improve the learning experience.
Notes: Part of enhanced learning experience functionality.
Retention: Maximum 10 years after last update.
No. 36 | Table: User Video Logs
Field: Duration
Purpose: The total duration of a video is stored to enable time calculations and support progress-related functions.
Notes: Part of enhanced learning experience functionality.
Retention: Maximum 10 years after last update.
No. 37–42 | Table: Vouchers
Fields: Voucher ID, Voucher Count, Voucher Code, Valid From, Valid Until
Purpose: These fields manage voucher/coupon codes that allow free or discounted access to the platform. Each voucher has a unique code, a defined number of redemptions, and a validity period. Vouchers can be created and managed by the platform operator.
Notes: Part of the voucher/coupon functionality.
Retention: Maximum 10 years after last update.
No. 43–51 | Table: Administrator Settings
Fields: Platform Name, Platform Abbreviation, Logo, Text Color, Button Color, Admin Password, Admin Email, Minimum Password Length, Payment Method
Purpose: These fields store the configuration settings for the platform as set by the administrator, including branding, security settings, and payment method.
Notes: Part of the administrator settings.
Retention: Maximum 10 years after last update.
No. 52–56 | Table: Comments
Fields: User ID, Comment Text, Chapter ID, Lesson ID, Module ID
Purpose: These fields enable the commenting functionality within the platform. Comments are associated with specific users and specific content locations (chapter/lesson/module). Users may only edit or delete their own comments.
Notes: Part of the comment functionality.
Retention: Maximum 10 years after last update.
No. 57 | Table: Payment System
Field: All Fields
Purpose: For payment transactions, this platform uses a secure payment provider (Digistore24) so that minimal payment data needs to be stored on our own servers. Working with a professional payment provider ensures legally compliant and GDPR-conformant payment processing.
Notes: Part of the payment functionality. See the Digistore24 privacy policy for details.
Retention: Maximum 10 years after last update.