RCKNSign in

Privacy Policy

Effective October 7, 2026

RCKN (“we”, “our”, “us”) is a product of LVNG AI, Inc. This policy explains what data we collect when you use RCKN, how we use it, and your rights with respect to that data.

1. What we collect

When you connect your email account, RCKN ingests:

  • Email metadata — subject lines, sender/recipient addresses, timestamps, and thread IDs.
  • Email bodies — full message text and HTML, stored in workspace-scoped application records and used to build workspace-tagged graph relationships.
  • Attachments — incoming attachment metadata is indexed and content is fetched when needed. Files you add to a draft are stored in private object storage and retained with that draft until the applicable cleanup or deletion workflow runs.
  • OAuth tokens — encrypted access and refresh tokens used to sync mail and perform the mail, calendar, and meeting actions you choose.
  • Account information — the email address and user ID you sign in with via Supabase Auth.

We do not collect billing information directly — payments are processed by Stripe and covered by their privacy policy.

2. How we use your data

We use collected data to:

  • Extract and link clients, deadlines, and documents visible in the RCKN UI.
  • Generate draft replies through the configured commercial model API. The provider receives email content included in the task's prompt context.
  • Compute semantic embeddings (pgvector) for inbox search. Embeddings are stored per-workspace and never shared across tenants.
  • Produce audit log entries for your firm's own compliance use.

We do not use your email content to train RCKN models. Third-party model processing is governed by the commercial API terms and data controls in effect for the deployed service; those terms are available on request.

3. Data sharing

Depending on the deployment and enabled features, RCKN uses service providers for model inference, database and object storage, infrastructure, authentication, and payments. We disclose data only as needed to provide those services. We do not sell personal data or share it with advertisers. A current, deployment-specific subprocessor list is available on request at privacy@lvng.ai.

4. Google user data

RCKN'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.

When you connect a Google account, RCKN requests these Google scopes and uses each one only for the purposes shown:

  • Gmail, read (gmail.readonly scope): show your messages, threads, and attachments in RCKN, keep your inbox in sync, read the sending aliases and their verification status for your selected reply account to leave your verified addresses out of suggested reply recipients, power inbox search, find the clients, deadlines, and documents RCKN shows you, and produce the AI features RCKN builds from your mail: thread summaries with urgency, risk flags, and action items; smart replies and reply drafts; folder suggestions; Copilot answers; your digest; and the digital twins in your settings.
  • Gmail, send (gmail.send scope): send the messages, replies, and forwards you write or approve in RCKN and your replies to meeting invitations, and email you the daily or weekly digest you turn on or ask for, sent from your account to you.
  • Gmail, organize (gmail.modify scope): carry out the inbox actions you take in RCKN, ask Copilot to take, or approve from a digital twin's suggestion, such as archive, mark as read or unread, label, snooze, and move to trash, and undo them; return a snoozed thread to your inbox when its snooze ends; and apply the inbox rules you set up in Settings (label, archive, mark as read) to new mail as it arrives, and to your recent mail when you accept a suggested rule.
  • Google Calendar, read (calendar.readonly scope): list the calendars in your Google account and read the events on your primary calendar and on the other calendars you have selected in Google Calendar, including each event's title, time, description, location, and guests with their responses, to show them to you in RCKN, on your Calendar, Today, and Work pages, and to open an event's details; and read only the busy times on your calendars, not what your events are, to find open times: for the booking pages you publish, whose visitors see only the open times; when you or a teammate asks Copilot to schedule a meeting with you, which books a time when everyone is free; and when a member of your workspace looks for a time to meet with you, who then sees when you are busy but not your events.
  • Google Calendar, events (calendar.events scope): create events on your calendar, with invitations to their guests and, for some meetings, a Google Meet link: the events and invitations you make in RCKN, from the Calendar page or from a draft; the meetings you ask Copilot to schedule or approve from a digital twin's suggestion; and each meeting someone books through one of your booking pages, with the invitation sent from your account, and delete that event again if the booking cannot be completed. It also lets RCKN edit or reschedule the events you change or drag to a new time in RCKN, including events RCKN did not create, with the change sent to their guests.
  • Google Meet (meetings.space.created and meetings.space.readonly scopes): when you turn on recording for a booking type, create a Google Meet space with recording and transcription turned on for each meeting booked through it, and after the meeting check whether Google has finished that meeting's transcript and recording so RCKN can mark the booking's transcript as ready. RCKN does not download or read the transcript or recording.
  • Account identity (openid and userinfo.email scopes): confirm which Google account you connected and show its address in RCKN, use it as the From address of your replies to meeting invitations, and invite you at that address when a teammate asks Copilot to schedule a meeting with you.

