How Araflo handles your data

Last updated October 7, 2026. Covers the Araflo web platform, Aracalend booking, Araflo Meet (Android, iOS, and web at meet.araflo.com), and the /support contribution page.

Who this covers

Araflo is a business platform for wellness practitioners, solo business service providers, and small businesses. "Practitioners" or "merchants" are the business owners who sign up for Araflo — whether that's a wellness practitioner, a solo service provider, or a small business team. "Clients" are the people who book sessions with a practitioner through Araflo. This policy applies to all of them, and "practitioner" is used throughout as shorthand for any of these account types.

What we collect

Account data: name, email, and business details a practitioner provides when signing up.
Client intake data: whatever a practitioner's intake form asks for (name, email, phone, session notes) — this belongs to the practitioner, not Araflo; we store it on their behalf.
Payment data: card numbers never touch our servers. All payments run through Stripe, which tokenizes cards. We store transaction amounts, dates, and status — never raw card numbers.
Meeting media: Araflo Meet requests camera and microphone access to let you participate in a meeting. Meeting audio and video can be transmitted between participants and through Araflo's self-hosted meeting infrastructure. Screen shares, shared video and Blackboard content can also be visible to meeting participants.
Calendar (mobile app only): if you grant calendar permission, Araflo Meet can show your upcoming meetings and let you add a session to your device calendar. This stays on your device — Araflo does not upload your calendar to our servers.
Name and contact info (mobile app, first launch only): before you can use Araflo Meet, we require your name once, at first launch, plus either an email or a phone number (whichever you have — we don't require both, since not everyone has easy email access). A location field is also offered but is entirely optional. Unlike calendar data, this is sent to and stored on Araflo's servers as a contact record. Araflo's team receives a notification containing these details and may use them to follow up about Araflo services. This information is not needed for a particular meeting. You can request its deletion by contacting us.
Usage data: standard server logs (IP address, timestamps, error reports) used for security and debugging, kept only as long as needed for that purpose.

What we don't do

We don't sell your data.
We don't use advertising trackers or an advertising ID — Araflo Meet has no ads.
We don't share client data across practitioners — each practitioner's client list is theirs alone.

Video calls and Araflo Meet

Araflo Meet is built on Jitsi Meet, self-hosted by Araflo at meet.araflo.com — not the public meet.jit.si service. Booking-generated room links use random identifiers and do not include the client's name. A person creating or sharing a custom room link controls its room name. Calls can be peer-to-peer or relayed through Araflo's meeting infrastructure.

Blackboard drawings are shared with participants in the meeting through the collaboration service. A moderator can hide the Blackboard for participants, and each participant can hide it on their own screen. Hiding changes what is displayed; it does not itself erase the drawing or the collaboration details needed to reopen the board in that meeting.

Meeting recordings

The web version can let a participant start a local recording after choosing the meeting browser tab for capture. Depending on the selected option, that recording can include the meeting view, other participants' audio and video, screen shares, shared video and visible Blackboard content, or only the recorder's own media. The completed file is downloaded to the recording participant's device. Araflo does not receive or control that local file merely because the participant uses this feature. The person recording is responsible for giving required notice, obtaining any required consent, and protecting and deleting their copy. Other participants may not be able to determine whether a separate device or browser tool is recording the meeting.

Server-side recording in the Android app is not currently available. If Araflo later enables server-side recording, we will describe its storage location, access, retention, deletion and participant notices before making it available.

Third parties we use

Render — hosting for the main Araflo website and API.
Hetzner — infrastructure hosting for Araflo Meet.
Stripe — payment processing (Stripe's own privacy policy applies to payment data).
Resend — transactional email (booking confirmations, receipts).
Anthropic (Claude) — powers Ara, the in-app business assistant; a practitioner's own business data is sent to generate responses to their questions.

Data retention and deletion

Practitioners can request deletion of their account and associated client data at any time by emailing info@araflo.com. Clients can request the same by contacting the practitioner they booked with, or Araflo directly.

For deletion instructions, see Data Deletion. Browser-local meeting recordings are retained on the recorder's device according to that person's choices, not an Araflo server retention schedule.

Children

Araflo is a business tool for adults running or booking professional services. It is not directed at children under 13, and we do not knowingly collect data from them.

Changes to this policy

If this policy changes materially, we'll update the date at the top of this page.

Contact

Questions about privacy: info@araflo.com

Back to Araflo