Privacy, in plain language
Restricted access is useful. It is not a promise of absolute confidentiality.
RA Commons collaborator office hours (Cal.com)
This section covers the separate Cal.com-connected RA Commons office-hours service; IDEA Office Hours is covered below. Office-hours invitations grant access only to their program, without creating community membership or private-room access. Hosts connect Cal.com to their calendars and Zoom or Google Meet. We store the host profile, invitation email, encrypted connection credentials, published office-hour rules, appointment details, matching requests, attendance and optional feedback. Your name, email, timezone and appointment question are shared with Cal.com and the host. We do not store private calendar event descriptions. Recording and transcription are off for the pilot. You can download your office-hours data and remove program access after cancelling upcoming appointments. Removal clears credentials and sessions; coordination records remain. Completed, cancelled and failed appointment names, emails, questions and meeting links are cleared after 90 days; unresolved appointments remain for support. Provider records follow the provider and collaborator's own retention. Contact [email protected] about roster data or deletion requests.
What members can see
Approved global members can see Global Commons posts, replies, and member profiles. Private room posts, replies, reactions, bookmarks and search results require membership in that room. A matching confirmed work domain allows automatic room joining; other requests need a private review. Shared university and research-network domains identify institution-wide rooms, not a specific lab or office. Room request notes are visible to authorized reviewers. Rooms open without an automatic first-joiner steward. A nominee must accept and another approved room member must confirm; existing appointments remain, and platform stewards handle appeals. Your chosen display name and unique @handle are visible to approved members. If you have not chosen a display name, your registration name is shown. Organization, role, and country/office are also visible to approved members. Even with a display name, these details can identify you in a small office; this is not anonymous posting. Choosing a new name does not remove names or clues you previously typed into posts and messages. Profiles never expose email addresses or verification details. Mentions and reply notifications follow the original conversation’s audience and never grant room or chat access. Conversations are restricted to their participants; moderators can inspect a specific reported message. Blocking hides each person’s content and stops access to their conversation.
Information you must not share
Sharing any organization’s secret, private or confidential information or documents is not allowed anywhere on RA Commons, including private rooms, messages and Global Commons. This includes internal files, restricted findings, financial or personnel records, credentials, and identifiable research participant data. Share general lessons and resources that are already public instead. Room-admin approval never overrides this rule.
Who else can access content
Messages and attachments are encrypted, but RA Commons stores a protected copy of account recovery keys. Authorized platform and infrastructure operators with access to those keys can decrypt stored messages and attachments. Ordinary sign-in restores messages on new browsers after account recovery is enabled. Older history requires a usable key from an original browser or recovery key; already-lost keys cannot be reconstructed. Conversation membership, timestamps and device records are retained for access control. Members can copy or screenshot content. No analytics or third-party AI processes private message content. Do not share confidential organization or research-participant information.
Sharing from a private room
A room post never becomes global automatically. Its author may prepare a separate draft for a room admin to approve; the submitted version is fixed for review. Another admin must review an admin's own draft. Approval publishes that exact draft as a separate Global Commons post credited to its author; the original post, replies, reactions, and review notes stay in the room. A published draft remains visible to global members even if the author later leaves the room or the source is hidden. Report the global copy separately if it needs moderation. Authors must remove private context and references to other people without their agreement. Approval never permits sharing organization secrets or private or confidential information or documents.
What we store
Our sign-in provider processes your login email, sign-in information, first and last name, organization, declared current research role, and country/office you enter during registration. Our community database stores your confirmed sign-in email, approximate last activity time, private registration name, optional public display name, role, organization, country/office, optional introduction and profile photo, current and previous handles, application and membership status, administrator dashboard layouts and administration-access records, along with room requests, admin and consent nominations, acceptance and confirmation records, discussions, messages, reply references, mentions, notifications and their read status, bookmarks, chosen recommendation topics, hidden-feed preferences, reaction choices, public opportunity listings and saves, blocks, reports, sharing drafts and review decisions. Profile photos are cropped and resized; feed images are resized and normalized, and image metadata is removed before storage. Feed images inherit the post’s audience, including organization-room restrictions. Unpublished image uploads expire after 24 hours; deleting a post removes its active feed images. Chosen topics and public community activity guide recommendations; viewing history is not used. Work-email verification keeps the approved domain, verification time, and a protected fingerprint of the email to limit reuse. It does not keep the full work email. One-time codes are stored in a protected form, expire after ten minutes, and are removed after successful verification.
Evidence and retention
Profile URLs and free-text application notes are cleared after automatic admission or a membership decision. Confirmed domain, institution mapping, email fingerprint, automatic admission and room-join events, reviewer decisions and timestamps remain to support membership integrity. Expired verification entries and unused invitations may remain until cleared. Posts, messages, mentions, notifications and moderation history remain until an operator handles a deletion request. Previous handles stay reserved to their owner while the account exists; earlier mentions retain their text and link to the same identity after a handle changes. Room request notes are cleared after a membership decision or automatic joining. Sharing drafts and admin nomination/decision records remain for review until an operator handles deletion. Replacing or removing a photo removes the previous active image; older backups may contain it. Write to [email protected] about access, correction, deletion, or backup retention. These requests are handled individually rather than through automatic account deletion.
Providers and browsing
Supabase provides managed authentication. Community content and profile photos stay in our PostgreSQL database; our email provider delivers verification codes and a membership welcome email to your confirmed sign-in inbox. The welcome includes your first name. We keep delivery timestamps and retry counts without tracking email opens. Private member content is not sent to analytics or AI providers. Platform administrators can view aggregate membership counts and Global Commons contribution totals, with small groups omitted. A separate private member directory lets platform administrators who complete a security check see registration and display names, sign-in emails, organizations, membership status, join dates and approximate last activity. Directory access is recorded. Last activity records an authenticated app request at most once every 15 minutes; it is not a live online indicator and does not record page history. Sign-in emails are updated when you use the app and are not shown on member profiles. These statistics use existing records; we do not add browsing trackers. Shared links show locally generated URL cards; no external preview or avatar service is used. Opening an external link exposes normal browser connection information to that website.
Registration reminders
If you chose work-email verification but have not completed it, we send a reminder to your confirmed sign-in email after two days and a final reminder after seven days. Older unfinished registrations receive the first reminder after this feature is enabled, with at least five days before the second. Reminders stop after work-inbox confirmation, membership approval, or switching to private review. They do not send a verification code or use the full work address. We retain private delivery timestamps, attempt counts and short-lived delivery leases; messages contain a sign-in link, without tracking pixels. Delivery failures retry at most three times per reminder, at least a day apart. You can ignore the reminders if you no longer wish to join.
Email activity reminders
After 24 hours away from the foreground app, members can receive one combined email per day about new posts or replies in their organization rooms and unread private messages. These reminders are enabled by default and can be disabled separately in account settings. Emails contain aggregate counts and app links, not private text, sender names or room names. Muted message conversations are excluded. We retain the latest foreground activity time, latest room visit, private message read marker, reminder preferences and delivery metadata for this purpose; these are not exposed as a public last-seen history. The optional community digest has its own subscription. Our email provider processes your sign-in email and reminder counts for delivery, without email-open tracking.
Cookies and preferences
Sign-in uses protected cookies that browser scripts cannot read. The hosted app must send them over an encrypted connection. Sign-in cookies persist across browser restarts for up to a year and renew during normal use. Steward email security checks can also be remembered in the same signed-in browser for up to a year, renewed when you return. Sign-out or clearing cookies removes browser access; account or provider security changes can require signing in again. Clearing browsing history alone may leave cookies intact. The theme preference may be saved in your browser. Encrypted messaging keeps device keys, encrypted drafts and encrypted history in member-scoped browser storage. Signing out clears this browser’s messaging storage; ordinary browser restarts keep it. After account recovery is enabled, ordinary sign-in restores message access without device approval. Existing legacy accounts may need an original browser or recovery key once to migrate; missing keys cannot be recreated. Login passwords and verification codes are not stored there. Your browser can still hold information in memory, and members can screenshot content.
Video resources
Members may share recordings they have permission to publish. Uploaded videos, captions and drafts are stored in our community database and its encrypted backups. Drafts are restricted to their author and checked platform administrators; published recordings require active community membership. Members can download or copy recordings. YouTube and Vimeo links load an external player only when you choose Load video player. This connects your browser to that provider and sends the video identifier and our site origin; the provider may receive normal browser connection information and use its own cookies or playback data. We do not send member profiles, posts, messages or research data to the video provider. Provider-hosted videos retain that provider's privacy settings: an RA Commons link does not make a public or unlisted external video private. Recording deletion removes uploaded bytes, captions and saved references from the active application, but encrypted backups may retain them for the documented retention period.
Scheduled sending
Choosing Schedule send stores your post or reply draft and its attachments privately on our servers until delivery, so it can publish while the app is closed. Scheduled messages store an encrypted envelope prepared by your device, along with the sender, conversation, device, send time and delivery status. This does not change the platform's message recovery access described below. Times use your local time zone and are stored as UTC instants. You can change the time or cancel a pending send. Delivery checks membership and the original audience again; messages also stop if their participants or devices change. Held attachments remain available while scheduled. Completed or cancelled draft text and authorization context are removed from the active queue; status records are retained for up to 30 days. Backups and recipient copies may retain earlier data. Delivery may be delayed or fail if services or access are unavailable.
Your profile and privacy
Your profile page and photo are available within the approved-member community, not as a public directory. Pending applicants can prepare their own profile while they wait for review. Email addresses and verification evidence are not shown on member profiles. You can change your introduction and remove your profile photo from your profile settings.
Encrypted messaging records
The private messaging service stores ciphertext, encrypted key backups, member and device identifiers, conversation membership, timestamps and file sizes. File names and decryption keys stay inside encrypted messages. Drafts and read-receipt preferences are encrypted. Personal archive, favorite, pin and mute settings, and timestamps for clearing or deleting a chat from your view, are stored as account metadata readable by the platform so they follow you across browsers. Clearing history or deleting a chat from your list hides earlier messages for you; it does not erase stored ciphertext, other members’ copies or group membership. Link cards do not fetch third-party pages. Deleting an individual message removes access through the app and queues ciphertext cleanup; it cannot erase copies already downloaded. Abandoned uploads expire after 24 hours. Resolved report evidence is cleared after 90 days; backups can retain earlier versions. No analytics or third-party AI processes private message content.
IDEA Office Hours
IDEA Office Hours is provided by RA Commons. The following practices apply to its accounts, bookings and connected calendars. Updated 26 October 2026. For privacy, access or deletion requests, contact [email protected].
Account and programme information
When you sign in, we receive your provider identity and, when supplied, your name and account email. We store a connected-account label, programme membership, your profile information, availability and booking records. Profile information you choose to add can include a photo, biography, affiliation, expertise and time zone.
Session titles, times and host profiles are visible to other signed-in programme members. Meeting details are available to the host, currently booked members and authorized IDEA coordinators for IDEA-arranged sessions. Attendee lists are restricted to the host and, for IDEA-arranged sessions, those coordinators.
Connected calendars
You choose one destination calendar for holds and appointments and calendars to check for conflicts. We access calendar names, identifiers, time zones and access permissions to support those choices. Conflict checks use event identifiers, times and availability status. We do not retain or share unrelated event titles, descriptions, locations or attendees.
We create, read, update and remove IDEA-managed events in your destination calendar to reserve offered time and reflect bookings and cancellations. These events are host-only: we do not add attendees or send calendar invitations. We retain their identifiers, scheduling details and ownership records to prevent duplicates and reconcile changes. We do not use your calendar connection to edit unrelated events.
Storage and use
Provider access and refresh tokens are encrypted on the server. Sessions use server-validated, httpOnly cookies. We use account and calendar information to provide scheduling, prevent conflicts, maintain connections and resolve synchronization problems. We do not sell this information, use it for advertising or use it to train AI models. Hosting and backup infrastructure processes stored information for operating the service. Operators read specific Google-derived data for support only with your affirmative permission for that data, or as necessary for security or legal obligations.
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Meetings and calendar subscriptions
When automatic Zoom meeting details are used, we send session scheduling details to the RA Commons Zoom account. We do not send unrelated personal calendar content. IDEA Office Hours does not send email notifications.
Optional subscription links contain session titles, times and status, without meeting links, passcodes or attendee lists. Anyone with a subscription link can read its calendar until the link expires after seven days. Share these links only with people you intend to give access.
Retention and disconnecting
Sign-in sessions last seven days; authorization requests expire after ten minutes. Raw conflict-check responses are not persisted. Profile, booking history and synchronization records are retained to operate the service and reconcile calendar changes. Disconnecting a calendar does not delete your programme profile or booking history.
Disconnect under My calendar. We pause availability and attempt to remove unbooked holds, while preserving confirmed appointments. On successful disconnection we delete saved provider tokens. If cleanup fails, encrypted credentials and ownership records may remain while the connection needs repair; the interface identifies anything requiring attention. You may need to remove outstanding events manually if access has been revoked.
You can also revoke Google access in your Google account connections, or Microsoft access through your account’s app permissions. Revoking access prevents further synchronization and can prevent automatic cleanup.
Email [email protected] to request account or data deletion. We will confirm the request and explain any records that must remain for security or legal reasons. Copies in backups may remain until those backups are replaced. We do not promise immediate removal from backups.