Call Consent Policy.

This Policy explains how calls are recorded and processed in connection with Rlly, and provides notice and consent templates for customers.

1. Purpose and Scope

This Policy explains how calls are recorded and processed in connection with the Rlly product, and provides notice and consent templates for use by Rlly customers and design partners ("Customers"). It applies to any audio, video, or transcript captured and processed through Rlly.

2. The Standard We Apply

Recording laws differ. U.S. federal law and many states require only one party to consent, but a number of states require all parties to consent, and several countries treat call recordings as personal data requiring a lawful basis and clear notice. Because a single call can involve participants in multiple jurisdictions, the safe operating standard is to obtain the informed consent of every participant before recording or AI processing begins. Rlly is built to support this standard, and Customers are contractually responsible for meeting it (see the Design Partner Agreement and the customer agreement / DPA).

3. Core Rules for Customers

  • Notify before you record. Every participant must be clearly told, before recording starts, that the call is being recorded and processed by AI, and by whom.
  • Default to all-party consent. Unless counsel has confirmed otherwise for a specific scenario, obtain affirmative consent from all participants.
  • Honor objections. If any participant declines, do not record that participant. Stop recording, or proceed without the recording feature.
  • Disclose AI processing. State that the recording will be transcribed and analyzed by automated tools, not only stored.
  • Log consent. Capture and retain a record of the notice given and consent received as part of the audit trail.
  • Do not record sensitive content that participants have not agreed to have captured (for example, legally privileged or special-category personal information).

4. How to Capture Consent

Use these layers together for the strongest position:

  • Pre-meeting written notice in the calendar invite and on the scheduling page.
  • Verbal disclosure at the start of the call, with a moment for participants to object.
  • A visible recording indicator during the call.
  • A logged consent record retained with the call.

5. Notice and Consent Templates

5.1 Calendar invite / scheduling page notice

This meeting may be recorded and transcribed, and the recording may be analyzed using AI tools provided by Rlly to help [Company] capture notes and follow-ups. By joining, you consent to this recording and processing. If you prefer not to be recorded, please let the host know before the meeting begins, or contact [[email protected]].

5.2 Verbal disclosure at the start of the call

Before we get started, I want to let you know that this call is being recorded and transcribed, and we use an AI assistant called Rlly to help us take notes and capture next steps. Is everyone comfortable proceeding on that basis? If anyone would prefer we not record, just say so and we will turn it off.

(Wait for affirmative acknowledgment from each participant. If anyone objects, do not record.)

5.3 In-app / in-meeting banner

Recording and AI note-taking are on. This call is being captured and analyzed by Rlly.

5.4 Email / footer reference

We use Rlly to record and transcribe meetings with your consent. To learn more or opt out, see this Policy or contact [[email protected]].

6. International Calls (GDPR / UK GDPR and Others)

If any participant is in the EEA, the UK, or another jurisdiction with comprehensive privacy law, recording is processing of personal data and requires a lawful basis (often consent or legitimate interests) plus clear, advance notice of who is recording, why, what will be processed, how long it is kept, and the individual's rights. Some countries impose stricter or sector-specific rules. Confirm the approach with counsel before recording cross-border calls.

7. Responsibilities

The Customer is the party in control of its calls and its relationships with participants and is responsible for lawful recording, notice, and consent. Rlly provides the tooling, indicators, templates, and consent logging described above, and will not knowingly record a participant who has not been disclosed to where the Customer has configured the product to enforce this. Rlly does not provide legal advice and does not assume the Customer's compliance obligations.

8. Changes

We may update this Policy as the product and the law evolve. Material changes will be reflected in the "Last Updated" date above.

9. Contact

Rlly, Inc.
530 Lawrence Expy PMB 925
Sunnyvale, CA 94085
[email protected]