Privacy

For Ottofill version 1.5.1. Last updated 26 October 2026.

Ottofill (Luma Autofill) saves and reuses approved registration answers on lu.ma and luma.com. It has no account, backend, analytics, telemetry, cloud sync, paid API or remote code. The extension makes no network requests.

What is accessed

The extension identifies accessible registration questions, native field types, option labels and field constraints on supported Luma pages. A scan determines whether supported fields already contain a response so it can preserve that response. It does not record keystrokes or silently save form values.

Automatic badge scans send these question metadata and filled/empty flags to the extension background worker. They do not send typed answer text or return saved answer values to the page. The worker computes a per-tab ready-answer count and updates Chrome's native badge. Current metadata is kept only in memory and refreshed when forms, fields, navigation or saved answers change. The current Luma tab URL is checked to identify supported pages and route form requests. No form metadata, event URL or browsing-history log is persisted by this feature.

After a supported field changes, in-page controls offer to review reusable answers. Clicking Save answers reads supported nonempty responses into a temporary preview. The preview shows new and changed answers; unchanged saved answers are omitted. Only selected answers approved by the final Save action are persisted. Updating an existing entry requires explicit selection. Closing a preview discards its unsaved selections.

Identity and contact fields, credentials, payment details, government identifiers, consent choices and other sensitive fields are excluded through labels, field types and metadata. These safeguards cannot understand every sensitive value placed in an innocuous field. Review the preview and do not intentionally store secrets.

During a deliberate popup inspection, save or Autofill action, the extension may briefly open and close supported Luma dropdowns to verify their option labels and committed selection markers. It skips active user searches and consent/terms widgets. Option catalogues stay in page memory and are not stored with browsing metadata. Automatic badge scans never open dropdowns. An invalidated session disables its old actions and stops observing the form; it never discards answers or reloads the page automatically.

Local profile and migration

The version-2 profile contains facts (company, job title, LinkedIn, GitHub, X/Twitter and industry), intent answers (work, biography and goals), short/long variants, custom question/answer records, custom field types and review settings, generated identifiers, update timestamps, a schema version and a revision. It lives only in chrome.storage.local. There is no additional application-level encryption.

An existing version-1 answer library migrates to exact custom answers marked for review. Original labels, types, ids, timestamps and full values are retained. The old record stays locally as a recovery copy until Delete all. No event URL or browsing history is stored.

You may edit or delete entries from Saved answers. Delete all saved answers in Settings, after confirmation, clears both the active profile and legacy recovery answers, leaving empty schema/revision metadata. Removing the extension removes its Chrome-managed storage; independent device backups are outside the extension's control.

Filling and Undo

A deliberate Autofill or recommendation action sends only relevant saved-answer candidates to the supported form. Strong matches can fill empty fields; uncertain text matches and inferred checkbox preferences remain unselected until you choose them and click Apply. Recommendations use local phrase matching and saved profile/work evidence; they are not sent to an AI service. Applying one does not save a new profile entry.

In-page suggestions are displayed within the website and may be accessible to its scripts before Apply. Reviewing suggestions in the extension popup keeps that display inside the extension until a fill is requested. A fill inserts approved values into empty matching fields. Facts are highlighted green; intent/review answers amber. The extension never submits registrations or changes consent choices.

Luma and event organisers can access values inserted into their page, including any processing the website performs before submission, under their own policies. The extension itself makes no external requests containing the profile or form data.

Undo keeps original and inserted values in memory for fields changed by the current page's fill operations. It preserves subsequent edits and skips changed or replaced fields. Radio and custom single-select Undo are explicitly reported as manual when there is no verified clear action. Multi-select Undo removes only unchanged extension-added selections. Undo history is not persisted and is discarded when the form or page lifecycle ends.

Import and export

Export downloads the active profile as JSON only after a user click. That file contains personal answers; its storage or sharing is controlled by you. Import reads a user-selected local JSON file, validates it, and requires confirmation before replacing the active profile. Failed validation leaves current data unchanged. Neither operation uploads data or uses a server.

Permissions and access

storage stores approved profile data locally. Direct storage access is limited to trusted extension contexts.
Host access and content scripts are restricted to https://lu.ma/* and https://luma.com/*, without subdomains.
No activeTab, broad tabs, scripting, clipboard, account, cookie, authentication-token or broad host permission is requested.

The content script receives only data needed for a user-requested fill or recommendation or the current save preview, not unrestricted profile storage access. Automatic badge counting returns counts without saved answer values. No page postMessage bridge is provided. Website-generated synthetic clicks do not authorize in-page actions.

No information is sold, sent to advertisers or used for model training by this extension.

Support and this website

This policy describes Ottofill's extension data handling. The extension itself contains no analytics. This website is different and is described here.

This website is hosted on Vercel, which processes ordinary web-request metadata to deliver pages. It uses Vercel Web Analytics to count page visits. That service does not use cookies. It records the page visited, the referring site, and general browser, operating system, device type and country information, and reports them to the site owner as totals. It does not see anything stored in the Ottofill extension. The website loads no other external scripts and no remote fonts.

If you email support, your email address and message are used to respond to that request. Do not send secrets, personal form answers or complete profile exports.

Publication details

Ottofill is an independent product by Elroy Chua and is not affiliated with Luma. For privacy questions, contact elroymx@gmail.com or visit Ottofill support.