Freshservice Import

Privacy & security

How the tool protects your API key, your Freshservice data and your customers, and how we handle personal data.

Security

How your API key and data are protected in practice.

Your API key

  • The key is sent over HTTPS only to this site's own server functions, which use it to call your Freshservice (<domain>.freshservice.com) and nothing else. Requests can't be pointed at any other host.
  • The server functions use the key for that one call. They don't store it, log it or send it anywhere else.
  • The API key is kept in the page's memory only, and is forgotten when you reload. "Remember the API key until this tab is closed" is off by default. When ticked, the key is kept in this browser tab only (session storage), never on a server, and is forgotten when the tab is closed. Don't tick it on shared computers.
  • Recommended: use a key from a dedicated Freshservice agent whose role and groups cover only what the import needs, not an administrator's key. A Freshservice key can do everything its agent can.

What's stored, and where

  • On our server, only your account: your name and email from sign-in, your plan and trial dates, which Freshservice subdomains your account is licensed for, how many rows were sent this period, and an audit log of each send (who, when, which action, the Freshservice subdomain, the ticket number and whether it worked). This is kept in a Supabase database that only the server functions can read.
  • Never stored on our server: your Freshservice API key, your sheets, or ticket and reply contents. These pass through the server functions to Freshservice and aren't kept. Responses are marked not to be cached.
  • In your browser: your settings (domain, default requester, workspace, import type, rate and safety settings, and your display and accessibility choices), the API key only if you chose to remember it, and the tracking list. Tracking records each row already sent: its ticket number, a short summary (for example an email address or subject) and when it was sent. This is what stops a row being sent twice.
  • You can export, import or reset tracking from step 5. Clearing this site's data in your browser removes everything above.
  • One cookie keeps you signed in for up to 12 hours. It's HTTP-only (page scripts can't read it), sent only over HTTPS and signed so it can't be forged. No analytics or tracking scripts are used.

Export, retention and deletion

  • Export: Your data → Download my data in the tool gives you everything stored about your account as a JSON file. The list of rows already sent, and each run's results, can also be exported from the tool.
  • Send log: each entry holds the time, who sent it, the action, the Freshservice subdomain, the ticket number and whether it worked. For a failed send it keeps only the error status and Freshservice's error codes, not the message, which can repeat what was sent. Entries are deleted automatically after 90 days.
  • Lapsed accounts: if an account has had no plan for 30 days after its trial or subscription ended, its data is deleted automatically: everyone's names and emails, and the send log. In billing, every subscription is cancelled and the name, email, phone and address on our Stripe customer record are removed. Invoices and payment records stay with Onelink and Stripe for as long as tax law requires.
  • Delete on request: Your data → Delete account & data does the same straight away, with no refund for the rest of the period. It can be done by the owner of a personal account or an admin of an organisation's account, within 10 minutes of signing in (the tool offers to sign you in again). Tickets already in Freshservice aren't affected.
  • What's kept after deletion: nothing about the people on the account: no names, emails or sign-in IDs, hashed or otherwise. We keep a record of each Freshservice subdomain the account used: that it has had its free trial, and the email domain of the organisation it belongs to (for example acme.co.uk). This is kept only so each Freshservice gets one free trial, whoever signs up for it, and is deleted automatically 24 months after the account is deleted, unless the subdomain is in use on an account again. A bare account record with no names or emails (its dates and rows-used counts and, for an organisation's account, the sign-in service's ID for the organisation, so it returns to the same account if it signs up again) is deleted at the same time. If you're a sole trader using your own email domain, that domain may identify you.
  • Different retention periods can be set per account on request.
  • Data in your browser (settings, tracking, a remembered key) stays until you reset tracking in step 5 or clear this site's data.

Accounts, sign-in and payments

  • Sign-in is handled by WorkOS. We never see or store your password, and your organisation's single sign-on can be used.
  • Payments are sold through Onelink (formerly Link), part of Stripe, as merchant of record. Card details go straight to Stripe and never reach our server or this page.
  • Every server call checks your sign-in, that you still belong to the account, your plan or trial, and that the Freshservice subdomain is licensed to your account. Someone removed from your organisation in WorkOS is moved off its account as soon as WorkOS tells us, and their sessions on it stop working. Templates are tied to the account that made them.
  • Services we use: Netlify (hosting), WorkOS (sign-in), Stripe (billing) and Supabase (account database).
  • Where it runs: the server functions, which handle your requests to Freshservice, run in Frankfurt (EU). Sign-in (WorkOS) and billing (Stripe) are processed by those providers, including in the US, under their data processing agreements.

