Privacy Policy
Effective and last updated: September 16, 2026
This Policy covers the Rlly website, applications, hosted services, AI features, and connected integrations.
This Privacy Policy explains how Rlly, Inc. ("Rlly," "we," "us," or "our") collects, uses, stores, discloses, and protects personal information when you visit rlly.ai, communicate with us, create an account, use the Rlly applications or hosted services, or connect third-party services (collectively, the "Services").
Rlly, Inc. is a Delaware corporation located at 530 Lawrence Expy PMB 925, Sunnyvale, California 94085. For privacy questions or requests, contact privacy@rlly.ai.
1. Scope and our role
This Policy applies to personal information Rlly handles for its own business purposes and to information processed through the Services. When an organization uses Rlly for its personnel, customers, prospects, or meeting participants, that organization generally determines why and how Customer Data is processed and Rlly acts as its processor or service provider. The organization's agreement and Data Processing Addendum govern that processing. Individuals may need to direct certain requests to the organization that controls their data.
Our Data Processing Addendum provides additional terms for customer-controlled personal data. This Policy does not govern a third-party service's independent handling of information after you direct Rlly to send data to that service.
2. Information we collect
Information you provide
We collect account and profile information such as your name, work email, company, role, team, preferences, signature, support messages, survey responses, and billing or transaction details. We collect information you submit through the Site, including demo requests, waitlist entries, applications, and other communications.
Customer and Service Data
Depending on the features you and your organization enable, the Services may process meeting audio streams, transcripts, notes, participant and contact details, CRM records, deal information, calendar events, call analysis, knowledge-base content, drafts, attachments, user approvals, action receipts, and other information you choose to submit or connect. Rlly does not intend the Services for medical records, financial-account credentials, government identifiers, or other highly sensitive data unless expressly agreed in writing and configured for that purpose.
Google user data
If you sign in with or connect a Google account, Rlly accesses only the Google data and capabilities that you authorize. Current production features use the following permissions:
- Basic identity. OpenID, profile, and email: your Google account identifier, name, email address, and profile information used for sign-in, account matching, and showing which Google account is connected.
- Calendar. Google Calendar event information for calendars you own, currently from your primary calendar: event ID and status; title and description; start and end times; attendee names, email addresses, and response status; organizer and creator details; location; event link; and video-conference or meeting link. Rlly uses this data to display upcoming meetings, provide reminders and conflict warnings, prepare user-facing meeting context, and create events that you request or approve.
- Gmail send. The recipients, sender, subject, message body, formatting, and attachments you choose to send from the connected Gmail account. Rlly uses Gmail only to send a message that you initiate or approve and receives limited delivery identifiers or status from Google. Rlly does not read your Gmail inbox, sent-mail history, drafts, contacts, labels, or Gmail settings.
- Connection credentials. Google OAuth access and refresh tokens, granted scope information, token expiry, connected-account email, and connection timestamps. Tokens are stored server-side and are not exposed to the Rlly desktop renderer.
The Google Calendar permission technically permits creating, changing, and deleting events on calendars you own. Current Rlly production features use it to read upcoming events and create events; Rlly will update its disclosures and obtain any required consent before materially expanding that use.
Information from other integrations
If you connect Microsoft 365, HubSpot, Zoom, Microsoft Teams, Linear, or another provider, we receive the account, calendar, mail, meeting, CRM, or work-management data permitted by that provider and your configuration. The exact data depends on the permissions shown by the provider and the features you enable.
Device, usage, and website data
We collect device and application information such as app version, operating system, device type, language, approximate region derived from network information, feature interactions, performance timing, crash and error information, authentication state, and pseudonymous account or team identifiers. The Site may collect IP address, browser type, referring pages, pages viewed, and cookie identifiers.
3. How we use information
We use personal information to:
- provide, operate, personalize, maintain, and secure the Services;
- authenticate users, manage accounts and organizations, and maintain connected-service permissions;
- display calendars, provide meeting reminders and preparation, detect conflicts, and create requested calendar events;
- generate notes, summaries, drafts, coaching, and other user-facing AI assistance;
- send emails or take other actions in connected services only when initiated, configured, or approved by an authorized user;
- provide support, diagnose errors, monitor reliability, prevent fraud and abuse, and protect users and systems;
- process billing, manage subscriptions, respond to inquiries, and send administrative messages;
- send marketing communications where permitted, subject to your right to opt out;
- analyze aggregate or de-identified usage to improve the Services; and
- comply with law, enforce agreements, and establish or defend legal claims.
4. Google API data use and Limited Use
Google user data is used only to provide or improve visible, user-facing features that you request or enable. In particular:
- Calendar data may be fetched in the background to keep upcoming-meeting displays, reminders, conflict warnings, and meeting preparation current.
- Relevant calendar context, such as an attendee email address and meeting details, may be used to match a contact or deal in another integration you connected, solely to provide the meeting-preparation or workflow feature shown in Rlly.
- If you explicitly enable draft personalization from history, Rlly may retain a limited, redacted style sample derived from titles and descriptions of events you created or organized. The current implementation stores up to ten calendar samples, removes email addresses and phone numbers where detected, and uses the samples only to personalize your own user-facing drafts. Disabling the setting stops collection and use; you may request deletion of stored samples.
- Rlly may process relevant Google data through Microsoft Azure and Azure OpenAI only to provide the user-facing feature you requested. Google data is not sent to OpenAI consumer services and is not used to train a shared or general-purpose AI model.
- Rlly does not use Google user data for advertising, retargeting, creditworthiness, lending, data brokerage, or surveillance, and does not sell Google user data.
- Rlly personnel do not read Google user data except with the user's specific affirmative permission for support, when necessary to investigate abuse or a security incident, when required by law, or when data has been aggregated and de-identified for internal operations as permitted by policy and law.
Rlly'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.
5. AI processing
Rlly may send Customer Data, including relevant calendar or meeting context, to AI services configured for the account to generate user-facing summaries, drafts, classifications, coaching, or proposed actions. In Rlly-hosted deployments, model processing is performed through Microsoft Azure services, including Azure OpenAI, under contractual restrictions. In customer-managed deployments, processing may occur in the customer's own tenant and with providers selected by the customer.
We do not use Google user data, meeting content, CRM records, or Customer Data to train or improve shared foundation models. Optional user-specific personalization uses limited samples as context for that user's requested output and does not train a shared model.
6. How we disclose information
We may disclose information in the following circumstances:
- Service providers. Vendors that process data for Rlly under contract, such as Microsoft Azure and Azure OpenAI for hosting and user-facing AI processing; Microsoft Entra for authentication; Datadog or similar diagnostics services when enabled; Cloudflare for Site security and delivery; HubSpot for Site forms and communications; and Stripe or another payment processor for billing. We do not intentionally send OAuth tokens or raw Google calendar or Gmail content to advertising or website-analytics tools.
- Connected services. Third-party integrations you or your organization connect. We disclose only the information needed to perform the user-facing action or synchronization you request, such as sending an email through Gmail or matching a calendar attendee to a connected CRM.
- Organization administrators. Your organization and its authorized administrators, in accordance with the organization's configuration, agreements, and applicable law.
- Legal and safety. Government authorities or other parties when reasonably necessary to comply with law or legal process, protect rights and safety, investigate fraud or security issues, or enforce agreements.
- Business transfers. A buyer, successor, or adviser in connection with a merger, financing, reorganization, bankruptcy, or sale of assets, subject to appropriate confidentiality and any consent required for Google user data.
- At your direction. Other parties when you direct us to disclose information or provide affirmative consent.
A current overview of infrastructure and subprocessors is available on our Security page. Customer-specific deployment choices may change which processors apply.
7. Storage, retention, and deletion
Google credentials and connection data
Google OAuth access and refresh tokens and connection metadata are encrypted or otherwise protected using access controls in Rlly's server-side Azure environment and retained while the Google connection remains active. Disconnecting Google in Rlly removes the stored Google connection credentials from Rlly. You may also revoke access through your Google Account's third-party connections. Revoking access at Google stops future access but does not automatically delete information already retained by Rlly for a permitted purpose; use Rlly's deletion controls or contact us for deletion.
Calendar and email information
Rlly generally fetches calendar events on demand and maintains short-lived service and device caches to keep the calendar and meeting-reminder experience responsive. Rlly does not maintain a general-purpose archival copy of a user's Google Calendar. Cached local calendar data is cleared through Rlly's logout, account-deletion, or reset-state process. We may retain meeting-preparation artifacts, action receipts, user-created event details, or other Customer Data where needed to provide the Services and according to the organization's settings and agreement.
Outgoing email drafts, content, attachments, and send records may be retained as Customer Data to provide call follow-up, audit, CRM logging, or user-requested history. If draft personalization is enabled, Rlly may retain up to five redacted samples from emails actually sent through Rlly; Rlly does not read Gmail sent mail to build those samples.
Other retention
We retain personal information only as long as reasonably necessary for the purposes described in this Policy, including providing the Services, honoring customer settings, maintaining security and audit records, complying with law, resolving disputes, and enforcing agreements. Retention periods vary by data type, plan, deployment, customer instruction, and legal requirement. We delete or de-identify information when it is no longer needed.
When a valid account-deletion request is completed, Rlly deletes or de-identifies account data under its control, subject to legal obligations, security records, backup cycles, and any Customer Agreement. In customer-managed deployments, the customer controls deletion within its own tenant.
8. Security
We use administrative, technical, and organizational safeguards designed to protect personal information, including encryption in transit, encryption at rest for hosted data, least-privilege access controls, token protection, logging and monitoring, tenant separation, and secure development practices. Provider OAuth tokens remain on the backend and are not returned to the desktop renderer. No system is perfectly secure, and we cannot guarantee absolute security.
9. Your choices and controls
- Connections. Disconnect Google Workspace or other integrations in Rlly settings and revoke access through the connected provider.
- Feature settings. Control calendar reminders, conflict warnings, synchronization windows, and optional draft personalization in Rlly settings where available.
- Account and data requests. Request access, correction, deletion, or export by using in-product controls or contacting privacy@rlly.ai. Organization-managed users may need to submit requests through their administrator.
- Marketing. Unsubscribe using the link in a marketing email or contact privacy@rlly.ai. Administrative and security messages may continue.
- Cookies. Use browser controls, the Site's cookie settings, and recognized opt-out signals where required by law.
10. Regional privacy rights
United States
Residents of California and certain other states may have rights to know, access, correct, delete, or obtain a copy of personal information and to opt out of certain sales, targeted advertising, profiling, or sharing. You may exercise applicable rights by contacting privacy@rlly.ai. We may verify your identity and authority before responding. You may use an authorized agent where permitted. We will not discriminate against you for exercising a privacy right.
Rlly does not sell personal information for money and does not sell or share Google user data for cross-context behavioral advertising. Depending on the Site's cookie configuration and applicable law, some website analytics activity may be treated as "sharing." Use the Site's cookie controls or a recognized opt-out preference signal, such as Global Privacy Control, where available.
EEA, United Kingdom, and Switzerland
Where applicable, you may have rights to access, correct, erase, restrict, or object to processing; receive a portable copy; withdraw consent; and complain to a supervisory authority. Our legal bases include performance of a contract or steps requested before a contract, legitimate interests in providing and securing the Services and operating our business, consent where required, and compliance with legal obligations.
When personal data is transferred from the EEA, United Kingdom, or Switzerland to a country without an adequacy decision, we use safeguards such as the European Commission Standard Contractual Clauses and the UK Addendum, as applicable. Contact privacy@rlly.ai for more information.
11. Cookies and analytics
The main marketing Site loads Google Analytics, Google Tag Manager, HubSpot and RB2B only after you accept optional tracking. Google measures site use; HubSpot and RB2B support visitor and company identification and marketing. These providers may link browsing activity, cookies, device or network identifiers with information they or their partners hold, including email addresses. Rlly or its service providers may use that information for marketing communications.
Choose Essentials only to keep these tools off, or reopen Cookie settings in the footer to change or withdraw your choice. Withdrawing consent reloads the page to stop active trackers; it does not erase information already collected. You can remove existing cookies using your browser controls. We honor Global Privacy Control and Do Not Track by keeping optional tracking off. Choices expire after 180 days.
The desktop application may store local settings and short-lived caches needed for application functionality; these are not used for cross-site advertising.
12. International processing
Rlly is based in the United States. Personal information may be processed in the United States and other countries where Rlly, its providers, or customer-selected infrastructure operates. Data-protection laws may differ from those in your location. Enterprise and customer-managed deployments may provide additional regional and residency controls.
13. Children's privacy
The Services are intended for business users and are not directed to children under 16. We do not knowingly collect personal information from children under 16. If you believe a child provided personal information to Rlly, contact privacy@rlly.ai so we can investigate and delete it where required.
14. Changes to this Policy
We may update this Policy to reflect changes in the Services, laws, or data practices. We will post the updated Policy and change the effective date. If a change materially expands how we use previously collected Google user data or other personal information, we will provide additional notice and obtain consent where required before applying the new use.
15. Contact us
For privacy questions, complaints, or rights requests:
Rlly, Inc.
530 Lawrence Expy PMB 925
Sunnyvale, CA 94085
privacy@rlly.ai
Related policy: Rlly Terms of Use