Privacy & cookies · Updated 30 September 2026

Your privacy matters.

This notice describes the website’s consultation booking service and optional consultation progress measurement.

Your discovery-call answers

The form asks about community platforms, member count, recurring revenue range, team size, needs, collaboration preference, call platform, the contact needed for that platform, and your timezone and selected time. Answers stay in temporary page memory until submission. The booking service then stores them encrypted to arrange the call. You can use a Telegram or Discord username without providing an email or creating an account. Qualification does not decide whether you may book, and no payment is required.

Available times come from the server. Selecting a time does not reserve it. The interface reports a confirmed appointment only after the booking service confirms it. Automatic operator messages, customer messages and external calendar invitations are currently disabled. The operator arranges call details manually.

Individual consultation links

An individual link contains a random invitation token. The server protects its internal contact reference and label with encryption. It never returns those details or previous answers to a visitor. The link provides attribution only: it does not sign you in or let you manage a booking. Anyone may forward it, so a link does not verify the visitor’s identity. A booking submitted through an active link is associated with that invitation. An invalid, expired or revoked link still opens the general form without invitation attribution.

Optional consultation progress

Optional booking progress uses the analytics choice in Cookie settings. It stays off until you choose “Accept optional” or enable “Analytics, including booking progress” and save your preferences. The server receives versioned event identifiers, step numbers, safe validation/error categories, timestamps and estimated active intervals. Individual-link observations are associated with the invitation’s internal reference for the private administrator view. No field answers, revenue selections, contact identifiers, text typed, recordings, raw query strings or raw IP addresses are included in these events. No advertising or third-party analytics provider receives them.

We observe opens only from a visible form after consent, and starts only after deliberate interaction. Page requests, previews and HEAD requests do not count as starts. Active time pauses while the page is hidden or after 60 seconds without interaction; intervals are capped at 15 seconds. It is an estimate, not exact attention. A new session starts after 30 minutes without interaction. An inactive session does not establish permanent abandonment.

Your cookie choice lasts up to 180 days. Booking progress uses a separate server receipt valid for at most 24 hours in this tab; it is renewed only while your current analytics choice still allows it. Use “Reject optional”, or disable analytics and save, in Cookie settings to stop tracking and remove earlier progress observations. If removal fails, tracking stays off and a revocation request is retained for retry. Declining or withdrawing never prevents booking. We do not buffer activity before consent, reconstruct it later, fingerprint visitors or bypass blockers.

Browser storage

Cookie preferences are remembered for up to 180 days. Earlier website-only preferences require a fresh choice for the combined analytics notice. Website-wide analytics and replay adapters remain disconnected. Consultation consent credentials and non-personal journey IDs, counters and activity timestamps use this tab’s session storage for at most 24 hours. Booking answers are never saved there. A separate, temporary booking-recovery credential allows this tab to check a submitted request after a refresh or lost response; it is separate from invitation links and expires after 24 hours. Clearing browser data removes these local credentials. No cross-device draft recovery is provided.

Retention and deletion

Consultation progress sessions and their events are deleted after 90 days without observation. Withdrawal deletes those observations sooner. Invitation mappings are deleted after 180 days from creation, including their linked progress; invitations default to 30-day expiry and cannot exceed 90 days from creation. Administrators can revoke a link immediately or erase its protected mapping and progress through the authenticated deletion endpoint. Aggregates are calculated from retained records, so deletion also removes their contribution.

Booking records are separate from optional analytics. Unconverted requests are subject to the existing 180-day deletion job; confirmed or cancelled booking retention requires an operator retention decision. Authorized booking deletion removes protected answers, credentials and linked progress. Encrypted rolling backups can retain an earlier copy until replaced; recovery procedures must apply deletion records before returning restored data to service.

Access and infrastructure

Private invitation, contact, booking and progress information requires an authorized administrator with MFA. Hosting infrastructure necessarily receives technical connection information to serve and secure the site; its exact access-log policy remains to be documented. Invitation pages use no-store, noindex and no-referrer controls, and application logs use route templates instead of tokens or payloads. Choosing a call platform does not send information to that platform automatically. Following an external link is subject to that service’s privacy terms.

Choices and requests

You can book without optional tracking, withdraw booking progress consent through Cookie settings, and clear browser data. The operator must replace the example privacy contact above with a working route for access, correction, deletion and other privacy requests. This page does not claim verified legal compliance.