Only signed templates are accepted

  • Each Excel template is built from your live Freshservice form, then signed on the server (HMAC-SHA256) with a secret that never leaves the server.
  • The signature ties the template to one Freshservice, one import type, one service item or ticket form, one workspace and its exact columns. It's valid for 30 days.
  • Uploads are rejected, with the reason, if the file is a CSV or wasn't made by this tool. They're also rejected if the signature is missing or altered, if columns were added, renamed, moved or removed, if it's for a different item, workspace or import type, if the form has changed since, or if it has expired.
  • The header row and helper sheets are locked, so only data rows can be edited.
  • A signature proves the sheet came from this tool. It can't vouch for what someone typed into it, which is why the checks below exist.

Checks before anything is sent

  • Validated against Freshservice: every row is checked against the live form: required fields, allowed values, category and sub-category combinations, dates, numbers, emails and the form's own validation rules. Rows that fail aren't sent.
  • Confirmation: before the first send, a plain summary says what will happen. For example: how many tickets will be created, changed or closed, how many customer emails will go out, any BCC addresses, and how many rows contain a web address.
  • Plain text by default: descriptions and replies are sent as plain text, so a sheet can't add hidden links, images, forms or other markup to customer emails. A web address typed as text still shows as a link to the recipient, and the confirmation counts those rows. HTML can be switched on in step 1.
  • Allowed CC/BCC domains: if set in step 1, replies can only copy addresses at those domains.
  • Settings stay as they were when checked: changing the domain, default requester, HTML or allowed-domains setting after loading a file clears it, so it's checked again. These settings are locked while sending.

Safe sending

  • Throttled: sending is throttled to a per-minute rate (3 a minute by default) that holds across batches. When Freshservice asks the tool to slow down, the whole run pauses.
  • No duplicates from retries: new tickets, service requests and replies are never retried after a lost response, because they may already have been created. Such a row is marked Uncertain and stays out of every later send until you've looked in Freshservice and marked it done or asked for it to be sent again. Rows already sent are skipped if the same sheet is uploaded again.
  • Mandatory-field checks are only skipped if you say so: Freshservice refuses to resolve or close a ticket with no description (common for service requests). The send confirmation says how many rows that affects, and only if you tick the box are those rows sent again with Freshservice's mandatory-field checks switched off. Each such row is marked in your send log.
  • Only to your Freshservice: IDs in requests must be numbers, and a redirect from Freshservice is treated as an error and never followed, so a request can't be steered to another address.
  • Nothing in the browser console: the tool doesn't write row contents, Freshservice's answers or form definitions to the browser console, so a screenshot or a shared screen doesn't give them away.

Browser protections

  • A strict Content Security Policy lets the page run only its own code and two pinned spreadsheet libraries: ExcelJS 4.4.0, served from this site, and SheetJS 0.20.3 from cdn.sheetjs.com. Each is locked to its exact file by an integrity hash, so the browser refuses it if the file served is ever changed. The page may only connect back to this site, so even a tampered library couldn't send your key elsewhere.
  • The site is HTTPS-only (HSTS) and can't be embedded in other sites (anti-clickjacking). It also sends no referrer and turns off camera, microphone and location access. The tool page itself isn't indexed by search engines.
  • Everything shown on the page from your sheets or from Freshservice is escaped, so it's displayed as text and never run as code.
  • The downloadable CSV report neutralises spreadsheet formulas.

Limits to be aware of

  • Any signed-in account can use the tool with its own Freshservice API key. Without a valid key it can't reach your Freshservice.
  • Whoever controls the code repository or the Netlify account controls what this page does. Keep both behind two-factor sign-in and reviewed changes.
  • Bulk changes are only as correct as the sheet: test with a few rows first.

Reporting a concern

If you think something isn't working as described here, stop any run in progress, rotate the Freshservice API key, and contact support. For anything that looks like a security incident, email support@zestco.uk with the subject Security incident: those are read first.

If there's a personal data breach

A personal data breach is a security incident that leads to personal data being lost, altered, disclosed or accessed without authorisation. For this tool that could be the account data we hold (names, email addresses, the send log), or, while a send is running, the ticket contents and API key passing through our server functions.

Our written process has five steps, and every incident goes through all of them:

  1. Detect: from our logs, the weekly security scan, a notice from a provider, or a report to support. The clocks below start when we become aware.
  2. Contain: stop the exposure. That can mean signing everyone out, rotating our secrets and keys, and taking the affected function or the site offline. If your Freshservice API key may have been exposed, we tell you to rotate it.
  3. Assess: what happened, what data, whose, how many people, for how long, and the likely harm.
  4. Notify: we tell every affected customer within 24 hours of becoming aware, by email to the account's users and organisation admins, with what we know so far, what we've done and what we suggest, and we keep you updated as we learn more. We help you with your report to the ICO, which as controller you must make within 72 hours of becoming aware if the breach is likely to put people at risk. For the account data we hold as controller, we make that report ourselves and tell the people affected where there's a high risk to them.
  5. Record: every incident and near miss goes in our breach register with what we decided and why, and what we changed as a result.

The same commitment is in clause 4.7 of our data processing agreement.

Privacy policy

Last updated 9 November 2026.

Who we are

Freshservice Import is run by ZestCo Ltd (trading as Zest), company number 16694401, registered office Ingles Manor, Castle Hill Avenue, Folkestone, England, CT20 2RD. We're registered with the UK Information Commissioner's Office, registration number ZC278477.

For the account data described below, we are the controller. When the tool passes your Freshservice data (tickets, requests, replies) between your browser and your Freshservice, we act as your processor: we handle it only to carry out the send you asked for, and don't keep it. Our data processing agreement sets out that processing and is part of our terms.

Questions or requests about your data: support@zestco.uk.

What we hold

  • Your sign-in details: name and email address, your sign-in ID from our sign-in provider (WorkOS), and, if you sign in through an organisation, its ID and your role in it.
  • Your account: plan, trial dates, subscription status and billing period, the Freshservice subdomains licensed to the account, and how many rows were sent each period.
  • Your acceptance of the terms: who accepted the Terms & Conditions and Data Processing Agreement for the account, which versions, when, and the browser it was done from; and, at checkout, who confirmed that the subscription is for a business or organisation rather than as a consumer. Kept as evidence of the agreement until the account is deleted, including after that person leaves the account.
  • A send log: for each send, the time, who sent it, the action (service request, new ticket, update, reply or template), the Freshservice subdomain, the ticket number and whether it worked. For a failed send we keep the error status and Freshservice's error codes, not the error message. For a ticket update sent with Freshservice's mandatory-field checks skipped, that it was.
  • Which organisation each Freshservice subdomain belongs to: the email domain (for example acme.co.uk, never a full address) of the first account to connect to it successfully, so other organisations can't use it. Kept while the subdomain is in use and for 24 months after the last account using it is deleted; ask support to change it.
  • Which Freshservice subdomains have had a free trial: the subdomain and when its trial started, so each Freshservice gets one free trial. Kept while the subdomain is in use and for 24 months after the last account using it is deleted. It holds no names or emails.
  • Look-ups of unlicensed Freshservice subdomains: which subdomains an account looked up and when, to limit look-ups to five a day. Deleted after two days.
  • Payment details are held by Stripe, not by us: card details, billing name and address, and payment history. We store only the Stripe customer and subscription IDs, and see the plan, status and billing dates.
  • Hosting logs: our hosting provider (Netlify) records requests to this site, including IP addresses, for security and operation, and keeps them for a short period under its own policy. Our server functions log errors without your API key or sheet contents.
  • Complaints: what you send through the complaint form (your name, email, organisation and what happened) is stored for us by Netlify and emailed to our support mailbox, and kept for as long as the complaint and any follow-up need it.

We never store your Freshservice API key, your spreadsheets, or the contents of tickets, requests or replies. They pass through our server functions to your Freshservice and aren't kept.

In your browser only: the tool keeps your settings and a list of rows already sent (ticket number, a short summary such as an email address or subject, and when it was sent), so a row isn't sent twice. If you tick Remember for this tab, the API key is kept in this tab's session storage until you close the tab. None of this reaches our server. You can reset it in the tool or by clearing this site's data.

Where it comes from, and what's required

  • From you, when you create an account: your name and work email. These are required: without them we can't create an account or tie it to your organisation.
  • From our sign-in provider (WorkOS): your sign-in ID, when you last signed in, and whether your email is verified.
  • From your organisation, if it uses single sign-on: your name, email, organisation ID and your role in it (for example admin or member), as set by your organisation's identity provider. Your organisation decides who can sign in.
  • Sign-up check: when you sign up or sign in, WorkOS sends us the email address you entered so we can check it's a work address. Personal addresses (Gmail, Outlook, iCloud and similar) are refused, and nothing about a refused attempt is kept by us.
  • From Stripe: your plan, subscription status and billing dates, once you subscribe.

Why we use it, and our lawful basis

  • To provide the service you signed up for (contract): signing you in, applying your plan and limits, licensing your Freshservice subdomains, counting rows and billing you.
  • To keep the service secure and fair (legitimate interests): the send log, look-up limits, and checking you still belong to your organisation. After an account is deleted we keep only which Freshservice subdomains have had a free trial and which organisation (email domain) each belongs to, for 24 months, so the free trial can't be started again on the same Freshservice. Nothing about the people on the account is kept.
  • To meet legal obligations: accounting records of what we've been paid, and a check of the country each request comes from (worked out from its IP address by our hosting provider) against the countries and territories where UK sanctions stop us providing the service. A refused attempt is logged with the country and the page only, never with who it was.

