Italiano

Privacy and terms of use

What the extension stores, what it never sends anywhere, and the few things you agree to by using it.

The short version

Ticket Assistant does not have an account, a login, a server run by its author, analytics, advertising, or cookies. Everything you write stays in your own browser. Nothing is sent anywhere unless you point the extension at an address yourself, and it asks you before it does.

This page describes version 5.6 and applies to the extension published on the Chrome Web Store by Variety Project. Last updated: 8 September 2026.

Who is responsible

The extension is published by Variety Project, an individual developer, and can be reached at vrt.varietyproject@gmail.com for anything on this page — questions, complaints, requests about your data.

Because the extension never sends your content to the author, there is normally nothing for the author to give you, correct or delete: your data is on your own computer, and you remove it by removing the extension or clearing its data yourself.

What is stored, and where

All of the following lives in the storage your browser reserves for this extension, on the computer where you installed it:

  • Your content: tabs, sections, entries, contacts, procedures, form texts, and the images you attach (images are kept in a separate local database so that saving stays fast).
  • Your settings: theme, view mode, interface language, background color, number of tabs.
  • Your synced sources: the name you gave each one, its address or file name, the network path if you typed one, and whether it refreshes automatically.
  • Passwords of encrypted feeds, so a protected source can refresh without asking every time. They are stored only on that computer and are never included in an export.
  • The install code (in the shape TA-0000-0000-0000): a random identifier used to say which installations may edit a shared feed. It is not derived from your computer, your browser or you, and it does not identify a person.

None of this is transmitted to the author or to any third party.

The one exception: Chrome sync

The install code is written to chrome.storage.sync. If you are signed into Chrome with synchronisation switched on, that means this one value — the code, and nothing else — travels through Google's sync service to your other Chrome profiles, under Google's own privacy terms. If sync is off, it never leaves the computer. No other data of yours is written to synced storage.

When the extension uses the network

Only when you have added a synced source, and only towards the address you typed:

  • It requests the JSON file of that source, and the images that file references.
  • Requests are sent without cookies or credentials, and without caching.
  • Chrome asks for your permission for that specific domain at the moment you add the source. You can withdraw it at any time from the extension's settings in Chrome.
  • The server you point at will see, as any web server does, your IP address and the request. If that server is your company's, its own rules apply — the extension adds nothing to the request.

A source that is a local file or a folder on a network share is read directly through the browser's file access, after you have selected it yourself. Nothing goes over the internet in that case.

Shared feeds and other people's data

A shared feed is a file you publish and you control. If you put colleagues' names, phone numbers or email addresses in it, you are the one deciding to do so, and — in a work setting — your employer is normally the one responsible for that data under data protection law. The extension is a tool that reads and writes the file you point it at: it does not send that file to the author, does not keep a copy anywhere else, and cannot see what is in it.

Two consequences worth stating plainly:

  • Who can read a shared file is decided by the permissions of the share it sits on, not by this extension. The editor code is a guard against accidental clicks, not an authorisation system.
  • Encrypting a feed protects the file where it sits. Once a feed is open on someone's computer, its content is in that computer's local storage in the clear.

Cookies

The extension uses no cookies, and no cookie-like tracking technology: no tracking pixels, no fingerprinting, no advertising identifiers. There is nothing to consent to and no banner to show. What it uses is the browser's own extension storage, which is not a cookie and is never shared with any website.

The extension does not read, write or have access to the cookies of the sites you visit. It does not have permission to do so and does not ask for it.

Links out of the extension

Three links leave the extension, and only when you click them:

  • The Chrome Web Store page, to rate the extension.
  • Ko-fi, for an entirely optional donation. Ko-fi is a third-party service with its own privacy policy and terms; the extension sends it nothing and receives nothing back, and no feature depends on donating.
  • An email address, which opens your own mail program. If you write, you are sending your address and your message directly to the author, who uses them to answer you and nothing else.

No page of the extension loads code, fonts, styles or images from any external server.

Children

The extension is a work tool for support teams. It is not directed at children, and it collects nothing from anyone.

Terms of use

Short, because there is not much to agree to: the extension is free, it takes nothing from you, and it has no account to suspend.

What you may do

Install it and use it, at work or privately, on as many computers as you like, and share feeds with whoever you want. You keep every right over the content you write: it is yours, it stays on your machines, and the author has no claim to it.

What you are responsible for

  • What you put in your sections and in your shared feeds, including anyone else's personal data, and whether you are allowed to put it there.
  • Where you publish a feed and who can reach it.
  • Keeping the password of an encrypted feed. It is written nowhere: if it is lost, that file cannot be opened again, by anyone, including the author.
  • Keeping your own backups. The extension can export everything into one file; whether you do so is up to you.

No warranty

The extension is provided as it is, without any warranty, express or implied, including of fitness for a particular purpose. To the fullest extent the law allows, the author is not liable for lost data, lost work or indirect damages arising from its use. Where the law of your country gives you rights that cannot be waived — and, as a consumer in the European Union, it does — those rights are unaffected by this paragraph.

Changes and availability

The extension may be updated, changed or withdrawn from the Chrome Web Store at any time. Data already on your computer is not deleted by an update. If this page changes in a way that matters, the change is described in the guide's changelog.

Which law

The author is based in Italy; Italian law applies, and the mandatory consumer protections of the country where you live apply to you regardless.