Privacy policy.

1. Who we are

RoveNotes is operated by Radiant Maple Studios LLC, a California limited liability company ("Radiant Maple," "we," "us," "our"). This Privacy Policy explains how we collect, use, store, and share information when you use RoveNotes at rovenotes.com and any related services (the "Service").

For privacy questions or to exercise your rights, contact privacy@radiantmaple.com.

2. Scope

This policy applies to information we collect through the Service. It does not apply to:

• Plaud (the hardware and the Plaud cloud service operated by Plaud's manufacturer). Plaud's own privacy policy governs your use of Plaud's hardware and cloud.
• Third-party destinations you connect (Notion, Obsidian, Google Drive, reMarkable, Todoist, Google Calendar, email inboxes, webhook endpoints). Once we deliver content to a destination you authorized, that content is governed by that third party's terms and privacy policy.

3. Information we collect

3.1 Account information

We use Google Sign-In as the only authentication method. When you sign in, Google provides us:

• Your name
• Your email address
• Your Google account ID
• Your profile picture (if set)

We do not store your Google password. You can revoke RoveNotes's access from your Google Account at any time. The full list of Google OAuth scopes RoveNotes requests, what each scope is used for, and how RoveNotes complies with Google's Limited Use requirements is in Section 5.

3.2 Plaud access credentials

To retrieve your recordings from Plaud, you supply a Plaud bearer token. We store this token encrypted and use it to make authenticated requests to Plaud on your behalf. You can revoke or rotate this token at any time from your Plaud account or from RoveNotes's settings.

We are not affiliated with, endorsed by, or operated by Plaud. Our access to Plaud depends on credentials you provide and on interfaces Plaud exposes, which Plaud may change or restrict at any time.

3.3 Content from Plaud

Once authenticated, we retrieve and store:

• Audio recordings
• Transcripts (produced by Plaud)
• Summaries (produced by Plaud)
• Associated metadata (title, duration, timestamps, speaker labels)

3.4 Integration credentials and configuration

When you connect a destination (Notion, Google Drive, Todoist, Google Calendar, Obsidian vault via its API, reMarkable, email addresses, or webhook URLs), we store the OAuth tokens, endpoint URLs, signing secrets, and routing preferences needed to deliver content. OAuth tokens and webhook signing secrets are stored encrypted.

3.5 Derived content

Our AI router generates classifications, task extractions, calendar-event extractions, and routing decisions from your Plaud content. This derived content is stored alongside the source content and deleted on the same schedule.

3.6 Payment information

Payments are processed by Stripe. We do not see or store full payment card numbers. We store a Stripe customer ID, subscription status, plan, and a redacted card descriptor (brand and last four digits) returned by Stripe.

3.7 Service logs and operational data

We collect standard operational data: IP address, user agent, timestamps, API request paths, error traces, and integration delivery status. These logs are used for security, debugging, abuse prevention, and service reliability.

4. How we use information

We use your information to:

• Authenticate you and secure your account
• Retrieve your content from Plaud using the credentials you supplied
• Classify and route content using AI (see Section 6)
• Deliver content to the destinations you have authorized
• Send operational notifications (email digests, webhook deliveries) that you have configured
• Bill you, prevent fraud, and administer your subscription
• Detect abuse, debug failures, and maintain the Service
• Communicate with you about the Service (account notices, material changes)

We do not use your recordings, transcripts, or summaries to train AI models. We do not sell your personal information.

5. Google API user data

RoveNotes uses Google APIs (Sign in with Google, Google Drive, Google Calendar) to deliver features you turn on. This section spells out which Google OAuth scopes we request, why we request them, and what RoveNotes will and will not do with the data Google returns. It supplements the rest of this Privacy Policy and reflects our compliance with the Google API Services User Data Policy, including the Limited Use requirements.

5.1 Scopes RoveNotes requests, and why

RoveNotes requests only the narrowest scopes needed for these features. RoveNotes does not request drive (full Drive access), drive.readonly, calendar (full calendar access), any Gmail scope, or any other Google scope.

5.2 Limited Use — how RoveNotes handles Google user data

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

Specifically, with respect to data obtained through Google APIs, RoveNotes:

• Uses the data only to provide or improve user-facing features that are prominent in the RoveNotes product — namely Sign in with Google, Drive backup of your recordings, and Calendar event creation from voice notes.
• Does not use Google user data for serving advertising of any kind, including retargeted or personalized advertising.
• Does not sell Google user data, and does not transfer Google user data to third parties except (a) as necessary to provide or improve the user-facing features above, (b) to comply with applicable law, or (c) as part of a merger, acquisition, or sale of assets, with notice to users.
• Does not allow humans to read Google user data, and does not use Google user data outside the user-facing features described above, except (i) with your affirmative consent for specific items, (ii) when strictly necessary for security purposes such as investigating abuse, (iii) to comply with applicable law, or (iv) when the data has been aggregated and anonymized and is used for internal operations such as capacity planning.
• Does not use Google user data to develop, train, fine-tune, or improve generalized or non-personalized AI/ML models. Anthropic processes summaries and transcript excerpts to power RoveNotes's user-facing routing features only, under a contract that prohibits training on customer content.

5.3 Storage, retention, and deletion of Google data

The only Google-account data RoveNotes stores on its own servers is your Google account ID, name, email address, profile picture URL, and the OAuth refresh tokens for the scopes you have authorized. OAuth tokens are stored encrypted (see Section 10).

RoveNotes does not store copies of your Drive files or Calendar events on its servers — Drive backups are written directly to the folder you selected in your Drive, and calendar events are written directly to your Google Calendar. The source recordings, transcripts, and summaries that get mirrored to Drive remain subject to the retention rules in Section 9.

You can disconnect Google Drive or Google Calendar at any time from RoveNotes's settings, which deletes the corresponding stored OAuth tokens. You can also revoke RoveNotes's access to your Google Account at any time at myaccount.google.com/permissions. When you delete your RoveNotes account, your stored Google identifiers and OAuth tokens are deleted on the schedule described in Section 9 (Retention). Files RoveNotes has already written to your Drive and events already created on your Calendar remain in those Google products under your control — see "Non-cascading deletion" in Section 9.

6. Subprocessors

We share information with a limited set of service providers ("subprocessors") strictly to operate the Service. As of the effective date, they are:

We do not send Plaud content to any subprocessor other than those listed above, and only as needed to deliver the Service. An updated list is maintained at rovenotes.com/subprocessors.

7. Legal bases (EEA, UK, Switzerland)

If you are in the EEA, UK, or Switzerland, we process your data on the following legal bases:

• Performance of a contract (Art. 6(1)(b) GDPR) — to deliver the Service you've subscribed to.
• Legitimate interests (Art. 6(1)(f) GDPR) — to secure the Service, prevent abuse, and improve reliability.
• Consent (Art. 6(1)(a) GDPR) — for any processing you specifically opt into (e.g., marketing email, if we ever add it).
• Legal obligation (Art. 6(1)(c) GDPR) — to comply with applicable law.

8. International transfers

We are based in the United States and store data in the United States. If you access the Service from outside the US, your information will be transferred to and processed in the US. Where required, we rely on the European Commission's Standard Contractual Clauses and equivalent UK/Swiss mechanisms with our subprocessors.

9. Retention

• Solo (free): Recordings, transcripts, summaries, and derived content are automatically deleted 30 days after they were ingested.
• Pro: Retained until you delete them or close your account.
• Any tier: You can delete any recording with a single click. Deletion is immediate in our database and purged from object storage within 30 days.
• Account closure: When you delete your account, we delete your stored content, integration tokens, and Plaud credentials. We retain minimal records (billing history, fraud-prevention signals, and legal-compliance records) for as long as required by law, typically up to seven years for financial records.

Non-cascading deletion. Content we have already delivered to your connected destinations (Notion pages, Drive files, Todoist tasks, Calendar events, emails, webhook payloads) lives in those destinations under your control. Deleting the source in RoveNotes does not delete those downstream copies. You must delete them in the destination tool yourself.

10. Security

• All data is encrypted in transit (TLS 1.2+) and at rest.
• Plaud bearer tokens, OAuth tokens, and webhook signing secrets are stored encrypted with keys separate from the application database.
• Access to production systems is limited to authorized personnel and audited.
• We do not train AI models on your recordings, transcripts, or summaries.
• No system is perfectly secure. We will notify you of a security incident affecting your personal data without undue delay and, where legally required, within 72 hours of becoming aware of it.

11. Your rights

Depending on where you live, you have rights regarding your personal information. These may include:

• Access — get a copy of the data we hold about you.
• Correction — correct inaccurate data.
• Deletion — delete your data (see Section 9).
• Portability — receive your data in a portable format.
• Restriction / objection — limit or object to certain processing.
• Withdraw consent — where processing is based on consent.
• Complaint — lodge a complaint with your local data-protection authority.

Most of these can be exercised directly in RoveNotes's settings. For anything else, email privacy@radiantmaple.com. We respond within 30 days.

12. California residents (CCPA / CPRA)

California residents have additional rights:

• Right to know what categories of personal information we collect, the purposes, and the categories of third parties we share it with (disclosed in Sections 3–6).
• Right to delete your personal information (Section 9).
• Right to correct inaccurate personal information.
• Right to opt out of "sale" or "sharing" — we do not sell or share your personal information as those terms are defined under the CPRA.
• Right to limit use of sensitive personal information — we do not use sensitive personal information for purposes beyond providing the Service.
• Right to non-discrimination for exercising these rights.

To exercise these rights, email privacy@radiantmaple.com. We may need to verify your identity before fulfilling a request.

13. Children

The Service is intended for users 18 and older. We do not knowingly collect personal information from anyone under 18. If we learn we have collected information from a person under 18, we will delete it. If you believe a minor has provided us information, contact privacy@radiantmaple.com.

14. Cookies and similar technologies

We use strictly necessary cookies and similar technologies to keep you signed in and to secure the Service. We do not use third-party advertising cookies.

15. Browser extension (RoveNotes Connector)

RoveNotes publishes a browser extension called RoveNotes Connector for Chrome (and Chromium-based browsers such as Edge, Brave, and Arc) and Firefox. Its sole purpose is to link a user's existing Plaud account to their RoveNotes account in one click, replacing the manual DevTools copy-and-paste step that was previously required during onboarding.

This section describes exactly what the extension accesses, what it transmits, and what it does not store. It applies only to RoveNotes Connector; the rest of this privacy policy continues to apply to the RoveNotes web app and account.

15.1 What the extension does

When a signed-in RoveNotes user clicks the extension's toolbar icon:

1. The extension reads the value of localStorage.tokenstr from the user's web.plaud.ai tab. This value is the session token that Plaud's own web app stores for that user. If no web.plaud.ai tab is currently open, the extension briefly opens one in the background, reads the token, and closes the tab.
2. The user pastes a short, single-use link code (8 characters, valid for 5 minutes) generated by RoveNotes's onboarding page.
3. The extension sends a single HTTPS request to https://app.rovenotes.com/api/onboarding/extension/submit containing that link code and the Plaud session token.

That is the entire extent of the extension's behavior. There is no background activity, no scheduled tasks, no analytics, and no other network traffic.

15.2 Data the extension accesses

• Plaud session token (localStorage.tokenstr from https://web.plaud.ai). Used only to forward to RoveNotes for the account-linking request, then discarded.
• The link code the user pastes into the popup. Used only as the body of the linking request, then discarded.

The extension does not access:

• Cookies, browsing history, bookmarks, downloads, or tabs from any origin other than web.plaud.ai.
• Any content of any page besides the single localStorage value described above.
• Microphone, camera, location, clipboard, or any other device sensor or permission.

15.3 Data the extension stores

Nothing. The Plaud session token is held in memory only for the duration of a single submit request, then released. It is never written to chrome.storage, localStorage, IndexedDB, cookies, or any other persistence layer on the user's device. The link code is likewise not cached — closing the popup mid-flow means starting over with a fresh code.

15.4 Data the extension transmits

The extension makes exactly one outbound request, to:

https://app.rovenotes.com/api/onboarding/extension/submit

It does not contact any other server, including Plaud's own API. It does not include analytics, telemetry, crash reporting, A/B testing, or any third-party SDKs.

15.5 How RoveNotes uses the forwarded token

Once received, the Plaud session token is used to enable RoveNotes's syncing service to read recordings from the user's own Plaud account into the user's own RoveNotes account. Token storage, retention, and deletion on RoveNotes's servers are governed by the rest of this privacy policy (see the "Information we collect" and "Retention" sections above).

15.6 Permissions the extension requests, and why

The extension does not request <all_urls>, cookies, webRequest, storage, notifications, or history.

15.7 Sale, sharing, and advertising

RoveNotes does not sell user data, does not share it with third parties for advertising purposes, and does not use the data forwarded by the extension for any purpose unrelated to the single account-linking function described above.

15.8 Source code

RoveNotes Connector is open source. The exact source corresponding to any published version is available at the public repository linked from the extension's store listing.

15.9 Contact

Questions about the extension's privacy behavior: support@rovenotes.com.

16. Law-enforcement requests

We will disclose personal information when required by valid legal process (subpoena, court order, warrant) or where we have a good-faith belief that disclosure is necessary to protect our rights, users, or the public. We will push back on overbroad requests and notify you where not legally prohibited.

17. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify you by email and post a notice in the Service at least seven days before the changes take effect. The "Effective date" at the top reflects the current version.

18. Contact

Radiant Maple Studios LLC
Carlsbad, California, USA
Privacy: privacy@radiantmaple.com
Legal: legal@radiantmaple.com