Information we process
Booking records include the information needed to identify, prepare, and manage a session.
- Client name, email, WhatsApp, selected consultant, selected slot, duration, and language.
- Session intake notes such as goal, context, urgency, and links or artifacts shared by the client.
- Booking status, policy actions, confirmation-token state, payment status reference, and Beam room reference.
How booking data is used
Consulta uses booking data to provide the scheduling and handoff experience, not to sell unrelated advertising profiles.
- Show availability, create free-intro bookings, start paid-session checkout, and confirm sessions.
- Generate confirmation pages, calendar files, reschedule/cancel decisions, and support recovery.
- Record audit events so payment webhooks, retries, notifications, and policy actions remain traceable.
Usage analytics
Consulta uses Silvatech-hosted Rybbit analytics to understand aggregate page use and improve booking and workshop journeys.
- Analytics records page and referral trends without session replay, form-input capture, or stored IP addresses.
- Query strings are excluded and tokenized booking and workshop paths are masked before analytics storage.
- Analytics data stays on Silvatech-operated infrastructure and is not used to create cross-site advertising profiles.
Workshop advertising measurement
On public workshop pages only, Consulta offers an optional Meta Pixel measurement choice for understanding workshop advertising results.
- Meta code loads only after you select Allow measurement; choosing No thanks keeps it off, and the Ad privacy control on workshop pages lets you revise your choice.
- Allowed events are page view, public workshop view, successful interest, and checkout start. They may include the public workshop slug, price, and currency.
- Consulta does not send Meta your form entries, name, email, WhatsApp number, organization, role, registration or payment IDs, private tokens, checkout URL, payment status, or query string.
- Meta may use cookies or similar technology for measurement and advertising delivery. Tokenized attendee, payment, dashboard, account, and other non-workshop pages do not initialize this Pixel.
Payments
Payment is handled through Silvatech Payments links. Consulta does not collect or store card numbers, CVV, or bank credentials.
- Consulta stores payment IDs, amounts, currencies, status, checkout references, and webhook audit state.
- Paid bookings are confirmed only after a valid payment webhook.
- Refund and reschedule handling follows consultant policy data and provider records.
Notifications
Confirmation and reminder messages can be sent through the live SMTP and WOP transports when the specific message contract and worker are enabled.
- Notification records track channel, kind, recipient, status, timestamps, and provider references.
- Approved workshop templates and guarded reminders are active; other template families and optional workers keep separate gates.
- Client messages should point back to the same confirmation page so join, calendar, reschedule, and cancel actions are obvious.
Video and join links
Beam is the video component used by Consulta. Consulta avoids placing consulting notes, payment data, or policy records inside Beam.
- Beam receives room and join-token context needed to enter the browser video session.
- Tokenized join links are sensitive and should not be forwarded casually.
- Expired or invalid join links show a recovery path through WhatsApp 501-672-3021.
Booking links
Tokenized confirmation links can show session details and management actions without account login.
- Do not forward a booking or join link unless you want the recipient to access that booking or room.
- Support can recover a booking only with matching booking and contact information.
- Final rights, export, deletion, and retention operating details remain tracked in the Data Policy.
