Privacy

Privacy policy

This policy explains what SlashNijo collects, why, and what we do not collect. It covers the website and the Chrome extension. Last updated 10 September 2026.

Who this covers

SlashNijo is a snippet tool: you create shortcuts like //mail, type them in a text field, and the matching text is inserted. Romain Lourenco operates the website and the extension.

Email hello@slashnijo.com.

You can use the playground and the extension without an account. An account is only for backup and sync across devices.

What the extension can see

The extension injects a small script on web pages so // works in the field you are already typing in (Gmail, Notion, chats, forms, and similar). That is why Chrome asks for access to all sites.

  • It looks at the current text field only enough to detect a //key at the caret and to show matching snippets.
  • When you confirm with Tab or Enter, it replaces the key with the snippet you chose.
  • It does not send the contents of web pages to our servers.
  • It does not read your browsing history, cookies of other sites, or files on your computer.
  • It does not sell, barter, or use your data for advertising.

Snippets live in Chrome storage on your device until you sign in. If you sign in, keys and snippet content are copied to your account so they can sync.

Data stored on your device

No account needed for this. It stays in your browser unless you later choose to sync.

  • Your snippets (the key and the text to insert).
  • How many times you expanded a snippet, and an estimate of time saved.
  • A random device id, used to count usage without asking for your name.
  • If you sign in: a session token so the extension can sync.
  • On the website playground: snippets and a device id in localStorage. That playground is local. It is not your account.

Uninstalling the extension deletes the local Chrome copy. Website playground data stays in that browser until you clear site data.

Data we store on our servers

If you never create an account and never send uninstall feedback, we still may receive anonymous usage pings from the playground or the extension:

  • A device id.
  • That an expansion happened, the estimated time saved, and the snippet key (for example mail), not the snippet body and not the rest of the page.
  • Totals used for the public counters on the homepage.

Do not put secrets in the key name. Keys can be stored with usage events. Put secrets only in snippet content, and only if you accept that content is stored locally and, after sign-in, on your account.

If you create an account, we also store:

  • Username, email, and a hashed password. We do not store your password in plain text.
  • If you sign in with Google: the identifiers Google shares for sign-in (such as email and name).
  • Your synced snippets (keys and content).
  • Devices linked to the account, expansion counts, and estimated time saved.
  • Session cookies and, for the extension, a hashed access token.

If you fill the uninstall form, we store the reason, optional comment, browser user agent, device id if present, and a snapshot of the account at that time (username, email, snippet count, usage). That form is optional.

Why we use this data

  • To expand //keys on the pages you choose to type in.
  • To sync your library when you sign in.
  • To show you, and the public homepage, expansion counts and estimated time saved.
  • To keep sessions signed in (cookies and tokens).
  • To understand why the extension was removed, when you send that form.
  • To secure the service (abuse, debugging, keeping accounts apart).

We do not use snippet content to train public AI models, to advertise, or to profile you for unrelated products.

Legal bases (EEA and UK)

  • Contract: providing the product you asked for, including sync if you have an account.
  • Legitimate interests: anonymous product stats, optional uninstall feedback, security.
  • Consent: Google sign-in, when you choose that button.
  • Legal obligation: if we must keep or disclose something the law requires.

Cookies and similar storage

SlashNijo uses cookies that are needed to sign in and stay signed in (session, CSRF, and related auth cookies). We do not set advertising cookies and we do not run a third-party analytics pixel today.

The playground and a device id use localStorage on the website. The extension uses Chrome storage. Those are not advertising trackers.

Sharing

We do not sell your personal data.

  • Hosting and database providers that run this website, only to operate it.
  • Google, only if you sign in with Google, under Google's terms and privacy policy.
  • Authorities, if the law requires it.

People who operate admin tools for SlashNijo can see account and uninstall-feedback records in order to run the service. They are not a marketplace of your snippets.

Retention and deletion

  • Local extension data: until you delete a snippet or uninstall.
  • Account and synced snippets: until you delete the account or we delete it after a valid request.
  • Anonymous usage totals may remain as aggregate numbers that no longer identify you.
  • Uninstall feedback: kept to improve the product, without using it for ads.

To access, correct, export, or delete account data, email hello@slashnijo.com. Say which email or username the account uses. We may need to verify it is you.

There is not yet a delete-account button in settings. Email is the way to ask for erasure until that exists.

Your rights

If you are in the EEA, UK, or another region with similar rules, you can ask for access, correction, deletion, restriction, objection, and a copy of the data you provided. You can also complain to your local data protection authority. In France that is CNIL.

Children

The product is not aimed at children. Do not create an account if you are under 16 in the EEA, or under the digital-consent age where you live.

International processing

Servers are hosted by OVH SAS, 2 rue Kellermann, 59100 Roubaix, France. The site runs in OVH datacenters in the European Union. If you sign in with Google, Google also processes the identifiers needed for that sign-in.

Changes

If this policy changes in a material way, we will update this page and the date above. Keep using the site or the extension only if you accept the current version.