Opt in the BrowserHome

Privacy Policy

What the browser processes, what basic visitor analytics measures, what Google Drive shares with the app, and what stays under your control.

Effective

At a glance

Opt in the Browser solves optimization models in your browser. Solving does not send models to an Opt in the Browser application server. Google Drive is optional and is used only when you choose to connect it.

The application does not sell Google user data, use it for advertising, or use it to train machine learning models.

Basic website analytics

The website uses Overtracking only to count visitors and report their approximate country. Loading the analytics script requires a network request that discloses routine technical information, including an IP address, to Overtracking. Country is inferred from that network information.

This installation is not used for advertising, custom interaction goals or session recordings. It does not intentionally collect optimization models, solver input or output, local workspace files or Google Drive file contents. Overtracking processes the basic analytics data under its own privacy policy.

Google data the application accesses

When you connect Google Drive, the application requests the https://www.googleapis.com/auth/drive.file permission. This permission is limited to files created by the application or files and folders you explicitly open or share through Google Picker. It does not provide general access to every file in your Drive.

For the items you make available, the application may process:

  • File and folder identifiers, names, types, parent relationships and version information.
  • Capabilities needed to determine whether an item can be read, changed or deleted.
  • The contents of supported text files selected for the workspace.
  • Changes needed to create, edit, rename, move, synchronize or trash workspace items.

How Google data is used

Google Drive data is used only to present the folder you mounted as an editable workspace, load files you selected, save your changes and synchronize the workspace at your request or while the workspace is open.

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Where data is processed and stored

Google Drive file content travels directly between your browser and Google APIs. Opt in the Browser does not operate a backend that receives or stores your Drive access token or file content.

  • OAuth access tokens are kept only in browser memory. They are not written to cookies, localStorage, Pinia or IndexedDB. Reloading the page or token expiry requires reconnecting.
  • IndexedDB may retain a local workspace cache, selected folder metadata, file contents needed for recovery and pending synchronization operations on that device.
  • Google Identity Services and Google Picker are loaded from Google when you use the Drive integration.
  • The website is delivered through Netlify, which may process routine network information such as IP addresses and request logs under its own privacy terms.

Sharing and disclosure

The operator does not sell, rent or share Google user data with advertisers or data brokers. Data is disclosed to Google only as needed to perform the Drive operations you request. Technical network data may be processed by the hosting provider to deliver and protect the website.

Your controls and deletion

  • Disconnect Google Drive in the application to clear the in-memory access token.
  • Revoke the application from your Google Account permissions.
  • Clear this site’s browser data to remove its local IndexedDB cache and preferences.
  • Delete or restore Drive files through the application or Google Drive, subject to Drive’s rules.

Security and retention

Access is limited through the per-file OAuth permission and short-lived access tokens. Locally cached data remains on the device until the browser removes it or you clear the site’s data. Files in Google Drive remain there until you delete them under Google Drive’s retention behavior.

Changes to this policy

This policy may change when the application or its integrations change. The effective date at the top identifies the current version. Material changes to Google user data practices will be reflected here before they take effect.

Contact

Questions about privacy or Google user data can be sent to sebastian.herrera.monterrosa@gmail.com.