What we collect, and what we don’t.

Last updated 31 October 2026

Flincth is made by one small team, and this page is written to be read rather than skimmed past. It covers each Flincth app separately, then this website: Flincth Workspace Manager for Mac, Flincth Split View for Chrome, Firefox and Edge, Flincth Speed Reader for iPhone and iPad, and this website.

Flincth Workspace Manager (Mac)

Flincth Workspace Manager has no account system, no analytics and no server of its own. It never sends your setups, your window layouts, your clipboard history or any usage data anywhere.

Your setups and your clipboard history are stored locally on your Mac. Deleting the app removes them along with it. Nobody at Flincth can see them, recover them, or hand them to anyone else, because they never leave your machine.

New-feature announcements, only if you turn them on. This is the app’s only use of the network, and it is off until you switch it on in Settings. When it is on, your Mac’s push notification identifier and whether announcements are on are sent to OneSignal, the service that delivers them, over an encrypted connection. OneSignal also sees your IP address when the app connects. Nothing else is sent: no setups, no clipboard content, no name or email address, no location and no usage data. Turning announcements off tells OneSignal to stop; if you are offline at that moment, the app finishes unsubscribing the next time it can connect. See OneSignal’s privacy policy.

Flincth Split View (browser extension)

Flincth Split View, the Flincth browser extension, does not collect, transmit, sell or share any data. It contains no servers, no analytics, no telemetry and no crash reporting, and it makes no network requests of its own.

Your workspaces are stored in your browser’s local extension storage on your own device, together with your extension settings. That covers their names, how each one divides the tab, and the web addresses you assign to its panes. Removing the extension removes them.

Installing the extension gives it access to no website. In Chrome and Microsoft Edge (version 1.0.2 and later), it then offers optional access to all HTTP(S) websites. You can skip this and continue organizing workspaces; activating a site asks for access again if it is missing, and without consent sites stay inactive. In Chrome and Edge that access is used only inside the extension’s own tab, to remove framing response headers and set the navigation destination header to document so websites can display in panes. In Firefox, the extension asks for access one site at a time, when you put that site in a pane; Firefox does not let extensions change framing headers, so a site that refuses to be embedded opens in its own window instead. In every browser, the extension never reads cookies, page content or form data. Bundled navigation code runs only in permitted Flincth panels to track their current addresses and support Back and Forward. The latest address is saved locally so reopening a workspace restores that destination. Site access can be revoked through your browser’s extension settings.

Address fields accept URLs or search text. Search text goes through the browser search API and its current default provider, using an inactive temporary tab to resolve the URL before loading it in the pane. The temporary tab is closed on success, failure or timeout. Queries are sent to the chosen search provider by the browser; Flincth does not collect them or select a provider.

Flincth Speed Reader (iPhone and iPad)

Flincth Speed Reader is not out yet. This section describes the app as it will ship, and will be updated before launch if anything changes.

The app has no account system and no server of its own. The documents you import, their text, titles and file names, and anything you paste stay on your iPhone or iPad. If you turn on iCloud sync (a Pro feature), your library, reading positions, settings and statistics are also stored in your own private iCloud account, which Apple runs and which Flincth cannot read.

Usage statistics. To learn which parts of the app work, it counts events such as a finished reading session or a failed import, using Google Analytics for Firebase. Events include reading and app interactions, trial and purchase activity, and categories of import failures. Their parameters contain only categories and numbers (for example the file format, a speed range or a session length range), never document content, titles, file names, web addresses or pasted text. Events are associated with an app-installation identifier, so repeated activity can be connected to the same installation. Google Analytics can derive approximate location from the IP address used to connect; this is not GPS location. We do not send a name, email address, phone number or account ID to Analytics. There is no advertising identifier and no tracking across apps. In the EU, the UK and Switzerland this stays off unless you agree on a first-run screen; elsewhere the app tells you on first run and you can turn it off in Settings → Privacy.

Remote settings. The app fetches a small set of settings, such as the free plan’s limits, from Firebase Remote Config. Requests use a Firebase installation identifier and include technical information such as country, language, time zone, OS version and app version, as well as the IP address used to connect. This lets Firebase return configuration values and maintain the service; it includes nothing about what you read. Remote Config operates separately from the usage-statistics switch.

News and offers, only if you turn them on. Off by default. When on, your device’s APNs push token and subscription status are registered with OneSignal to deliver feature announcements and promotions. OneSignal assigns a subscription identifier and sees your IP address when the app connects. These identifiers relate to your installation; no name, email address, phone number or document content is sent. You can turn News and offers off in the app’s notification settings. Reading reminders are created on the device and need no network.

Purchases go through Apple’s App Store. Flincth never sees your payment details. When usage statistics are enabled, the app also reports purchase, trial and restore events to Analytics using categorical parameters and its app-installation identifier.

This website

The website is a set of static files. You can browse without an account.

A few things still happen when you visit, and you should know about each of them.

• Hosting. The site is served by GitHub Pages. Like any web server, GitHub receives your IP address and browser user agent in order to send you the page. This is handled under GitHub’s privacy statement, and we neither see nor keep those logs.
• Analytics. We count visits with Google Analytics, using Google’s consent mode. In the EU, the UK, Switzerland and Türkiye, no analytics cookie is stored unless you press Accept on the cookie banner. Until then, or if you decline, Google receives only cookieless pings: that a page was viewed, with no cookie and no identifier that could recognize you on your next visit. Google uses them to estimate how many visits went unmeasured. Everywhere else, Google Analytics stores its cookie unless you press Decline, after which it sends only those cookieless pings. Which rule applies is worked out from your device’s time zone, in your browser.
• Notifications, only if you ask for them. The “Notify me at launch” buttons and the Notifications link in the footer let you opt into browser push. Your browser asks for permission when you choose to subscribe. A button on a product’s page also stores a tag naming that product (for example launch_speed-reader) with your subscription, so a launch notification reaches only the people who asked about that product. Once you are subscribed, OneSignal holds a browser push token and an anonymous subscription id for you, so that a notification can reach this browser. There is no name, no email address, and no way for us to tell who you are. Pressing the same button or link again unsubscribes, and your browser’s own site settings can revoke the permission outright. See OneSignal’s privacy policy.
• Your cookie choice. Whichever you pick is remembered in your browser’s local storage under the key flincth-analytics-consent. It stays on your device and is never sent anywhere.

To change your mind either way, use the Cookies link at the bottom of any page. Clearing your browser’s site data for flincth.com also erases the choice, and you will be asked again on your next visit.

What Google Analytics sees

With its cookie, it records the pages you view, roughly where in the world you are, and what kind of device and browser you use, and it can tell a returning browser from a new one. Without the cookie it sees the same page view but cannot connect it to any other visit. Google shortens IP addresses before storing them, and this is not something we can switch off or configure. We use the data to count visits. Google signals and every advertising feature are switched off. We do not run advertising, we do not build profiles, and we do not sell or share this data with anyone else.

Your rights

If you are in the EU, the UK, or Türkiye, you have the right to ask what personal data is held about you, to ask for it to be corrected or deleted, and to withdraw consent at any time. Withdrawing consent for analytics takes one click on the Cookies link.

Because the Flincth apps hold nothing about you beyond what is described above, and neither does the website, most requests are answered quickly and with very little to report. Write to us and we will tell you exactly what exists.

Changes

If this policy changes in a way that affects you, the date at the top changes with it. We will not quietly start collecting something new under an old date.

Contact

Questions about anything on this page: support@flincth.com.