Skip to content
frontforge
  • Report Server
  • Editions
  • Docs ↗
  • Consulting
  • Contact
  • Sign in
  • Get it free

On this page

  • When you send an enquiry
  • When you ask for a Community licence
  • Analytics, only if you agree
  • Cookies
  • Server logs
  • The client portal
  • Who else is involved
  • How long we keep things
  • Your choices
  • Changes to this page
  • Getting in touch

Privacy

What we collect, and what we don't

Last updated 1 November 2026

This site collects very little. There are no advertising trackers, no third-party fonts or scripts loading in the background, and nothing is sold or shared for marketing. This page sets out exactly what happens.

Shopify apps we publish have their own page — Privacy for Shopify apps — because they read shop data that this website never sees.

When you send an enquiry

The contact form asks for your name, email address, an optional company name, what the message is about (Frontforge Report Server, a project, or something else), and your message. The app support form also asks which app and which shop the message is about. When you submit either, we record the IP address the request came from and your browser's user-agent string — these help us block automated spam and nothing else.

Both public forms run a Cloudflare Turnstile check before a message is stored. That is a bot check, not analytics: Cloudflare sees the token and the address the request came from, and we do not use it to understand how the site is used. A failed check is answered as a success and nothing is recorded, so it is not a way to probe what we accept.

That information is stored in a database on a server we run, and a copy is emailed to us so we see it promptly. We use it to reply to you and to carry on the conversation if it goes further. We don't add you to a mailing list, and we don't pass your details to anyone else.

If you are a client with a client portal account, enquiries sent from this form appear there when the email address on them matches the one you signed in with — alongside their status and any replies from us. That is the only way an enquiry becomes visible to anyone other than us, and it takes a verified email address to happen.

When you ask for a Community licence

The Community licence form asks for your email address and, if you choose, your name, your company and a rough number of employees. We sign a free licence for Frontforge Report Server and email it to that address. The licence is made out to your company, or to your email address if you leave the company blank, and it carries your email address as well.

We store what you typed, the licence we sent and when we sent it. We use it to send you the same licence again if you ask with the same address, and to know who uses the product. Nothing else about you is stored: the address the request came from is used only in memory, to limit how many licences can be asked for at once, and appears otherwise only in the server logs below. The form runs the same Cloudflare Turnstile check as the other public forms, and SMTP2GO delivers the email.

Once you have the licence, it stays on your own server. Frontforge Report Server checks it there, offline, and never contacts us, so we don't learn where, how or whether you use it.

If you have a MyAccount account with the same email address, or create one, we show the licence there so you can copy or download it again. We match it to the account by that address, which MyAccount has already confirmed with a one-time code. You can also add a Community licence sent to a different address by pasting it in; we then record that it is on your account. In both cases we store only which licence is on which account and when it was added. Nobody else's account shows it unless they hold the licence and add it themselves.

The box for product emails is separate, optional and unticked to start with. If you tick it, we record that and when, and use your address only to tell you about new releases and features of Frontforge Report Server. Leaving it unticked on a later visit doesn't undo an earlier yes, because anyone who knows your address could submit the form; to stop the emails, ask us (see Your choices).

Analytics, only if you agree

We use Microsoft Clarity to understand how the site is used — which pages hold attention, and where people get stuck. It records anonymised session activity such as clicks, scrolling and navigation.

Clarity does not load unless you accept it. If you decline, nothing is requested from Microsoft at all — the script is never fetched, rather than fetched and told to stay quiet. You can change your mind at any time using Cookie settings at the bottom of any page.

If you do accept, your data is handled by Microsoft under the Microsoft Privacy Statement.

Cookies

This site sets no cookies of its own. Your analytics choice is kept in your browser's local storage under ff-analytics-consent, which never leaves your device and is not readable by anyone else. If you accept analytics, Microsoft Clarity sets its own cookies; declining means it never runs, so it never does.

Server logs

Our web server records each request — time, page, IP address, user-agent — as most servers do. We use these to investigate faults and abuse. They rotate automatically and are deleted after 30 days.

The client portal

People can sign in at myaccount.frontforge.com to see invoices, payment status and tickets. Consulting clients are invited, and a link is sent to the email address on their billing record. Merchants using a Shopify app can sign in themselves — Google, Microsoft, or an email one-time code — through the same Microsoft Entra External ID tenant. We never see or store a password. The sign-in page runs the same Cloudflare Turnstile check as the public forms before Microsoft is asked anything.

If you do use it, more companies are involved, and only then:

  • Microsoft — provides the sign-in. Your email address and the fact that you signed in are handled by Microsoft Entra.
  • Stripe — holds the billing records a consulting client sees. We read invoices from Stripe when you open the page; we don't copy them anywhere. A Shopify merchant's tickets do not involve Stripe.

We link a portal account to a billing customer only when an invitation is opened — never by matching an email address on its own. A guest support message is attached later if you sign in with the same address you typed on the form.

Who else is involved

  • Amazon Web Services — hosts the server this site, the portal, your enquiry and your Community licence sign-up run on.
  • SMTP2GO — delivers the notification email when you send an enquiry, portal invitations, and Community licences.
  • Microsoft — provides Clarity analytics, and only ever sees anything if you accept it. Also provides sign-in for the client portal.
  • Cloudflare — the human check on the public forms, the Community licence form included. It is not analytics and is not optional on those forms: without it the queue would be anyone's.
  • Stripe — our payment provider, and only for clients who are billed. It is never involved in an enquiry from this website.

That's the complete list. No advertising networks, no data brokers, no analytics beyond the above.

How long we keep things

  • Enquiries — for up to 24 months after our last contact, so we can pick up a conversation where it left off. Ask us sooner and we'll delete them.
  • Community licence sign-ups — for as long as the licence exists, which is indefinitely, because it never expires; we keep it so we can send you the same licence again. Ask us and we'll delete it: the licence you already have keeps working, because it is checked on your server and never against our records. Product emails stop as soon as you ask.
  • Server logs — 30 days.
  • Your analytics choice — until you clear your browser storage.
  • Client portal accounts — while you are a client, and removed on request. Invoices themselves we have to keep for as long as tax law requires, which is longer. A record that a licence is on an account goes when either the account or the licence sign-up is deleted.

The database that holds enquiries, portal accounts and Community licence sign-ups is backed up every night, and each backup is kept for 30 days on a separate disk of the same server. When you ask us to delete something, it goes from the live database straight away, and from the backups as they age out, within 30 days; we don't restore a backup to bring back something you asked us to delete. Server logs and your analytics choice are not backed up. Our Shopify apps run on separate infrastructure and are backed up; the app privacy page says what that means for a deletion there.

Your choices

You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. We'll do that, and we won't make it difficult. The quickest route is the contact form — say what you'd like and we'll confirm once it's done. The same goes for stopping product emails about Frontforge Report Server.

To turn analytics off after previously accepting, use Cookie settings in the footer and choose Decline.

Changes to this page

If what we collect changes, we'll update this page and the date at the top. If the change is significant, we'll ask for your consent again rather than assuming it.

Getting in touch

Questions about any of this, or about how we handle data on a project, go through the contact form. Questions about a Shopify app go to support.

frontforge

Frontforge Report Server, and bespoke software for businesses that have outgrown off-the-shelf.

Report Server

  • Overview
  • Editions
  • Get started
  • Documentation
  • Releases

Company

  • Consulting
  • Shopify apps
  • Writing
  • Contact
  • MyAccount

Legal

  • Privacy
  • Community Licence
  • App terms
  • App privacy
  • DPA
  • App support

© 2026 Frontforge Pty Ltd. All rights reserved.