What this policy covers
FCT Technologies LLC (“FCT”, “we”) builds this website and a portfolio of native apps that share one FCT account. This policy covers all three: fct-technologies.com, the FCT account, and every FCT app you sign into with it.
Each app also publishes its own privacy policy for what only that app does: the data it holds, the permissions it asks for, what runs on your device and never leaves it. Those sit under this one. Where both speak, both are true: the app’s policy describes that app, and this one describes the account and the systems every app shares.
This website
The site is a set of static files served by Cloudflare Pages. Cloudflare handles the requests it serves, as any host does.
Analytics. Public pages load Google Analytics 4 (gtag.js, measurement ID G-76CMSV079Z). It records page views and the standard signals a browser sends with them: the page URL, the referring page, your device, browser and language, and an approximate location derived from your IP address. It sets its own cookies. We read it to see which pages get used, and nothing else is done with it.
The pages that can carry a session or a credential in their URL load no analytics at all: the account door at fct-technologies.com/account/, every app’s feedback board, the password-reset landing, and the OAuth callback. Those pages ship the site’s design and none of its measurement, because analytics transmits the page URL.
Forms. The contact form asks for your email, your phone number, what you need, and a short description. Submitting it runs a Cloudflare Turnstile check (the widget loads from challenges.cloudflare.com when you reach the form) and delivers the message to us as email through Resend. Villain Arc’s bug and feature forms work the same way and add the app and iOS version you type in. None of it is written to a database: a form submission is an email, and your address is there so we can reply.
There is no advertising on this site, no cross-site tracking, and nothing is sold or handed to a data broker.
Your FCT account
One account signs you into every FCT app. It holds:
- Your email address, and a password if you created the account with one. The password is stored by our authentication service as a hash, never as readable text.
- Which sign-in methods are linked to the account: Sign in with Apple, Sign in with Google, or email and password. You can connect the others later, and the last remaining one cannot be disconnected.
- Your name and avatar, if you set them.
- Your birthday and your storefront country, set once when you first onboard. The birthday is what a feature with an age requirement is answered from, on the server rather than on your device. The country is the App Store storefront the account was created from, not where your phone is.
You can correct your birthday or your country up to twice a year each. We keep a record of that change (the previous value, the new one, the date and your stated reason) because an age answer needs a history behind it; the reason you type is stored and never repeated back anywhere.
Signing in with Apple or Google. We ask each provider for what identifies an account and nothing else: your email address, and your name on the first authorization. We request no other data from them, no access to any other Apple or Google service, and neither provider is told anything about what you do inside an app. Apple’s Hide My Email works normally: if you use it, the relay address is the address on the account.
The account system sends exactly one kind of email: a password reset, when you ask for one. Signing up sends no confirmation mail.
Your session lives in one keychain item on the device, readable by the FCT apps you have installed. It is marked as never leaving that device and is never synced through iCloud.
App data in your account
An FCT app keeps a local store on your device and syncs it to your own space in the database we operate. That server copy is the canonical one: it is what makes an app arrive whole on your next device and what a reinstall restores from. Access is enforced per account inside the database itself, so no app and no account can read another account’s rows.
Files you author inside an app (an image, a recording, an attachment) are stored as objects on Cloudflare R2, under a key prefixed with your account, reachable only through a single-use authorization the server mints for you.
We do not sell your data, do not share it with advertisers, and do not use your content to train models. The one exception is something you turn on yourself, described under Diagnostics.
Signing out clears that app’s copy from that device only after the app has proven everything it holds reached the server. A sync that did not finish refuses the sign-out rather than clearing on top of unsaved work.
Erasing is two clearly separate options in any FCT app’s Settings:
- Delete this app’s data removes everything that one app holds, on our servers and on your devices, and leaves your account and the other FCT apps standing.
- Delete your account removes the account and everything under it: your rows in every app, your files in the object store, your feedback posts and votes, and the authentication record itself. It is a deletion, not a deactivation, and a device that was offline when it happened wipes and signs out when it comes back rather than restoring what you deleted.
Diagnostics
Every FCT app reports diagnostics to us, and the reason we can state the privacy of that plainly is that it rests on what the system is unable to collect rather than on a promise.
What is collected: crash and hang reports with a short trail of the screen and action names leading up to them, performance metrics from Apple’s MetricKit (launch time, hang rate, memory, disk writes, network volume, battery), onboarding and sign-in funnels with how long each step took, counts per named feature, and context for reading any of it (app version and build, OS version, device model class, locale).
Screen and action names are fixed values compiled into the app, so nothing you type, view or store can appear in one.
What cannot be collected: your account, any of your content, free text of any kind, the contents of a text field, precise location, contact information, or anything that joins to a row in your account.
No account, by construction. A diagnostics upload carries no account token at all. Instead of saying who you are, the device proves with Apple’s App Attest that it is running a genuine build of one of our apps. Rows key on a random install identifier the app mints at first launch and stores in its own storage, so reinstalling starts a new one. No column, key or grant in the diagnostics schema reaches an account, which is why deleting your account leaves diagnostics untouched: there is nothing in them to find.
Clocks are coarsened on arrival, to the hour for anything a device’s own action timed and to the day for our own receipt clock, because a timestamp precise enough to be unique is a join key even with no identifier attached to it.
Retention: 180 days for metrics, funnels and counters, 400 days for crash diagnostics, enforced by a daily job. Because nothing marks which rows are yours, none can be singled out for deletion, not by us and not on request. They expire on that schedule instead.
Diagnostics exist to find and fix crashes and to improve the apps. They are never sold. No FCT app contains a third-party analytics or crash-reporting SDK.
Improving an on-device suggestion engine happens on three tiers, and the tier decides the shape:
- Structure, always. Which engine made a suggestion, which version of it, which part of it ranked the suggestion, the position it appeared at, what became of it, and roughly how long that took. Never a title, a weight, a set, or an identifier of any kind.
- Content, only in aggregate. A count across installs is reportable only once at least 25 distinct installs stand behind it, and is not reported below that floor in any form.
- Anything richer, only donated. Detailed histories of the kind that would train a model leave your phone only after you tap help improve the engine, knowing what goes. It is one tap in onboarding, off until you tap it, and you can turn it back off.
Personalization itself runs on your device, computed from your own data, which never leaves for that purpose.
The feedback board
Each app has one feedback board: signed-in people using that app post suggestions and upvote each other’s.
The board shows no author. Not a name, not an avatar, not an anonymised handle. The server keeps the account on each suggestion and each vote so that your erase and your own withdraw can find them, and no client role can read that column: not the app, not this website. What a client can learn about ownership is two facts about your own account, whether a post is yours and whether you voted.
The residual is worth stating plainly: you can type your own name into a title. We do not scan free text for identity, so keep personal information out of a post.
A title and body cannot be edited once posted; withdrawing and posting again is the edit, and withdrawing takes every vote on that suggestion with it. We set each suggestion’s status (open, planned, shipped, declined) and can hide a post, which removes it from every path a client has while leaving its author able to withdraw it. Nothing on a board is public: there is no board without a sign-in. There are daily limits, currently 5 suggestions and 50 votes.
What we never do
- Sell, rent or trade your data, to anyone, for anything.
- Run advertising, ad identifiers, or behavioural profiling.
- Ship a third-party analytics or crash SDK inside an app.
- Track you across apps, across companies, or across the web.
- Hand your data to another company for its own purposes. The providers listed below process it to run the service and for nothing else.
One thing we will not claim: your app data sits in a database we operate, so we hold it in custody. Access is enforced per account and we do not mine it, but an app that stores your data on our servers is a company you are trusting, and we would rather say so than imply an end-to-end encryption we have not built.
Your rights
Wherever you live, these are available to you. If you are in the EU, the UK, California or another place with its own data law, this is how those rights are exercised here.
- Access. Sign in at fct-technologies.com/account/ and Export your data downloads a machine-readable JSON file, free and immediately: your account profile, your birthday and country with every recorded change to them, your subscriptions, and every row every FCT app has synced for you, plus a list of the files you have uploaded by name, size and type. Two things are not in it, and email is how you get them: your feedback-board posts and votes, and the record of which sign-in methods are linked to the account. Email [email protected] from the address on the account for those, if you cannot sign in, or if the account holds more than the automatic export can send in one file — within 30 days we send you a copy of everything, free.
- Correction. Your name and avatar are editable in the app. Your birthday and country go through the recorded change described above.
- Deletion. Both doors are in every FCT app’s Settings, and either one is a real erase rather than a flag. If you would rather ask us, email the address below from the address on the account.
- The web door. fct-technologies.com/account/ signs a browser into the same account, shows the address on it, and exports your data. Deleting is done from an app, where the data lives.
- Signed in with Apple? Deleting your FCT account does not remove Apple’s own authorization for the app. Remove that yourself in Settings → your name → Sign-In & Security → Sign in with Apple, per Apple’s instructions.
- Complaints. If you are in the EU or the UK, you can complain to your supervisory authority. We would rather you write to us first.
Why we are allowed to hold any of it, in one line: your account and app data because it is what running the service you asked for takes, diagnostics because keeping the apps working and safe is a legitimate interest of ours that identifies nobody, and the donated tier only with your consent, which you can withdraw.
Children
FCT accounts are not for children. You must be at least 13 to create one, and where your country sets a higher age of digital consent, that age applies instead.
Onboarding asks for your birthday, and any feature with an age requirement is answered from it on the server. That check is deliberately conservative: it compares against the earliest calendar date anywhere on Earth, so it turns true only once it is true in every timezone, and a gate that cannot know the answer says no.
We do not knowingly collect information from a child under 13. If you believe a child has created an account, write to the address below and we will delete it.
Security, and where your data lives
Every account’s rows are isolated from every other account’s in the database itself, nothing is public, nothing is reachable by following a link, and every server door is authenticated and rate-limited. On your device, the session is one keychain item marked as never leaving that device.
We rely on a small number of providers to run it: Supabase (the Postgres database, authentication, and the server functions that erase an account), Cloudflare (Pages hosting, R2 object storage, Turnstile), Resend (delivering form email), and Google Analytics on the public pages of this site. FCT Technologies LLC is based in the United States, so your information may be processed there or wherever those providers operate.
If a breach happens. Where a personal-data breach is likely to result in a risk to your rights and freedoms, we notify the relevant supervisory authority within 72 hours of becoming aware of it. Where the risk to you is high, we notify you without undue delay, with what happened, what data was involved, what we are doing, and what you can do. We keep a record of every breach and its handling whether or not it is notifiable. We hold the whole portfolio to that single deadline because it is the strictest one that applies to us.
Changes to this policy
When what we do changes, this page changes with it and the effective date at the top moves. Where a change materially widens what we collect or narrows what you can do about it, we will say what changed at the top of this page rather than quietly re-dating it.
Contact
Privacy questions, access and deletion requests, and anything else about this policy:
FCT Technologies LLC, an Illinois limited liability company
[email protected]
For help with a specific app, [email protected] reaches the same person and we respond within 5 business days.