What this notice covers
This notice covers information submitted through the RIN website, including the free waitlist, Founding Membership interest form, and member-account or enabled purchase flows. It also covers the connected Google and private relationship-workspace features described below when those features are enabled for a user.
Information collected before launch
The waitlist asks for your name, email address, and email consent. You may also choose to share your job title, company, primary use case, relationship-management challenge, approximate network size, interest level, referral source, or referral code.
If you create a member account, Supabase provides managed authentication using email or an enabled third-party sign-in provider. RIN receives your verified email address and may receive your display name. RIN stores your account role, plan, status, creation time, and recent sign-in time so it can provide and administer account access.
Basic technical and interaction information may also be recorded to understand site performance and actions such as page views, form completion, checkout progress, and referral-link use.
How pre-launch information is intended to be used
- Manage your waitlist or Founding Membership interest status.
- Create, secure, and administer your RIN member account.
- Send product, launch, and early-access updates you requested.
- Understand which audiences and use cases RIN should serve.
- Operate, protect, and improve the pre-launch website.
- Process a purchase only when the paid offer is enabled.
A final policy must identify the legal entity responsible for this information, applicable service providers, retention periods, lawful bases where required, international transfers, and jurisdiction-specific rights before paid access begins.
Product privacy principles
RIN is being designed around the following principles:
- Permission-based connections: users choose which supported sources to connect.
- Source transparency: important context should show where it came from.
- Correction and deletion controls: users should be able to correct or remove stored information.
- Clear AI boundaries: source facts and AI-generated inferences should be distinguishable.
These are product-design commitments, not claims that unfinished features, certifications, or security standards are already in place.
Connected Google data
If you explicitly connect a Google account, RIN asks for read-only access to supported email and calendar data. The initial synchronization is limited to the previous 12 months. RIN may receive your provider account identifier and email address, message headers and bodies, sender and recipient information, and calendar event details such as titles, descriptions, participants, locations, and times. Attachments are not imported by this connection.
RIN uses connected data only to provide user-facing relationship features you request, including communication history, interaction signals, identity matching, meeting context, and potential updates to people profiles. The read-only connection cannot send, modify, or delete email or calendar items in your provider account.
You may separately authorize Gmail drafting and sending. RIN uses that additional permission only when you explicitly save a Gmail draft or confirm a send. Saving and sending are separate actions, and RIN does not send automatically from relationship suggestions, profile updates, sequences, or workflows. Outbound message content is transmitted to Gmail for the requested action; RIN records the action status and Google item identifier but does not retain the outbound message body in its audit record.
RIN does not use connected Google data for advertising, does not sell it, and does not use it to train general-purpose AI models. Human access is restricted to situations where it is necessary to provide authorized support, investigate security or abuse, comply with law, or protect users and the service.
Storage, security, and customer separation
Provider credentials and synchronized message and calendar content payloads, including message bodies and event descriptions, are encrypted before storage. Limited participant matching fields such as email address, display name, communication direction, and timestamp are kept in tenant-scoped structured indexes so RIN can deduplicate identities and calculate interaction counts. Connection records are associated with the signed-in RIN account, and server-side ownership checks are applied when data is read, synchronized, or deleted. RIN uses Cloudflare for application hosting and structured storage and Supabase for managed account authentication.
People profiles saved in a private workspace are also encrypted before storage and separated by signed-in account. Email-derived profile suggestions do not change a profile automatically: the user must review and approve each addition or update. RIN uses a keyed, non-reversible matching value to associate an approved email address with its encrypted profile.
No online service can promise absolute security. RIN limits the information requested, separates read-only synchronization from optional Gmail compose access, and maintains connection audit records that do not contain provider credentials or message bodies.
Disconnecting, revocation, and deletion
You can disconnect a provider account from the RIN Connections page. Disconnecting deletes the stored provider credentials and the synchronized RIN copy of that account's email and calendar data. Google access is also revoked through Google when available. You may also revoke RIN directly through your Google account at any time. Disconnecting does not delete drafts or sent messages that already exist in Gmail.
Limited security, fraud-prevention, transaction, and legal records may be retained when reasonably necessary, but connection audit records do not retain message bodies or access tokens. Backup copies are removed according to the applicable backup lifecycle.
Google API Services User Data Policy
RIN'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 its Limited Use requirements. Connected Google data is used only to provide or improve the user-facing features described in this notice.
Sale of personal information
RIN does not sell information submitted through this pre-launch website. The product is also being designed around a policy of not selling personal relationship data. That commitment must remain explicit in the legally approved policy before product access begins.
Email choices
You may unsubscribe from product-update emails using the link in any message. Administrative messages related to a purchase, a requested privacy action, or a material change may still be sent where appropriate.
Your questions and requests
To ask a privacy question or request access, correction, or deletion of pre-launch information, email hello@rinbase.tech. Identity verification may be required before a request is completed.