Staff Data Handling & Privacy Policy

FILLIT Support Desk - last updated 12 October 2026

1. Purpose and scope

FILLIT Diesel Trading LLC ("FILLIT", "we") uses the Support Desk to record and handle customer requests. Doing that means we hold personal data about our customers and about our own staff. This policy sets out how that data must be handled.

It applies to everyone who signs in to the Support Desk: agents, department admins, global admins and Management, whether permanent, temporary or contracted.

It covers data inside the Support Desk and any copy of it, wherever that copy ends up (screens, printouts, emails, phones, chat messages).

This is an internal staff policy. Customers are covered by a separate customer privacy notice and terms of service.

2. What data the Support Desk holds

Customer data

Staff data

What should not be in the Support Desk

Do not record anything the job does not need. In particular, never type in full card numbers, bank account numbers, passwords, Emirates ID or passport numbers, or health details. If a customer sends any of these, do not copy them into a ticket; record only that they were received and handled.

3. Who can see what

Access is based on your department and role. The system enforces these rules itself; do not try to get around them.

You may look at a customer or ticket only when you need to for your work. Being able to open a record is not a reason to open it.

4. Rules for handling customer data

  1. Need to know. Open, read and share customer data only for the ticket you are working on.
  2. Keep it in the Support Desk. Do not copy customer data into personal notes, personal email, WhatsApp, personal cloud storage or spreadsheets on your own device. If data must leave the system (for example to a supplier), share only what is needed, through FILLIT work tools, and note it on the ticket.
  3. No photos or screenshots of customer data on personal phones. Work screenshots go into the ticket, not into chats.
  4. Internal notes stay internal. Write internal notes as if the customer might one day read them: factual and polite. Check twice before posting a customer reply.
  5. Keep subjects plain. Do not put phone numbers, invoice amounts or other personal details in ticket subjects; subjects appear in notifications and emails.
  6. Right customer, right ticket. Before replying or sharing anything, check the customer and company match the ticket.
  7. Correct mistakes. If you find wrong or out-of-date customer details, update them.
  8. Do not share your account. Never let anyone use your sign-in, and never sign in for someone else.
  9. Ask if unsure. If you are not sure whether something is allowed, ask your department admin before doing it.
  10. In case of a password leak, please revoke your existing password and create a new one.

5. Sign-in, sessions and shared computers

6. Email notifications

7. Where data is stored and processed

Data is encrypted while it travels over the internet (HTTPS) and while stored by the providers we use. Database access rules make sure each person sees only what their role allows, even if the application has a fault.

8. How long we keep data

DataKept for
Sign-in log30 days
System error log30 days
Record of sent notification emails30 days
Unsent drafts in your browserUp to 14 days, or until you sign out
Tickets, comments and customer records1 year
Staff accountsNever deleted

Do not delete tickets or customer records yourself to "tidy up". Old records are deleted automatically, following this table.

9. Cookies and browser storage

The Support Desk uses only its own cookies, only for things it needs to work. There are no advertising, tracking or third-party analytics cookies.

NamePurposeHow long
sb-...-auth-tokenKeeps you signed inUntil you sign out or the session ends
fillit_last_seenSigns you out after 60 minutes idle or 12 hours12 hours
fillit_cookie_noticeRemembers that you saw the cookie notice for this sign-inUntil you sign out
themeLight or dark mode1 year
sidebar_collapsedWhether the side menu is collapsed1 year

Sign-in cookies cannot be read by scripts on the page, are sent only over HTTPS, and are not sent to other websites.

Your browser also keeps unsent drafts of ticket replies on your own computer for up to 14 days. They are cleared when you sign out.

You see a short cookie notice each time you sign in.

10. Data incidents and how to report them

A data incident is anything that puts customer or staff data at risk, for example:

What to do

  1. Report it straight away to Customer support at admin@fillit.co or support@fillit.co, even if you are not sure it is serious. Do not wait to investigate yourself.
  2. Do not delete anything that shows what happened.
  3. If a device is lost, also tell IT so your Microsoft account can be signed out everywhere.

The person responsible will assess the risk, contain it, and decide whether customers or the authorities must be told. Under UAE law, serious breaches may need to be reported to the regulator and to affected people without delay. Reporting an honest mistake quickly is always better than hiding it.

11. Customer requests about their data

Customers may ask to see the data we hold about them, correct it, delete it, or stop us using it.

Correcting a simple mistake in contact details (a wrong phone number, a misspelt name) is part of normal work and does not need to be passed on.

12. Responsibilities, review and contacts

Breaking this policy may lead to access being removed and to disciplinary action, in line with FILLIT's HR policies.

This policy is reviewed at least once a year, and whenever the Support Desk changes in a way that affects personal data.