Last updated: October 16, 2026
Account data (name, email, role), profile data you choose to add (skills, work experience, resume, social links, wallet addresses you verify), content you create (job posts, applications, offers, messages, reviews), and technical data (IP address, browser, device, pages visited).
We use PostHog (EU cloud, servers in the EU) to understand how the product is used. This includes session replay: a reconstruction of your visits showing pages, clicks, and scrolling. Everything you type into input fields is masked and never recorded. During the early-access phase we review replays to find and fix usability problems.
Calendar views and settings, scheduling cards, pending-booking previews, and the scheduling composer are excluded from session replay, including event text and meeting-link attributes.
We use Sentry to collect crash reports (error details, browser, and the page where the error occurred) and Resend to deliver transactional email such as application updates, offer notifications, and job alerts you subscribe to.
Wallet addresses you verify and transactions you execute (escrow deposits, milestone releases, salary streams) are recorded on public blockchains, which are outside our control and permanent by design.
We do not sell your data. It is shared only with the processors named above (PostHog, Sentry, Resend), with our hosting provider (Fly.io), and with other users as the product requires - e.g. your profile is visible to companies you apply to, and your resume follows the visibility setting you choose.
Session replays are retained for 30 days; account data for as long as your account exists. Under the GDPR you can request access, correction, export, or deletion of your data. Contact us via the in-app feedback button or the email address you received as an early-access participant and we will respond within 30 days. Calendar connection data and meeting history follow the more specific retention rules below.
Connecting Google Calendar is optional. You can offer manual availability in Weeve without connecting a Google account. If you connect, Weeve accesses your Google account email, calendar names and identifiers, access roles, timezones, and events from the calendars you select. Event data can include titles, descriptions, locations, start and end times, meeting and calendar links, organizer and attendee email addresses and attendance responses, and event identifiers and metadata.
We use this information to show your private agenda, check scheduling conflicts, offer available times, and create, update, or cancel Weeve meetings in an owned calendar you select as a destination. Google may send invitations and updates to the meeting attendees when you take these actions. We do not request Gmail, contacts, or calendar-sharing administration access.
Your unrelated event titles, descriptions, attendee lists, and links are not shared with other Weeve users. Same-company availability sharing is optional and exposes free/busy or available slots, not private event details. Booking a Weeve meeting allows its participants to check mutual availability within the original offered windows when rescheduling. The meeting time, title, participants, and join link are shared with that meeting's participants.
Calendar events are fetched on demand for your agenda; Weeve does not keep a separate stored copy of your full Google agenda. We store your connection preferences, calendar selection, Google account email, granted permissions, and encrypted access and refresh tokens. We also retain Weeve booking records, including meeting times, participants, join links, and associated Google event identifiers, to operate the meeting and its conversation history. Google authorization attempts are stored to secure the connection process.
Disconnecting in Calendar settings removes the stored Google tokens, account email, granted permissions, and calendar selections, and turns off availability sharing. Scheduling preferences and existing booking and conversation history remain. Deleting your Weeve account removes the Calendar connection and authorization attempts, cancels unsent booking reminders, and erases their delivery email addresses. Meeting correspondence and booking metadata remain in other participants' history. Neither action deletes existing Google meetings or revokes the entire Google authorization grant; manage those meetings in Google Calendar and revoke access through your Google Account permissions. Tokens are retained until disconnection or account deletion. Calendar data is encrypted in transit, and stored OAuth tokens are encrypted at rest.
Weeve's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used only to provide or improve the scheduling and calendar features you use. We do not sell this data, use it for advertising, or use it to train generalized AI models. Transfers are limited to providing these features with your consent, security, legal obligations, or a business transfer with your prior consent. Human access is limited to your specific agreement, security needs, legal obligations, or permitted aggregated internal operations. Our hosting providers process this data on our behalf; Google Calendar content is excluded from PostHog session replay.
For Google Calendar support or requests about this data, contact kasper@weeve.xyz.