Slash privacy policy

Effective date: November 2, 2026

This policy describes Slash — Emoji Shortcuts for Instagram. Version 1.3.4 and earlier perform all extension processing locally. Version 1.4.0 adds optional usage reporting to Google Analytics; reporting stays off until you explicitly enable it.

Messages and emoji choices stay on your device

Slash temporarily reads text and cursor position in a supported Instagram message editor to detect a slash query and insert the emoji you choose. This happens locally. Slash never sends message text, slash queries, selected emoji values, recipients, Instagram account identities, conversation identifiers, or page URLs to its developer or analytics backend.

Emoji favorites, their order, and per-emoji ranking counts remain in Chrome extension-local storage and are not uploaded or synced. Version 1.4.0 also maintains total picker-opening and insertion counts locally, which you can view in the extension popup even when sharing is off.

Optional usage reporting in version 1.4.0 and later

You can choose to share usage events in Slash’s toolbar popup. There are no notices, prompts, or blocked features in the emoji picker. Choosing not to share does not restrict emoji features. Sharing requires your affirmative choice and Chrome’s optional permission for the Slash website reporting host.

If you enable sharing, Slash sends picker-opening and successful emoji-insertion events, their time rounded to a second, the extension version, a session number, random event identifiers, and a randomly generated installation identifier. No message content, search terms, selected emojis, recipients, Instagram identities, conversation identifiers, or page URLs are included. Reporting identifiers are generated only after you enable sharing and are not tied to an Instagram account.

A picker opening means a new slash-picker session, not each typed character. An insertion means Slash inserted an emoji into a message draft; it does not establish that the message was sent or retained. No historical activity is uploaded when you enable sharing.

Events are batched approximately once a minute while Chrome is running. Unsent data is limited to 2,000 events and expires after 72 hours. Reports are best effort: offline conditions, blocked requests, or ambiguous retries may cause missing or duplicate events. The developer reads aggregate event totals in Google Analytics.

Your choice and controls

Open Slash’s toolbar popup to turn usage sharing on or off. Turning sharing off discards unsent events and the local reporting identifier. Revoking the optional reporting-host permission also turns reporting off. Previously shared events remain subject to Google Analytics retention settings; event-level data retention is configured separately from standard aggregate reports. Enabling sharing again creates a fresh identifier, which can affect user totals.

Removing the extension clears its local settings and counters. Reinstalling starts with default preferences and sharing off. There is no user account, advertising identifier, cross-site tracking, or sale of data.

Service providers and security

Optional usage events are transmitted over HTTPS to a fixed endpoint on instagram-slash.com, hosted with OpenAI Sites, and relayed to Google Analytics 4. The developer uses these counts only to understand and improve Slash’s emoji features. The relay forwards only the disclosed event fields; it does not forward cookies, IP-address headers, browsing URLs, or arbitrary message data. Service providers receive the connection information needed to serve requests, such as an IP address, and may retain operational logs under their own policies.

The relay uses Google’s EU collection endpoint. This is not a promise that Google Analytics data is stored only in Ireland or only in the EU; Google processes it under its Analytics terms and privacy policies. The Google Analytics credential stays on the website server and is not included in the extension. Advertising personalization and ad-user-data consent are denied in reported events. No advertising, cross-site tracking, or user-profile features are added.

Slash’s use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is not used for advertising, creditworthiness, lending, or unrelated purposes.

Permissions

Storage saves local preferences, counters, sharing choices, and pending usage events. Alarms schedules uploads for opted-in events. Instagram access runs the emoji picker only in supported message fields. Optional access to instagram-slash.com allows uploading usage events only after you enable sharing. Slash does not request browser history, cookies, contacts, camera, microphone, or location access.

Website and Chrome Web Store discovery

The website’s Add to Chrome link contains campaign tags identifying the Slash landing page. Google’s Chrome Web Store analytics processes listing visits and installation events under Google’s policies. This store-listing analytics integration does not add Google Analytics tracking inside the extension or give the developer access to message text. Website visits and the provider’s infrastructure are subject to the hosting provider’s own policies.

Instagram continues to process messages you send under its own policies. Slash is independent and is not affiliated with or endorsed by Instagram or Meta.

Contact and changes

For privacy questions, use the developer contact shown on Slash’s Chrome Web Store listing. This policy will be updated before material changes to these practices, with a revised effective date and in-product disclosure where appropriate.