icohub

Privacy Policy

Last updated 2026-10-16

This Privacy Policy describes how YINFLOW LTDA, CNPJ 42.516.954/0001-00, with registered address at Av. Paulista, 1636, Sala 1504, Cerqueira César, São Paulo - SP, 01310-200 ("YINFLOW", "we", "us"), collects, uses, and protects the personal data of users of the icohub platform (the "Platform"). This Policy is written to comply with Federal Law 12,965/2014 (Marco Civil da Internet) and Federal Law 13,709/2018 (LGPD — Lei Geral de Proteção de Dados Pessoais).

1. Who we are

icohub is a graph-native life-mapping tool operated by YINFLOW LTDA, and a marketplace that connects Patients with independent Professionals for scheduling and holding paid sessions. This policy explains what personal data we process and why.

2. End-to-end encryption

Maps and spaces are end-to-end encrypted. Everything you create in a map or a space — cells, notes, and the connections between them — is encrypted on your device before it is sent anywhere. Our servers store only encrypted data that we cannot read. No third party receives the content of your maps or spaces. The one exception is AI chat: by default, the content of a chat message you choose to send to an AI provider (Section 6) passes through our servers unencrypted so the provider can read and reply to it, and our servers do not store it. If you use the desktop app's local Claude Code option instead of our default (Section 6), that content goes directly from your device to the provider and does not pass through our servers, except when that option falls back to our default path.

3. Our role, and the Professional's role

For account, booking, and payment data, YINFLOW is the controller. For the content of a session — notes a Professional writes about a session — the Professional who provides the session is the controller: those notes are written and kept by the Professional, end-to-end encrypted, and readable only by that Professional. YINFLOW stores the encrypted data but cannot read it and is not the controller of its content.

4. What we collect

  • Account data: your email address, used to sign you in via one-time codes.
  • Your content: the maps, cells, notes, and chat transcripts you create. This content is end-to-end encrypted — we store it, but cannot read it (Section 2) — except chat content you send to an AI provider, which our servers do not store at all.
  • Booking and payment data: if you book a session, the Professional and time you booked, your Booking history, and payment metadata (not your full card number, which Stripe processes directly — see Section 7).
  • Session notes (Patients of a Professional): notes a Professional writes about your session are end-to-end encrypted and readable only by that Professional, as described in Section 3.
  • Voice (optional): when you use voice features, in the browser or the desktop app, microphone audio is processed to transcribe speech and generate replies.
  • Calendar data (Professionals only): if a Professional connects their Google Calendar, we read and write calendar events needed to keep their availability accurate and to hold a confirmed session.
  • Live session audio and video: during a Session, audio and video are transmitted through Cloudflare RealtimeKit. We do not record Sessions — no audio or video persists on our servers. Speech-to-text transcription of a Session runs locally on the Professional's desktop app device, never on our servers.
  • Technical data: logs and request metadata needed to operate and secure the service.

5. How we use your data

To authenticate you, to provide and synchronize the service across your devices, to process your Bookings and payments, and to power AI-assisted features you invoke. We process account, content, and booking data to perform our contract with you; where AI features are optional, we process the data they use based on your consent when you choose to use them. We do not sell your personal data and we do not use your content to train AI models.

6. AI features and subprocessors

When you use AI features, the relevant content and prompts are sent to an AI provider so it can respond. The default provider is Google (Gemini), reached through Cloudflare's AI Gateway. If Gemini is unavailable, chat falls back to Cloudflare Workers AI. Chat sends the parts of your map and messages the provider needs to answer you; voice and dictation run directly between your device and Gemini Live, with our server issuing only a short-lived token. In the desktop app, you may opt into running Claude Code locally instead of our default; that sends content directly from your device to Anthropic (Claude), not through our servers, except when it falls back to our default path (for example, when sending files, or if the local process cannot run). AI providers receive only the content you choose to send them when you use an AI feature, and that content is necessarily readable by the provider to generate a response. These providers process your data under their own terms: Cloudflare, Google, and Anthropic.

7. Sharing and third parties

We share data only with the subprocessors needed to run the Platform:

  • Cloudflare — hosting and infrastructure, including the AI Gateway, the email service that sends your sign-in code, and RealtimeKit for live session audio/video.
  • Cloudflare Workers AI — the fallback AI provider for chat when Gemini is unavailable.
  • Google (Gemini) — chat, voice, and dictation; Google Calendar — for Professionals who connect their calendar.
  • Anthropic (Claude) — AI features in the desktop app.
  • Stripe — payment processing. Stripe acts as an independent controller for the card and payment data it processes directly; see Stripe's privacy policy.
  • Resend — delivery of notification emails (not your sign-in code).
  • OneSignal — delivery of push notifications.
  • GitHub — when you use "Notify our team" to report a problem, we file a support issue in our private issue tracker on GitHub. The issue carries only your user id — never your email — and only structural ids (map and cell ids, the tool name, and an error class) plus a one-way hash of the error message; it never contains the content of your maps or messages. The issue is visible to our team and the automated tools that help us triage it.

We do not sell your data. We may disclose data if required by law, to comply with a judicial or regulatory order, or to protect our rights, users, or the public.

8. International data transfer

Some of our subprocessors are based outside Brazil. We only transfer personal data internationally under safeguards that meet the requirements of the LGPD (Law 13,709/2018, Art. 33).

9. Storage and security

Data is hosted on Cloudflare infrastructure (Workers, D1, R2, Durable Objects). As described in Section 2, map and space content is end-to-end encrypted; our servers store only opaque encrypted data that we cannot read. This end-to-end encryption does not extend to content you choose to send to an AI provider (Section 6) — that content is necessarily readable by the provider to generate a response. We use industry-standard measures to protect your data, though no method of transmission or storage is completely secure.

10. Data retention

We keep your account and content for as long as your account is active. When you delete your account, there is a 30-day grace period before deletion takes effect; you can export your encrypted content at any time before then. Once the grace period ends, your encrypted content is erased and — because it was end-to-end encrypted — cannot be recovered by anyone, including YINFLOW. Other content you delete without closing your account is removed from our active systems within 30 days, except where we must keep it longer to comply with a legal obligation. In particular:

  • Booking and payment records underlying our contracts with Professionals and payment processors are kept for 5 years after account deletion, as required by law, with your identifying information unlinked from the deleted profile where the Booking record itself must be kept.
  • Session notes are kept by the Professional according to their own professional record-keeping obligations; YINFLOW does not independently retain a readable copy, as described in Section 3.

11. Your rights

Under the LGPD (Art. 18) and depending on where you live, you have the right to confirm the existence of processing, to access, correct, anonymize, port, or delete your personal data, to be informed about the entities with which we share your data, to withdraw consent, and to object to or request review of certain processing. To exercise any of these rights, email ops@yinflow.life and we will respond within a reasonable time.

12. Cookies

We use cookies and similar technologies necessary to operate the Platform — including to keep you signed in — and, where applicable, to understand how the Platform is used. You can control cookies through your browser settings; disabling them may affect Platform functionality.

13. Children

The Platform is for adults only — it is not directed to anyone under 18, and we do not knowingly collect personal data from children. If you believe a child has given us their data, contact us and we will delete it.

14. Changes to this policy

We may update this policy; material changes will be reflected in the "last updated" date above and, where legally required, we will seek your renewed consent.

15. Governing law and contact

This Policy is governed by the laws of Brazil. In case of any divergence between this English version and the Portuguese version of this Policy, the Portuguese version prevails. Questions about this policy or your data: ops@yinflow.life.