OS Outreach OS

Chrome Extension Privacy Policy

Privacy Policy

This policy explains what data Outreach OS handles, how that data is used, and how users stay in control of locally stored extension information.

Local-first storage Settings, templates, logs, and metrics are stored in the user's browser.
No data sale User data is not sold, rented, or shared with advertisers or data brokers.
No passwords collected The extension does not collect or store Instagram or Google passwords.

Data Handled

Outreach OS handles data that users provide or make available while using the extension.

  • Google Sheet URLs entered by the user.
  • Instagram profile URLs and row data loaded from a user-provided Google Sheet.
  • DM templates, comment templates, and extension settings.
  • Automation logs, status messages, and task metrics.

How Data Is Used

This data is used only to run the selected Outreach OS workflow, personalize message or comment templates, and display status, logs, and settings inside the extension.

Storage

Settings, templates, logs, and metrics are stored locally in the user's browser using Chrome extension storage. Users can remove extension data by uninstalling the extension.

Sharing

We do not sell, rent, or share user data with advertisers or data brokers. Outreach OS does not transmit user data to our own servers.

Third-Party Services

The extension accesses Instagram and Google Sheets only as needed for the user-facing workflow. Google Sheet data is fetched from docs.google.com using the user's browser session.

Instagram and Google are third-party services with their own terms and privacy practices. Users are responsible for using Outreach OS in a way that complies with the services they access.

Credentials

Outreach OS does not collect or store Instagram passwords, Google passwords, cookies, or access tokens.

Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

For privacy questions or support requests, contact the developer.

mert.yaylaci@gmail.com Mert Yaylaci