Aure for Chrome: privacy.
What the Chrome extension sends, what it keeps, and what it never touches. Last updated 2 September 2026.
Aure for Chrome puts the Aure app in your browser's side panel, the same app that runs at aurecard.com and in the Aure desktop apps, and adds one thing only a browser extension can do: fill the form in front of you, from your voice or from a note in your account. This page says exactly what data that involves. It is written to be checked against the extension's source, which ships unminified.
The app in the panel
The panel shows aurecard.com itself, signed in as you. Recordings, notes, tasks and everything else you do there are handled exactly as they are on the website and are covered by your Aure account terms; the extension adds no collection of its own to that. Signing in happens in a normal browser tab; the extension then hands that session to the copy of the app in the panel and keeps no other copy.
What leaves your browser
| Data | When | Where it goes | What happens to it |
|---|---|---|---|
| Your voice (microphone audio) | Only while you hold Record in the Aure side panel | Aure's own servers at aurecard.com | Transcribed, used to fill the form, then discarded. Dictation audio is not stored. |
| Form field labels, placeholders and field types | When you press Fill | Aure's own servers | Used once to work out which box is for what. Not stored beyond the request. |
| Your Aure sign-in session | Read from your open aurecard.com tab | Sent only to aurecard.com with each request | Identifies your account. Held in memory for the session; nothing is written to disk by the extension. |
What never leaves the page
- What is already typed in the form. The extension reads labels so it knows what a box is for; it never reads or sends what is in it.
- Password and credential fields. Fields that look like passwords, one-time codes, card numbers or similar are skipped entirely.
- The rest of the page. Nothing outside the form fields you are filling is collected: no page text, no browsing history, no other tabs.
What the extension writes
Only the values you asked it to fill, into the boxes on the page you pressed Fill on, highlighted in amber so you can read them first. It never submits a form. You press the page's own save or submit button, or you press Undo and every filled value is restored.
Permissions, and why each one exists
- Read the page you are on, when you click Fill (
activeTab,scripting): to find the form fields and write into them. Granted per click, on the page you are looking at. - Side panel: the extension's own interface lives there.
- Offscreen document: Chrome's only route for an extension to record audio while its panel is open.
- aurecard.com: to talk to Aure's own API and read your Aure sign-in from the app tab.
- Optional access to other sites: asked for the first time you press Fill on a site, using Chrome's own prompt, and remembered per site. Aure does not request access to all websites at install.
What we do not do
- No analytics, tracking pixels or third-party scripts in the extension.
- No selling or sharing of data with third parties.
- No use of your data for advertising, credit decisions, or any purpose unrelated to filling the form you asked to fill.
- No remote code: everything the extension runs ships inside the extension package.
The microphone has a hard stop: if the side panel closes, is navigated away or crashes while recording, the recorder is shut down and the audio is discarded. A hot microphone with no visible control is the one state this extension is built never to be in.
Notes you fill from
When you fill from an existing Aure note, that note is already in your Aure account and is covered by the Aure account terms. The extension fetches it over your signed-in session and does not keep a copy.
Contact
Questions about this policy or a data request: reach Aure through aurecard.com.