fak10
Privacy in the app
What you tell Anna stays on your device. There is no account and no advertising. Something leaves your device only when you trigger it: when a big AI reads a document or a chat text for you, when you send feedback or use credits. Anonymous usage signals go out only if you agree.
Controller
Maciek Niemczyk · Macilias
c/o IP-Management #12114
Ludwig-Erhard-Str. 18
20459 Hamburg, Germany
Email: info@fak10.app
What stays on your device
The app stores people, statements, goals, needs, documents and the conversation only on your device; text you send to the big AI goes out as described below. I have no access to them. Anna understands your sentences on the device itself, offline. You can view and delete everything in the app. If you delete the app, this knowledge is gone; what lies on my server is covered below under feedback and credits.
Encrypted. The app stores your knowledge encrypted (AES-256) and requires Face ID or your device passcode to open it. By default it locks after 5 minutes in the background; you can change that. The key is held by your device's keychain, nobody else, not even me.
To a new device. During setup you choose a passphrase. With it you can export your knowledge, including filed originals, in encrypted form and import it again. If you forget it, your knowledge stays accessible on the old device, but the export can no longer be opened. Nobody can recover it, not even me.
Filed documents. The originals stay in the app. iOS keeps them encrypted with its file protection; while your device is locked, not even the app can read them. In the settings you see each file with its size and can delete it on its own. What Anna learned from it is deleted separately. If your device's iCloud backup is on, the originals and your encrypted store are included; that is governed by your agreement with Apple. On a new device, only your passphrase opens the store from that backup.
Forms in the browser
With the Safari extension, fak10 fills in forms from your knowledge. No AI is involved: the fields go to the app on your device, and after you confirm, the values go only to the page you have open. You can attach a filed document, such as a receipt, the same way. The app holds it ready for at most 10 minutes. What that page does with it is up to its operator.
Big AI (optional)
You can have a big AI read a document or a text in the chat. This happens only when you start it. Before that, the app shows you what goes out and what it costs, and you confirm. The same applies to a web page or PDF you share from Safari to fak10. In the chat this happens with each reservation of credit (see below).
- What goes out: the content of the document (text, for PDFs the file), its file name and instructions for how the AI should write down facts. The instructions contain the language and the names of classes, relations and categories, including ones you created or adopted yourself. If you named one after a person, that name goes along. The preview shows you the full instructions. Terms you marked as secret yourself do not go along. Fixed app terms such as the name of the IBAN field do go along, but not their values from your memory.
- In the chat with “You → AI”: If you switch the input field to “AI”, everything you write goes to the big AI, including questions, to the same provider and in the same regions as a document, even if you type something secret. A fixed instruction goes along too; it contains no data of yours. The date and time of your device go along with your texts, so that the AI can place words like “tomorrow” or “from Monday”. The AI knows the context of the last 20 minutes: each message also carries your earlier texts from that time. If the history gets very long, the oldest lines do not go along, and the chat tells you so. What goes to the AI is visible as your line in the chat; there is no separate preview for it. The first time you switch on AI mode, the app asks once for your permission. Credit is reserved without a further dialog for up to 20 minutes and a fixed number of texts, shorter with less credit; the display in the chat shows credit and remaining time. Once the reservation is used up, credit is reserved again and the history so far keeps going along. What was in the chat before you switched to “AI” does not go along unless you copy it in yourself. No stored facts or people from your memory go along. Of the terms, only the app's fixed ones go along, such as person, city or “has parent”, never your names or content and never terms you marked as secret. If the AI cannot answer a question because it refers to something outside this conversation, it passes the question on to Anna, and Anna answers it on the device. Anna's answers and her other lines go to you and not to the AI, not in the history either, unless you copy them into your text yourself. If you answer one of Anna's follow-up questions, that answer goes to Anna and not to the AI. The AI's answer appears in the chat and goes back to the AI as history during the window. What the AI passes on to Anna and what Anna answers stays with Anna. The app stores the history permanently on your device only. To make answers faster and cheaper, the provider keeps the app's fixed instructions in a cache for up to 1 hour; your text and the history are not part of it. No text goes to my credit server.
- What does not go out: the rest of your knowledge: no entries about people, no statements, no facts from your memory, except what you yourself wrote since switching to “AI”.
- Provider: Amazon Web Services (Amazon Bedrock) with the Claude model by Anthropic. The app calls Bedrock directly; your content does not pass through any server of mine. AWS processes it on my behalf (Art. 28 GDPR). AWS does not use the content for training and does not pass it to Anthropic. AWS may retain content for abuse detection. Images are checked automatically for child sexual abuse material, and AWS may store, review and report matches. My own log of calls contains no text or images.
- Where: In the TestFlight beta, the AI runs through data centres in the EU for all testers.
- The app stores the answer as suggestions you review. Nothing is adopted without asking.
- If a document or text contains health data or other specially protected details, you decide yourself whether to send it.
- Legal basis: your consent by confirming (Art. 6(1)(a) GDPR, for special categories Art. 9(2)(a)). You withdraw it for the future by no longer using the feature.
Feedback
You can send me feedback from the app. It goes out only when you tap send, to my server at AWS in the Stockholm region: your text, the type (bug, wish, other), the level, proof from Apple that it comes from the real app, and an identifier of your installation in hashed form. That is what links your feedback entries. Your name or address are not included.
- Secret is the default. The text is stored encrypted. The team and I read it to classify the entry; it never appears publicly, in a ticket or on a board.
- Public: after our review the text can appear publicly.
- fak10.app/testflight lists every entry with number, type, level, status and date, including secret ones, but without their text. The page shows text only for public entries after review. Please do not name other people.
- Recipients: The team consists of AI sessions using Claude by Anthropic (USA). Entries go to Anthropic in the clear for this, secret ones included.
- Deleting: You delete entries yourself under "My feedback". After reinstalling, that no longer works in the app; email info@fak10.app with the date and text. There is no fixed period yet; they stay until deleted.
- Legal basis: your consent by sending (Art. 6(1)(a) GDPR).
Anonymous usage signals
It is like a railway: I check whether the train runs and where it jolts, not who is on board or where they are going. On first launch the app asks whether it may send signals. If you say no, or nothing yet, it collects at most 200 signals on your device only and does not send them. If you say yes, those collected so far go along. In the settings you see what is waiting, change your choice, send once or delete everything.
What is sent: that the app started and how long that took, which area was opened, whether a sentence was understood, that a document was read or failed and how many facts came out; plus app version, iOS major version and language. Never content: no sentences, names, documents or facts.
The signals carry no persistent identifier, only a random number per app start. It stays on the device with the waiting signals until they are sent. So I see how often something happens, not who it was. The recipient is TelemetryDeck (TelemetryDeck GmbH, Von-der-Tann-Str. 54, 86159 Augsburg, Germany; stored in the EU). In the current beta this is not connected yet: the app asks and collects, but sends no signals. Legal basis: your consent (Art. 6(1)(a) GDPR), which you withdraw at any time in the settings.
Credits and purchases
Having the big AI read something costs credits. You get starter credits and can buy more in the app; Apple handles payment and I receive no payment data. In the beta, purchases are Apple test purchases and no money changes hands.
So that your balance is right, my credit server (AWS, Stockholm) stores, without an account: a pseudonymous identifier assigned by Apple, your balance with a booking journal, Apple's purchase receipts and proof from Apple that the request comes from the real app (App Attest). The identifier is the one for your purchases in fak10; in the beta it may instead be the device identifier Apple issues to vendors. It does not tell me who you are.
The server checks only origin and balance and gives the app a short-lived permission for the call. For that it learns the size and type of the document and the country of your App Store account, never the content. If actual usage clearly differs from the reported size, it notes this on the identifier until the difference is made up. For each call AWS logs only metadata: a hashed form of the identifier, time, model and token counts, never text or images.
Legal basis: Art. 6(1)(b) GDPR, for the booking journal and receipts also (c) (retention duty), for the call log (f) (billing and abuse prevention).
How long I keep this:
- Booking journal and receipts: 8 years from the end of the calendar year of the booking (§ 257 HGB, § 147 AO).
- Log of AI calls: 90 days.
- Technical operating logs: 14 days.
- Your balance stays as long as fak10 exists; purchased credits do not expire.
- Your device's App Attest key: 13 months after last use.
- Deleted entries remain in the server backup for up to 35 days.
- Server administration log (no user data): 1 year.
What I don't do
- No account, no sign-in.
- No ads, no tracking across apps and websites, no profiles.
- No push notifications, no location.
- I never sell data.
If you tap an address, link or phone number, iOS opens it in the matching app; an address then goes to Apple Maps.
Data provided by Apple
- Crash reports: If "Share with App Developers" is on in iOS settings, Apple gives me anonymised reports.
- TestFlight: If you join the beta, I see what Apple provides, such as your device and iOS version, with an invitation your name and email address, plus feedback sent through TestFlight. I use this only to improve fak10 and delete it after the beta (Art. 6(1)(b) and (f) GDPR).
- App Store statistics: aggregated numbers, no data about you.
Age
fak10 is meant for people aged 16 and over.
Contact by email
If you write to info@fak10.app, I process your address and message to reply (Art. 6(1)(b) or (f) GDPR). If a purchase was not credited, the app can prepare an email with the error code and transaction ID; it is sent only when you tap Send in your mail app.
Your rights
Access, rectification, erasure, restriction, objection and portability (Art. 15–21 GDPR); withdrawing consent for the future (Art. 7(3) GDPR); complaint to a supervisory authority, for example the Hamburg Commissioner for Data Protection and Freedom of Information, datenschutz-hamburg.de. Since the app's content lives only on your device, you exercise most rights there; otherwise email info@fak10.app.
Changes
If what the app processes changes, I update this policy and say so in the release notes.