Within your workspace, mail from your connected account is readable by you and your workspace's owners and admins. Legacy mail without a recorded mailbox connection remains readable to workspace members. Knowledge derived from mail, such as client facts and deadlines, is shared across the workspace and can reveal information from private messages. Your unsent drafts are not shared with other workspace members, including owners and admins.

Google user data that RCKN receives through these scopes:

  • is used only to provide the user-facing features described above;
  • is not used for advertising, including personalized, retargeted, or interest-based advertising;
  • is not sold, and is not transferred to advertising platforms, data brokers, or information resellers;
  • is not used to determine credit-worthiness or for lending purposes;
  • is not read by people at LVNG unless you give us permission for specific messages or data (for example, when you ask us to look into a problem), it is necessary for security purposes such as investigating abuse, or it is required to comply with applicable law;
  • is not used to develop, improve, or train generalized AI or machine-learning models;
  • is shared with AI model providers only to provide a user-facing feature of RCKN, such as summarizing a thread, finding a deadline, or drafting a reply (RCKN prepares some of these as new mail arrives so they are ready when you open it), and with our other service providers only as needed to run RCKN or to comply with applicable law; and
  • is otherwise transferred only at your or your workspace's direction: to the other members of the RCKN workspace you connect your account to, who can see mail and derived knowledge according to the workspace access rules above (never your unsent drafts), and the busy times described above; to the people who receive the messages, replies, forwards, invitations, and attachment links you send; to Microsoft's Office Online viewer when you open a Word, Excel, or PowerPoint attachment in RCKN, which fetches only that file, through a link that expires within five minutes, to show you its preview; and to another RCKN workspace's agent when you have Copilot send it a message.

RCKN's use and transfer to any other app of information received from Microsoft Graph follows the same commitments. When you connect an Outlook or Microsoft 365 account, RCKN requests these Microsoft permissions and uses each one only for the matching purpose above: Mail.Read and Mail.ReadWrite for the Gmail read and organize purposes, except that RCKN does not look up Outlook sending aliases; Mail.Send for the Gmail send purposes, together with Mail.ReadWrite to prepare a message, reply, or forward as a draft in your mailbox, with its recipients and attachments, just before RCKN sends it; Calendars.ReadWrite for the Google Calendar purposes, with a Teams link where Google would add a Meet link, and to answer the meeting invitations you reply to in RCKN; User.Read for the account identity purposes; and offline_access to keep your mailbox in sync and carry out the purposes above while you are away.

5. Retention and deletion

Email data is retained for the lifetime of your workspace. A workspace deletion runs a multi-store purge covering uploaded draft files, workspace-tagged Neo4j nodes, Postgres records, OAuth connections, and embeddings. The operation reports the outcome for each store; a partial failure is surfaced for retry and investigation. Completion time depends on the connected services and is not guaranteed to a fixed number of seconds.

6. Your rights

Depending on your jurisdiction, you may have the right to:

  • Access the personal data we hold about you.
  • Correct inaccurate data.
  • Request deletion (right to erasure / right to forget).
  • Port your data in a machine-readable format.
  • Object to processing.

To exercise any of these rights, email privacy@lvng.ai. We will respond within 30 days.

7. Cookies and tracking

RCKN uses session cookies (via Supabase Auth) strictly for authentication. We do not place advertising, analytics, or tracking cookies. There is no third-party analytics script loaded by the application.

8. Contact

Questions about this policy: privacy@lvng.ai
LVNG AI, Inc. · San Francisco, CA