This Cookie Policy explains how Flitch Solutions Pty Ltd ABN 57 682 821 512 of 191 St Georges Terrace, Perth, WA 6000, Australia ("Flitch", "we", "us" or "our") uses cookies and similar technologies to recognise you when you visit our website at flitch.io or use our AI dashboard creation platform ("Services"). It explains what these technologies are and why we use them, as well as your rights to control our use of them.
1. What Are Cookies?
Cookies are small data files that are placed on your computer or mobile device when you visit a website. Cookies are widely used by website owners to make their websites work, or to work more efficiently, as well as to provide reporting information.
Cookies set by the website owner (in this case, Flitch) are called "first-party cookies". Cookies set by parties other than the website owner are called "third-party cookies". Third-party cookies enable third-party features or functionality to be provided on or through the website (e.g., payment processing, analytics, and authentication).
In addition to cookies, we may use similar technologies such as:
Local Storage: Data stored in your browser that persists until cleared, used for authentication tokens and user preferences.
Session Storage: Data stored temporarily for the duration of your browser session.
Web Beacons: Small graphics (also called "pixel tags") used to track user activity and email engagement.
2. Why Do We Use Cookies?
We use first-party and third-party cookies for several reasons. Some cookies are required for technical reasons for our Services to operate, and we refer to these as "essential" or "strictly necessary" cookies. Other cookies enable us to track and understand how users interact with our Services to improve functionality and user experience. Third parties serve cookies through our Services for payment processing, authentication, and analytics purposes.
3. Types of Cookies We Use
The specific types of first and third-party cookies served through our Services and the purposes they perform are described below:
Essential Cookies
These cookies are strictly necessary to provide you with services available through our Services and to use some of its features, such as access to secure areas and maintaining your logged-in session. Because these cookies are strictly necessary to deliver the Services, you cannot refuse them without impacting how our Services function.
Functional Cookies
These cookies are used to remember choices you make (such as your theme preference, language, or region) and provide enhanced, more tailored features. These cookies may also be used to remember changes you have made to configurable parts of the platform.
Performance and Analytics Cookies
These cookies and similar technologies (including browser local storage) collect information about how you use our Services, such as which pages you visit, which features you interact with, and where errors occur. We also use session replay tools that record your interactions on the page (clicks, scrolls, navigation) so we can diagnose issues. Sensitive content such as data tables, chat messages, connection details, and form inputs is masked before recording. The information is associated with your account once you sign in. For visitors in the EU, UK, EEA, and Switzerland, these cookies and recordings only run after you accept them via our cookie banner.
4. Specific Cookies and Technologies
Below is a list of the specific cookies and similar technologies we use:
Name
Type
Purpose
Duration
better-auth.session_token
Essential
Maintains your authenticated session
Session
theme
Functional
Stores your light/dark mode preference
1 year
sidebar-state
Functional
Remembers sidebar collapsed/expanded state
Persistent
flitch-region
Essential
Records whether you are in a region requiring cookie consent (EU, UK, EEA, Switzerland) so the banner is shown only where required
30 days
flitch-consent
Essential
Stores your cookie preferences (analytics and session replay choices) so we do not ask you again
12 months
ph_*
Analytics
PostHog identifiers used to attribute usage data and session replays to your account. Only set after analytics consent.
12 months
Local Storage
We use browser local storage for the following purposes:
Authentication tokens: Securely stored tokens that maintain your logged-in session.
User preferences: Your display preferences, such as theme settings and UI configuration.
Draft content: Temporary storage of unsaved work to prevent data loss.
PostHog state: Distinct ID, feature flags, and session metadata used by PostHog for analytics and session replay. Only set after analytics consent.
5. Third-Party Cookies
In addition to our own cookies, we use cookies and technologies from third-party service providers:
Stripe (Payment Processing)
Stripe uses cookies to process payments securely and prevent fraud. These cookies are essential for payment functionality. For more information, see Stripe's Privacy Policy.
Google (Authentication)
If you sign in using Google, Google may set cookies to facilitate the authentication process. For more information, see Google's Privacy Policy.
Microsoft (Authentication)
If you sign in using Microsoft, Microsoft may set cookies to facilitate the authentication process. For more information, see Microsoft's Privacy Statement.
PostHog (Analytics and Session Replay)
PostHog provides product analytics and session replay so we can understand how Flitch is used and diagnose issues. It sets first-party storage (under the ph_* prefix) and is loaded through a reverse proxy on our domain. Sensitive content is masked before recording. For visitors in the EU, UK, EEA, and Switzerland, PostHog only runs after you accept analytics in our cookie banner. For more information, see PostHog's Privacy Policy.
Sentry (Error Monitoring and Session Replay)
Sentry captures application errors so we can fix bugs, and optionally records short session replays around errors. Error monitoring runs always to keep the platform reliable. Session replay only runs in the EU, UK, EEA, and Switzerland after you accept it in our cookie banner; elsewhere it runs by default. Sensitive content is masked before recording. For more information, see Sentry's Privacy Policy.
6. How Can You Control Cookies?
You have the right to decide whether to accept or reject cookies. You can exercise your cookie preferences through the following methods:
Cookie Preferences on Flitch
Visitors located in the EU, UK, EEA, or Switzerland see a cookie banner on their first visit to app.flitch.io. From the banner you can accept all cookies, reject non-essential cookies, or open the Manage dialog to choose product analytics and session replay independently. You can change your choices at any time using the "Cookie preferences" link in the footer or the "Manage cookie preferences" button at the top of this page.
Browser Settings
You can set or amend your web browser controls to accept or refuse cookies. If you choose to reject cookies, you may still use our Services, though your access to some functionality may be restricted. The method for managing cookies varies by browser:
To clear local storage data, you can use your browser's developer tools or clear all site data through your browser settings. Note that clearing local storage may log you out of the Services and reset your preferences.
Important: Essential cookies cannot be disabled as they are necessary for the Services to function. If you disable essential cookies, you may not be able to use certain features of our Services.
7. Do Not Track Signals
Some browsers include a "Do Not Track" (DNT) feature that signals to websites that you do not want your online activity tracked. We currently do not respond to DNT signals, as there is no consistent industry standard for how to respond to such signals. However, you can manage your cookie preferences using the methods described in Section 6.
8. How Often Will We Update This Policy?
We may update this Cookie Policy from time to time in order to reflect, for example, changes to the cookies we use or for other operational, legal, or regulatory reasons. Please revisit this Cookie Policy regularly to stay informed about our use of cookies and related technologies.
The date at the top of this Cookie Policy indicates when it was last updated.
9. Contact Us
If you have any questions about our use of cookies or other technologies, please contact us at:
