§1Who is responsible
The controller of your personal data is:
Oleksandr Pokariev, a private individual resident in Poland, Kwiatowa 6, 05-205 Ostrówek, Poland. Contact: alex@acebox.eu.
Contact for anything in this policy: alex@acebox.eu
We have not appointed a Data Protection Officer; we are not required to. Write to the address above and a human answers.
§2What Pocket frAIday is, in data terms
Pocket frAIday is a personal AI assistant. Each account gets its own isolated assistant instance running in its own container on our servers, with its own storage. The assistant is not a chatbot in front of a shared database: your conversations, its memory of you, the documents it writes for you and its browser profile all live in storage that belongs to your account alone.
Three consequences worth stating plainly, because they are unusual:
- The assistant remembers you on purpose. Its usefulness is its memory. That memory is personal data and it is kept for as long as your account exists.
- The assistant can act in the world on your behalf — browse the web while logged into your own accounts, read the mail you forward to it, write to your calendar, call your phone. Everything it touches while doing that passes through our systems.
- We do not train models on your data. Not our own models, and we do not grant anyone else the right to. Your conversations are used to serve you and for nothing else.
§3What we collect
3.1Data you give us
| What | Where it comes from |
|---|---|
| Email address, password (stored only as a bcrypt hash), name | Registration |
| Apple account identifier and, if you allow it, name and email (possibly an Apple private relay address) | Sign in with Apple |
| Assistant setup: archetype, tone, assistant name, your stated wish, timezone, language | Setup wizard and settings |
| Free-text instructions to the assistant ("persona override") | Settings |
| Telegram chat identifier and chat title | When you link Telegram |
| Age confirmation, with the date, IP address and browser user-agent at the moment you confirmed | Only if you enable the adult mode |
3.2Data produced by using the service
| What | Detail |
|---|---|
| Conversations | Every message between you and the assistant, in every channel (web, app, Telegram), plus the channel and mode each was sent in |
| Voice notes and media | Audio, photos, video, stickers and files you send; audio is transcribed to text by a speech-to-text model running on our own hardware |
| Documents | What the assistant writes and files on your desk |
| Calendar | A mirror of the events it syncs with your device calendar: titles, notes, locations, times |
| Location | If you switch it on in the companion app: a trail of coordinates with accuracy, altitude, speed, heading and battery level, collected in the background |
| Devices | Phone model, OS and app version, locale, timezone, push tokens, which permissions you granted |
| Calls | Metadata of voice calls with the assistant — direction, times, outcome, and the reason it called. We do not record or store call audio. |
| Notifications | A log of pushes sent to your phone and their payload |
| Browser profile | If you use the built-in browser: one persistent profile per account — cookies, history, local storage and the sessions you are logged into. This is what makes it useful and it is also the most sensitive thing we hold |
| If you connect forwarding, the messages forwarded to the assistant's mailbox, including their senders — who are third parties who did not agree to anything with us | |
| Billing | Plan, subscription status, trial dates, and the identifiers our payment provider gives us. Card numbers never reach our servers |
| Technical logs | Requests to our servers with IP address, timestamp and user-agent; application and container logs |
3.3Sensitive data, and the adult mode
An assistant you talk to every day will hear things that fall under Article 9 of the GDPR — health, beliefs, sex life. We do not seek that data and we have no feature that acts on it, but we cannot pretend it does not arrive.
The adult ("Romance") mode is different in kind: enabling it means you are choosing to have sexual conversations with the assistant and to have them stored. That is special-category data by definition, and we process it only on your explicit consent, given at the moment you open the gate, together with your confirmation that you are 18 or older. Both facts are recorded with a timestamp and IP address. Turn the mode off and the processing stops immediately; the conversation history remains until you delete it or your account.
The adult mode does not exist in the mobile app, in any form.
§4Why we process it, and on what legal basis
We do not use your data for advertising, we do not sell it, and we do not profile you to make decisions about you. The assistant acts on what you ask it to do; it does not make automated decisions with legal effect on you within the meaning of Art. 22.
| Purpose | Legal basis (GDPR Art. 6) |
|---|---|
| Creating and running your account and your assistant, holding its memory, delivering messages, documents, calendar and calls | Performance of a contract — Art. 6(1)(b) |
| Sending what you give the assistant — messages, voice, photos and files, and location only if you share it — to the AI providers named in §5, so it can understand and answer you | Performance of a contract — Art. 6(1)(b); in the mobile app also your explicit consent — Art. 6(1)(a), asked once before the assistant first hears from you and recorded with its date |
| Background location, so the assistant knows where you are | Your consent — Art. 6(1)(a); withdraw it in the app at any time |
| Reading mail you forward to the assistant | Your consent — Art. 6(1)(a); stop forwarding and it stops |
| Using the built-in browser on your behalf, including while logged into your accounts | Performance of a contract — Art. 6(1)(b), on your instruction each time |
| Adult mode: content and the age record | Explicit consent — Art. 9(2)(a) together with Art. 6(1)(a); the record itself is also kept under Art. 6(1)(f) to be able to show the gate worked |
| Security, abuse prevention, keeping the service standing | Legitimate interest — Art. 6(1)(f) |
| Invoicing, tax and accounting records | Legal obligation — Art. 6(1)(c) |
| Answering your support requests | Art. 6(1)(b) and (f) |
§5Who else sees it
We use a small number of providers. Each gets the minimum needed to do its job.
The assistant's thinking is done by AI models, and most of them are run by the companies named below rather than by us. To answer a request, the content that request needs goes to the model answering it: your messages, voice once it is turned into text, photos and files you send, what the assistant remembers about you when the reply needs it, and your location only if you have chosen to share it. Speech recognition in the app runs on our own hardware; on AI phone calls ElevenLabs does it. In the mobile app, before the assistant first hears from you, the app names these providers and asks for your consent, and nothing you say there is sent to them until you agree.
- We and our servers are both in the European Union, so most of your data never leaves it. Where a provider is outside the European Economic Area — chiefly in the United States — the transfer rests on the European Commission's Standard Contractual Clauses or on an adequacy decision. Write to us and we will tell you which applies to which provider.
- Notifications the assistant sends to your phone can contain the substance of what it wants to tell you, and a push passes through Apple or Google to get there. Keep notification previews off your lock screen if that matters to you.
- Beyond this list, we disclose data only when the law compels us, and only what is compelled.
| Provider | What for | What reaches them | Where |
|---|---|---|---|
| Hetzner Online GmbH | Servers, storage, backups | Everything the service stores | Nuremberg, Germany (EU) |
| Cloudflare, Inc. | Secure tunnel in front of the website | Traffic to and from the website (encrypted in transit) | EU / United States — standard contractual clauses (SCC) |
| MiniMax | The primary language and vision model: the assistant's replies, and reading the photos and files you send | The content of that particular request — your messages, the photos or files in it, and what the assistant remembers about you when the reply needs it | Outside the European Economic Area — see MiniMax's own privacy policy |
| Google (Gemini via our gateway) | Fallback chat and vision models when MiniMax is unavailable | The content of that particular request | United States / EU |
| Anthropic (Claude via our gateway) | Fallback chat model when the ones above are unavailable | The content of that particular request | United States — standard contractual clauses (SCC) |
| Ollama (ollama.com) | Hosting of open models (such as DeepSeek) used as a further fallback for chat, vision and memory search | The content of that particular request | United States |
| Our own dedicated hardware (EU) | Speech-to-text for voice notes and for your voice in the app's calls, memory search, and local fallback language and vision models | Your recorded speech, and conversation content sent for a reply | European Union |
| Stripe Payments Europe, Ltd. | Processing subscription payments | Your email, billing country and payment details — card data goes to Stripe and never reaches us | Ireland (EU) |
| ElevenLabs | The assistant's voice — in the app's calls, the voice onboarding and "listen" under a message — and AI phone calls (reminders, bookings), if you use them | The text the assistant speaks; on phone calls, the call audio, the phone number called and the instructions for that call | EU / United States — standard contractual clauses (SCC) |
| Twilio | The telephone network for AI phone calls, if you use them | The call audio and the phone number called | EU / United States — standard contractual clauses (SCC) |
| OpenStreetMap Nominatim and TimeAPI (timeapi.io) | Working out your time zone from a city you name during setup | The city name (Nominatim), then its coordinates (TimeAPI) — not who you are | Outside the EU — see each service's own privacy policy |
| Apple Inc. | Push notifications, VoIP ringing, Sign in with Apple | Device push tokens, notification titles and bodies, your Apple identifier | United States / EU |
| Google LLC (Firebase Cloud Messaging) | Push notifications on Android | Device push tokens, notification titles and bodies | United States / EU |
| Telegram | The Telegram channel, if you use it | Your messages in that channel and your Telegram chat id | Outside the EU — see Telegram's own privacy policy |
| LiveKit | Carrying voice calls | Live audio while a call is active; never stored on our servers | European Union / US |
| SMTP Email Provider | Verification, password resets, system notices | Your email address and the notification message | European Union |
§6How long we keep it
Nothing is kept "just in case". These are the actual retention periods:
| Data | Retention period |
|---|---|
| Account, settings, assistant memory, documents | While your account exists |
| Conversations and transcripts | While your account exists — this is the assistant's memory of you |
| Media files (voice notes, photos, video, sent documents) | 6 months from sending, then the file is deleted; the message and any transcript remain |
| Location trail | 90 days, rolling; your latest position is overwritten rather than accumulated |
| Calendar mirror | While your account exists; events more than 12 months past are removed |
| Call metadata | 12 months (there is no call audio to keep) |
| Notification log | 90 days |
| Browser profile: cookies, history, sessions | While your account exists, or until you clear it |
| Forwarded mail | While your account exists; you can ask the assistant to delete any of it |
| Session and refresh tokens | Until they expire or are revoked, then purged within 30 days |
| Password-reset and email-verification links | Until used or expired, then purged within 7 days |
| Age confirmation for the adult mode | While your account exists, and 3 years after it is deleted, reduced to the bare record: account identifier, timestamp, and IP address. |
| Invoices and accounting records | 5 years from the end of the tax year, as Polish accounting law requires. These survive account deletion |
| Server and application logs | 30 days |
| Backups | Rolling 30 days; deleted data disappears from backups within that window |
| Record that an account was deleted | 3 years, in minimal form (email hash), to prove erasure and prevent invite abuse |
§7Deleting your account
You can delete your account yourself: Settings → Danger Zone → Delete account on the web, or Settings → Account → Delete account in the app.
What happens the moment you ask:
Then a 14-day grace window runs, during which you can still write to us or click Cancel Deletion on the portal and have the account restored. We give you those two weeks on purpose: an account deleted in an angry hour is one of the few mistakes here that cannot be undone.
When the window closes, deletion is irreversible. We destroy your assistant's container and its entire storage — its memory of you, its desk, the browser profile and every session in it, all media files — and erase your rows from our database. What is left afterwards is only what §6 says survives: accounting records for 5 years, the age-confirmation record for 3 years if you ever enabled the adult mode, and a minimal note that an account with your email hash was deleted on that date.
Data already sent to a model provider to answer a request in the past cannot be recalled from them; what they retain is governed by their own terms, and none of them is permitted to train on it.
- You are signed out everywhere immediately and cannot sign back in;
- Your assistant instance is stopped — it stops writing, calling and notifying;
- Telegram is unlinked, push tokens are revoked, mail forwarding is switched off;
- Any active subscription is cancelled and not renewed.
§8Your rights
Under the GDPR and UK Data Protection Act you have the right to:
- Know what we hold and get a copy of it (Art. 15);
- Correct what is wrong (Art. 16);
- Have your data erased (Art. 17) — §7 is the fast path, and you can also write to us;
- Restrict or object to processing (Art. 18, 21);
- Take your data with you in a machine-readable form (Art. 20);
- Withdraw any consent — location, mail, the adult mode — at any time, without giving a reason, without losing the rest of the service;
- Complain to a supervisory authority. Ours is the Polish UODO (Urząd Ochrony Danych Osobowych); you may also complain to the data protection authority where you reside.
§10Security
Passwords are stored as bcrypt hashes. Sessions are short-lived signed tokens. Each account's assistant runs in its own container on its own isolated network with its own storage, with CPU, memory and process limits; containers hold no provider credentials — they reach models only through our gateway. Third-party tokens you give the assistant are stored encrypted. Traffic is TLS-only.
No system is perfect. If we ever suffer a breach that puts you at risk, we will notify you and the supervisory authority within the deadlines the GDPR sets (72 hours), and we will tell you what actually happened.
§11Children
Pocket frAIday is for adults only: you must be 18 or older to have an account. We do not knowingly process the data of children. If you believe a child has an account, write to alex@acebox.eu and we will delete it promptly.
§12Changes to this policy
When we change this policy we update the version and date at the top. For anything that materially affects you we also tell you by email or in the app before it takes effect, and where the law requires consent we ask for it again rather than assuming it.
Previous versions are kept and available on request.
Service Operator & Imprint
Legal entity responsible for this service