We don't use your data for marketing, don't sell or share it for advertising, don't use analytics or tracking scripts, and don't make automated decisions with legal or similarly significant effects about you.

Who processes it for us

  • Netlify — hosting and server functions, and storing complaint form submissions. The functions run in Frankfurt (EU).
  • Supabase — the account database, in Frankfurt (EU).
  • WorkOS — sign-in, including single sign-on. Processed in the US.
  • Stripe — payment processing and our record of your subscription. Processed in the UK, EU and US.

When you pay: subscriptions are sold through Onelink (formerly Link), part of Stripe, as merchant of record. For the payment itself, Onelink and Stripe handle your details as a separate controller under their own privacy policy (onelink.com/privacy): they take the payment, calculate and pay tax, send receipts and invoices, prevent fraud and answer payment questions. You can ask Onelink to delete the payment data it holds, which also cancels the subscriptions bought through it.

Each acts under a data processing agreement with us. Where data goes outside the UK, it's protected by the safeguards in those agreements, such as the UK International Data Transfer Addendum to the EU standard contractual clauses or the UK Extension to the EU–US Data Privacy Framework. The providers that handle your Freshservice data on our behalf, with the safeguard for each, are in the sub-processor list of our data processing agreement; we give 30 days' notice before adding one.

Your Freshservice itself is provided to you by Freshworks under your own agreement with them. We aren't affiliated with Freshworks.

How long we keep it

  • Send log: 90 days, then deleted automatically.
  • Accounts without a plan: 30 days after the trial or last paid period ends, names, emails and the send log are deleted automatically. In billing, every subscription is cancelled and the name, email, phone and address on our Stripe customer record are removed. Invoices and payment records stay with Onelink and Stripe for as long as tax law requires.
  • Deleting your account in the tool (Your data → Delete account & data) does this straight away. It can be done by the owner of a personal account or an admin of an organisation's account, within 10 minutes of signing in.
  • What remains after deletion: no names, emails or sign-in IDs, hashed or otherwise. Only a record of each Freshservice subdomain the account used (that it had its free trial, and its organisation's email domain) and a bare account record (dates, rows-used counts and, for an organisation, its sign-in service ID), to stop the free trial being started again on the same Freshservice. Both are deleted automatically 24 months after the account is deleted.
  • Invoices and payment records are kept by Onelink and Stripe under their own policies, for as long as tax law requires.
  • Different retention periods can be agreed for a customer on request.

Cookies

We use three strictly necessary cookies, and no others:

  • fi_session keeps you signed in, for up to 12 hours. It's HTTP-only, HTTPS-only and signed.
  • fi_state protects the sign-in round trip and lasts 10 minutes.
  • fi_notice carries a one-off message across a sign-out (for example “use your work email” or “your account has been deleted”). It lasts at most 10 minutes and is removed once the message is shown.

We also store some things in your browser's local storage, which never reach our server:

  • fi-a11y: your display settings from the accessibility button (theme, text size, motion, link underlines). Stored only when you change one.
  • tiq.settings and tiq.ledger: the tool's settings and the list of rows already sent, so a row isn't sent twice.
  • tiq.apiKey (session storage): your API key, only if you tick Remember for this tab, and only until the tab is closed.

These are needed for the service, or for a setting you chose, so they don't need consent and there's no cookie banner. To remove them, use Reset in the accessibility panel or the tool, or clear this site's data in your browser. Stripe and WorkOS set their own cookies on their pages when you pay or sign in.

Your rights

You can ask for a copy of your data, or have it corrected, deleted, restricted or moved, and you can object to how we use it. You can download your data yourself from Your data → Download my data in the tool, and delete your account there too. For anything else, email support@zestco.uk. We'll reply within one month.

If you're unhappy with how we've handled your data, please complain to us first (see Complaints about your data). You can also complain to the Information Commissioner's Office at ico.org.uk.

Complaints about your data

If you think we've got something wrong with your personal data, tell us. It's free, and you don't need to use any particular words.

  • Use the complaint form and choose How my personal data has been handled.
  • Or email support@zestco.uk with the subject Data protection complaint. Say what happened, and include the email you sign in with so we can find your account.

What happens next:

  1. We acknowledge your complaint within two working days, and within 30 days at the very most.
  2. We look into it, and may ask you for more details.
  3. We tell you the outcome without undue delay: what we found and anything we've changed.

If you're not happy with our response, or we don't respond, you can complain to the Information Commissioner's Office at ico.org.uk.

Changes

If we change this policy, we'll update the date at the top. If a change materially affects how we use your data, we'll tell account holders by email before it takes effect.

How the tool protects your API key and data in practice is described under Security above.