What we hold, and what we made a point of never holding.

ReserveCall exists to reserve a call payment before asking for someone’s time. That takes identity and payment information, and very little else. This page says what we collect, why, and who else sees it. It covers both sides: the requester who funds an invite and the recipient who takes the call.

What we do not collect

Worth stating before the list of what we do, because these are the answers people actually want.

• Not the call. No recordings and no transcripts. We read the times each side joined and left the room, and nothing else about what happened in it.
• Not your card or bank details. Those go to our payments provider, which is certified to hold them. They never reach our servers.
• Not your network. Signing in with LinkedIn lets us read your name, headline, and email. We never post, message, or connect on your behalf.
• No advertising trackers. We use PostHog for product analytics, not advertising, and do not share your activity for anyone else’s ads.

What we collect

From requesters. Your name, headline, profile link, and email from LinkedIn when you sign in. Your work email and company domain, and the result of checking one against the other. Everything you write into an invite: the topic, the length, the call payment, the times you offer, and the first name and email of the person you are sending it to. A record of each payment from our payments provider, meaning amounts, status, and a reference, not the card.

From recipients. The name and email you give when you book, the time you picked, and your acknowledgment that you read the terms and checked your employer’s policy. Join and leave times for the call. A record of the payout, and the account reference our payments provider gives back after you set up payout details with them directly.

From people who never book. If a requester sends you an invite, we hold the first name and email they gave us so the invite can reach you and be addressed to you. If you never book, that is all we ever have.

From everyone. Ordinary server logs from our hosting provider: IP address, browser, and timestamps. We use them to keep the service up and to spot abuse. PostHog also records pages viewed, referrers, clicks, scrolling, browser and device details, and a masked replay of how the site was used. Form input values are masked in those replays.

Why we use it

• To build, send, and display an invite, and to run the booking.
• To take payment, reserve the call payment for the invite, and release the payout or the refund.
• To decide claims. Join and leave times exist so a payout is settled on a record rather than on whoever argues harder.
• To verify a requester, so a recipient does not have to take a stranger’s word for who is asking.
• To send the email a booking needs: confirmations, reminders, reschedules, receipts, and payout notices.
• To prevent fraud and abuse, and to meet accounting obligations.
• To understand which parts of ReserveCall are useful, where people get stuck, and what needs fixing.

We do not sell your information, and we do not share it for anyone else’s advertising.

Who else sees it

The other side of your invite. A recipient sees the requester’s name, company, profile link, and, when completed, the relevant email or domain verification status, but not the email itself. Once a booking exists, the requester sees the recipient’s name and email, because they are about to meet. The requester never sees payout, bank, or tax details.

Our providers. A hosting provider runs the site. A database provider stores what is written here and keeps you signed in. PostHog provides product analytics. Our payments provider takes the funding, reserves the call payment, and sends the payout. Our video provider hosts the call and reports who joined and when they left. Each one receives only what its own job requires, may use it only to do that job, and may not use it for anything of its own. We will name any of them if you ask.

Nobody else, unless the law requires it, a legal claim makes it necessary, or the business is sold, in which case this policy travels with the data.

Where it is held, and for how long

We operate in the United States and our providers store data there. If you use ReserveCall from elsewhere, your information is transferred there.

Invites, bookings, attendance records, and payment records are kept as long as we need them for accounting, disputes, and fraud, which is typically seven years for anything a payment touched. Every funded invite creates a card authorization, even when nobody books it, so an expired invite remains in the requester's transaction ledger after its hold is released. Everything unrelated to a payment goes when your account does.

Security

Data is encrypted in transit and at rest. Internal access is single-sign-on and least privilege, so people reach what their job requires and no more. Card and bank details are held by a PCI DSS Level 1 payments provider rather than by us, which is the single largest thing we do for your security.

Your choices

Write to support@reservecall.com to see what we hold about you, correct it, get a copy, or have it deleted. We honor those requests wherever you live, not only where the law obliges us to. Some records survive a deletion request because accounting and fraud rules require it, and we will tell you which.

You can stop invite email at any time. Email about a booking you already made is part of the transaction and is not marketing, so it keeps coming until the booking is settled.

Children

ReserveCall is for people 18 and over. We do not knowingly collect anything from anyone younger.

Changes

When this policy changes, the date at the top changes with it. If a change affects what we collect or who sees it, we will say so rather than leave you to diff the page.

Contact

support@reservecall.com. The terms of service cover the money side.