Your day stays yours.
DayPerch is operated by RecRivals LLC, 3488 N Andrews Ave, Fort Lauderdale, FL 33309, United States. Contact support@dayperch.com about your information. Last updated October 31, 2026.
DayPerch is currently a preview. Account creation, persistent calendar connections and live payments remain closed while the product is tested. Poll respondents may use the limited calendar-check beta described below.
Your account and appointments
We store your name, verified email, availability settings and appointments created through DayPerch. A public booking page shows the host name, meeting details and available times the host chooses to share. It does not show private calendar event titles. Guests verify their email without creating an account. A scheduling poll stores the answers participants choose to submit; the poll explains whether results are shared.
Google user data
When you connect Google Calendar, DayPerch accesses your account identity and email address, your calendar list, free/busy information, and the events it creates for your bookings. We use these to identify the connected account, let you choose calendars, avoid scheduling conflicts, and create, reschedule or cancel your DayPerch appointments. We do not change unrelated events. Calendar access does not require Gmail access.
Authorization tokens are encrypted at rest and scoped to your account. Calendar lists and free/busy information are requested to provide scheduling; private event details are not published to guests. Disconnecting removes stored authorization credentials immediately and pauses affected booking pages. Existing appointments remain unchanged, and a request already in progress may finish. You can also revoke access in your Google account connections.
DayPerch does not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. We share it only as needed to provide the features you request, with service providers acting for us, or as legally required. Human access is limited to your consent, security investigations, or legal obligations. We complete requests to delete other connected-account data within 30 days, subject to the separate appointment, billing and legal-retention limits below.
DayPerch's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Microsoft user data
When you connect a Microsoft work, school or personal account, DayPerch accesses your account identity and email, calendars, availability, and calendar events needed for scheduling. We use delegated calendar access to list your calendars, check conflicts and manage appointments created through DayPerch. We do not change unrelated events. The initial calendar connection does not need permission to read or send mail.
Microsoft authorization tokens are encrypted at rest and removed when you disconnect. Revoke the provider grant separately in Microsoft account permissions for a personal account, or My Apps for a work or school account. Your organization may control the permissions it allows. The same purpose limits, 30-day deletion-request policy and retention exceptions apply as for Google. Microsoft user data is not sold, used for advertising, or used to train generalized AI or machine-learning models; human access is limited to consent, security or legal needs.
Private calendar checks for poll respondents
Checking your calendar on a poll is optional. If you already use DayPerch, we check your existing selected calendars only after confirming your sign-in and that the invitation address belongs to your own connected account. A forwarded personal poll link alone does not reveal calendar conflicts. You may briefly visit the signed-in DayPerch mailbox domain to confirm your session.
During the Google and Microsoft beta, eligible respondents can connect the calendar matching their invitation address for a one-time check. Google provides primary-calendar free/busy times. For Microsoft, we request only event start and end times, cancellation, availability and response status from your primary calendar; we do not request event titles, descriptions, locations or attendees. Access is read-only. Work or school accounts may require their organization’s approval.
These one-time checks do not create a connected account. Provider access tokens are used in memory for the check and then discarded; we do not retain refresh tokens or save the calendar data in the poll. Essential encrypted session cookies bind the consent request to your browser; consent requests expire after ten minutes. A result passed between the response page and the signed-in mailbox contains only the affected poll-slot identifiers, is encrypted, bound to your original browser and poll, and expires after five minutes. The displayed busy markers remain only in the response page for that session.
The organizer receives only the answers and comments you explicitly save, never your calendar events or busy markers. Calendar checks never select or save answers for you. You can answer manually without connecting. A future Free-account signup offers a separate, explicit account connection; a one-time check is not silently upgraded to persistent access. Provider consent may remain listed in your Google or Microsoft account until you revoke it using the links above.
Optional inbox summaries
Inbox access is a separate, optional feature. It is not part of the calendar-first launch permissions. If enabled and separately authorized, DayPerch reads up to 20 unread-message headers per inbox on refresh to summarize counts, age and frequent senders. It does not read message bodies, send or modify mail, or upload messages to an AI service. Headers are processed for the current page rather than stored as a digest. Google inbox access remains unavailable for public use until restricted-scope verification is complete.
Payments
Free includes one connected account without a card. Pro is USD $3 per month for up to three connected accounts, plus USD $1 per month for each extra, when paid signup opens. RecRivals LLC uses Stripe for checkout and billing. Stripe receives card details; DayPerch does not store card numbers. Deleting a DayPerch account does not silently cancel or change a subscription. See our Terms of Service.
Essential storage and retention
Essential cookies keep you signed in and let you manage an appointment. Sessions last up to seven days; verification links expire after 30 minutes, calendar-consent requests after ten minutes, and guest verification after two hours. Verification and session tokens are stored as hashes. Request records use keyed hashes instead of raw IP addresses.
Private appointment links expire 30 days after the appointment's current end time. Anyone with that link can manage that appointment within the host's rules, so keep it private. Opening it sets an essential two-hour management cookie.
When accounts are open, daily housekeeping removes expired verification, session and guest records after a 24-hour grace period, and rate-limit records older than 24 hours. Disconnect removes provider credentials immediately. A disconnected account label, calendar references in existing appointments, and booking or billing records may remain to support existing appointments, resolve disputes or meet legal obligations. They are not silently deleted by disconnect or routine cleanup. Support handles deletion requests and explains any records that must be retained.
Access, correction and deletion
You can disconnect a provider in Connections and delete an unused account from your account page. If the account has appointment or billing history, contact support@dayperch.com to arrange deletion and handle protected records or an active subscription separately. Automated account deletion refuses to change those records. We will explain any necessary retention and complete the eligible deletion within 30 days.
Material changes to these practices will be disclosed before we use connected-provider data for a new purpose. See current launch availability and our Terms of Service.