PocketOS Privacy Policy
Effective date: 1 November 2026
This policy explains what data the PocketOS app and the PocketOS service process, why, who receives it, how long it is kept and what you can do about it.
1. Who we are
PocketOS is provided by Dmytro Yakushev, 9020, Bulgaria, Varna, Vyara 6b ("we", "us"). We are responsible for the data described in this policy.
Contact: dmitriyzp@gmail.com
2. Summary
- There are no accounts. PocketOS does not ask for your name, email address or phone number.
- The mini-apps you create, their records, and the photos, videos, books and documents inside them are stored only on your device.
- When you build or change a mini-app with AI, the app sends your request, the photos you attach to that request and the structure of the mini-app to our server. Our server removes location and other metadata from the photos and passes the request to our AI model provider (section 8). Records of your mini-apps are not sent with these requests.
- A mini-app can also have an AI action, such as a button that fills in an expense from a receipt photo. Every time, before anything is sent, the app shows exactly what the action will send (a text, a photo or both) and sends it only if you confirm. Nothing else from your records is sent (section 4.3).
- Buttons in a mini-app for web pages, calls, emails, calendar events and sharing pass data from the mini-app to another app on your phone, and only when you tap them. A look-up button, such as "Add by ISBN", sends only the value you entered or scanned, from your phone directly to a website listed in the mini-app's preview (section 7).
- To manage limits, subscriptions and extra AI requests, our server keeps an anonymous device ID, usage counters and records of purchases.
- A mini-app can use your phone's sensors, your location while it is open, and Bluetooth devices nearby. This data is processed only on your device and is not sent to our server or to the AI model provider (section 3).
- We do not show ads, do not sell data and do not use advertising or analytics trackers.
3. Data that stays on your device
The following is stored only in the app's private storage on your device:
- your mini-apps, their versions and settings;
- the records you enter, including photos and videos you add to records;
- books you add from your device or download from a catalog, and your reading position;
- PDF documents the app creates from your records, until you choose to share or save them;
- app settings;
- backup and export files until you choose where to send them.
The app turns off Android's automatic cloud backup for this data. It leaves your device only when you export a mini-app, share it with a QR code, share or save a PDF document, create a backup and send or save the file somewhere, confirm an AI action (section 4.3) or tap a button that looks up a value on a website or opens another app with data from a mini-app (section 7). When you share a mini-app with a QR code, only its structure (screens and fields) is passed on, without records, photos, books or settings.
Uninstalling PocketOS deletes this data. In the app you can also delete it with Settings → Delete all data.
Sensors, location and Bluetooth
A mini-app can show and record readings of your phone's sensors (accelerometer, gyroscope, magnetometer, proximity sensor, air or battery temperature), your location and data from Bluetooth devices nearby — for example a heart rate monitor, a scale or a thermometer. The mini-app's preview names these features before you install it. Your phone gives access to your location and to Bluetooth devices only after you agree in the system dialog. The location is read only while the mini-app is open on the screen: when you tap a button or while a route you started is being recorded; never in the background. All of this is processed only on your device. Readings, coordinates, routes (their summary: distance, time, start and end points) and measurements are stored only if the mini-app saves them in its records, and they leave your device on the same terms as other records (see above). They are not sent to our server or to the AI model provider. When the app searches for Bluetooth devices, it does not use them to find your location and does not show or store their addresses; the device you choose to connect is remembered on your phone so that it can connect to it again.
4. Data we process on our server
4.1 Anonymous device ID
When the app first contacts our server, the server creates a random device ID and a token signed with it. The ID is not derived from your phone's hardware identifiers and is not linked to your name, Google account or email. We use it to count your usage against your plan's limits, to link a subscription to your installation and to prevent abuse. With the ID we store the date it was created, the end date of your 7-day trial, your plan, the day of the last request and the balance of your extra AI requests (section 4.6). You can see the ID in Settings → About and copy it for support requests.
So that there is one trial per phone and it does not start again after you reinstall the app or clear its data, on Android the app sends a trial key when it first contacts our server: a one-way hash (SHA-256) of the identifier Android gives this app on this phone (ANDROID_ID). That identifier is different for every app, changes when the phone is reset to factory settings and never leaves the phone itself; the app does not read the IMEI, serial number or other hardware identifiers. Our server does not store the key itself but a hash of it made with a server secret, together with the end date of the trial and the device ID that sent it last. If the key is already known, the new installation continues that trial, including the AI requests already used, and receives the extra AI requests left on the earlier installation.
With every request the app also sends its version (build number), so that the server can tell when an update is required.
4.2 AI requests
When you create or change a mini-app, the app sends:
- the text of your request (typed or dictated), the language of the app, the plan proposed by the AI and your answers to its questions;
- up to 4 photos you attach to the request;
- when you change a mini-app: its structure (screens, fields, settings of components) and technical messages about errors in that mini-app;
- web addresses mentioned in your request.
Before forwarding photos, our server removes the metadata embedded in them, such as the location where a photo was taken, camera details and comments (EXIF, XMP and similar blocks in JPEG, PNG and WebP files), as far as the file format allows. In the rare case that a file cannot be read this way, it is forwarded unchanged.
Our server checks the request, forwards it to the AI model provider to generate the result, checks the result and returns it to the app. The server does not store your request or photos and does not write request contents to its logs. A finished result is kept in the server's memory or database for up to 24 hours, so that the app can collect it when the connection was lost or the phone was asleep while the server worked, and a repeated request does not count twice.
Newer versions of the app build a mini-app on the phone itself: the app checks the result and, when it finds errors, asks the AI to fix them. Then every step of the build goes through our server as described above: the server adds its own instructions for the AI and forwards the step to the AI model provider. A step sends the same data as listed above, and also the AI's answers to the earlier steps of the same build, the errors that the check found and the text content of web pages that the phone read (section 4.4). Photos are sent with every step, and the server removes their metadata every time. The answer to each step is kept on the server for up to 1 hour, so that a step repeated after a lost connection does not go to the AI again.
Requests for content that our rules do not allow, such as sexual content or deceptive apps, are refused.
The records in your mini-apps, and the photos, videos and books stored in them, are not sent with requests to build or change a mini-app. Only an AI action can send a text or a photo from a mini-app, as described in section 4.3.
4.3 AI actions in mini-apps
A mini-app can contain an AI action: a button that sends a text, a photo or both to the AI and fills in fields or shows a short text with the answer. For example, a button in the Expenses template reads a receipt photo and fills in what was bought, the amount, the date and the category. A mini-app can have AI actions only if the list of permissions in its preview, which you see before you install it, includes AI.
Every time you tap such a button, the app first shows a confirmation with the name of the mini-app, the instruction for the AI, the text and a thumbnail of the photo that will be sent. Nothing is sent until you tap Send; if you cancel, nothing is sent and the action stops. After you confirm, the app sends our server:
- the instruction written in the mini-app;
- the text shown in the confirmation (up to 4,000 characters), if the action sends one;
- the photo shown in the confirmation (one photo stored in that mini-app), if the action sends one;
- a description of the fields the answer should fill in, as they are defined in the mini-app (for example "Amount", a money field, or the choices of a category list), the language of the app and the name of the mini-app.
Of the data in your mini-apps, only the text and the photo shown in the confirmation are sent. Other records, photos, videos, books and documents are not sent, and nothing is sent without your confirmation.
Our server removes the metadata from the photo as described in section 4.2, forwards the request to the AI model provider, checks the answer and returns it to the app. As with other AI requests, the server does not store the request, the photo or the answer and does not write their contents to its logs; a finished answer is kept for up to 15 minutes, so that a request repeated after a lost connection does not count twice. Requests that our rules do not allow are refused. Each successful AI action counts as one AI request of your plan, also when you try it in the preview of a new mini-app (section 4.5).
4.4 Web pages used to build a mini-app
If your request or the AI's plan mentions a public web page, our server downloads that page while building the mini-app and passes its text content to the AI model provider, so that the AI can write rules for reading values from it. For a look-up button (section 7), our server in the same way downloads an example address written by the AI, such as a search for a sample ISBN, checks the rules on it and, if they find nothing, passes the page's text content to the AI model provider to fix them. These requests to websites come from our server and contain no data about you.
When a mini-app is built on the phone (section 4.2), the app itself downloads these pages, the same way as a source of a mini-app (section 7), and sends their text content to our server for the AI model provider. In the same way the app opens public pages that the AI asks to read, to check whether data can be taken from them. Then the website sees the IP address of your phone; these requests contain no other data about you.
4.5 Usage counters and limits
For each device ID we keep the number of AI requests used in each month and short-lived counters (for example, the number of requests in the last 10 minutes) that protect the service from overload. Extra AI requests that are used are subtracted from the balance described in section 4.6. We also keep daily totals per operation without any device ID: the number of requests, their duration, the amount of AI processing used, its cost and error codes.
4.6 Subscriptions and purchases
Subscriptions and packs of extra AI requests are sold and paid through Google Play. We do not receive your card details or your Google account name.
When you buy or restore a subscription, the app sends our server the product ID and the purchase token from Google Play. Our server checks the purchase with Google, confirms it and stores the purchase token, the product, the plan, the subscription status, its expiry date and whether it renews automatically.
Packs of extra AI requests are one-time purchases. When you buy one, the app sends our server the product ID and the purchase token. Our server checks the purchase with Google, adds the pack to your balance once per purchase, confirms the purchase to Google as used up (consumed) and stores a record of it: the product, the purchase token, the number of requests added, the date and whether the purchase was later refunded or cancelled. With your device ID we keep the balance of extra AI requests and the list of these records.
With every purchase the app passes Google an obfuscated reference derived from your device ID (not the ID itself), so that the purchase can be matched to your installation. Google notifies our server about changes to your subscription, such as renewals, cancellations and refunds, and about refunds and cancellations of one-time purchases.
If support extends your trial or gives your device a plan manually, adds or removes extra AI requests (for example when moving them to another phone), or you enter an access code, we store the plan and its end date or the number of requests, the code (if any) and a short internal note.
4.7 Error reports
If the app crashes or meets an unexpected error, it sends an error report to our server: the app version and build number, the platform and operating system version, whether the error closed the app, the type and message of the error and the stack trace. The report is stored without your device ID. It is designed not to include your records or requests, but an error message can occasionally contain a fragment of text that the app was processing.
Error reports are on by default. You can turn them off in Settings → Send error reports; reports that have not been sent yet are then deleted from your device.
4.8 Reports about AI results
If you report a result of the AI, including a result of an AI action, the app sends the reason you chose, your optional comment, the request text (for a mini-app you have already installed, its description; for an AI action, what the action asked the AI) and the name of the mini-app. Photos are not sent with a report. The report is stored together with your device ID, so that we can see repeated problems and prevent abuse of the report form. We use these reports to find and fix problems with generated content.
4.9 Technical logs and backups
Our web server records the IP address, time, requested address, response code and app user agent of each request, in order to keep the service secure and to investigate failures. The application server records, for failed, slow and AI requests, only the time, method, address and response code, without IP addresses or request contents. We make daily backups of the server database.
4.10 Support requests
If you write to us, we receive your email address and whatever you include in the message, such as your device ID. We use it only to answer you.
5. Books, catalogs and PDF documents
- Books you pick on your device are copied into the app's private storage through the system file picker. PocketOS gets access only to the files you pick. Book files are never sent to our server or to the AI model provider.
- Book catalogs (OPDS) are contacted directly by your device: when you browse or search a catalog, your device sends the catalog's server the page address and the search words you typed, together with standard technical information such as your IP address and the app's user agent. Downloaded books are saved only on your device. The built-in catalog is Project Gutenberg; other catalogs are the ones you add yourself. Each catalog's own privacy policy applies to these requests.
- PDF documents, such as invoices or reports, are created on your device from your records. They leave the device only when you share or save them through the system share sheet.
6. Features handled by Google on your device
- Voice input uses the speech recognition service of your phone; on most Android phones it is provided by Google. That service records and processes your voice under its provider's terms, which may involve sending the audio to the provider's servers. PocketOS does not receive or store the audio; it receives only the recognised text, which you can edit before sending.
- Scanning of QR codes and barcodes uses Google's ML Kit library, which works on your device. Camera images are not stored or sent. ML Kit may send Google technical information, such as the device model, operating system and app version, performance metrics, error codes and a per-installation identifier, for diagnostics and usage analytics. It does not send camera images.
- Photos for your mini-apps are taken with your camera app and selected with the system photo picker, which gives PocketOS only the photos you select.
- Your location comes from the phone's location services; on most Android phones these are Google Play services. If Google Location Accuracy is on in your phone, Google processes Wi-Fi, mobile network and sensor information under its own terms. PocketOS gets only the coordinates, accuracy, altitude and time from these services.
- PDF books are displayed with Android's built-in PDF renderer on your device.
- Purchases are processed by Google Play under Google's terms and privacy policy.
Google's privacy policy: https://policies.google.com/privacy
7. Web pages and other apps in your mini-apps
A mini-app can check public web pages you chose, for example to read an exchange rate or a price. Your device downloads such a page directly from the website, on a schedule and when you open the mini-app. The request contains only the page address and standard technical information, such as your IP address and the app's user agent, and no data from your mini-apps. The website's own privacy policy applies to that request.
Some mini-apps have look-up buttons that find information on a public website or web service by a value. For example, "Add by ISBN" fills in a book's title, author and number of pages from the ISBN barcode you scan, and "Add by barcode" finds the name of a product. When you tap such a button, your device sends the request directly to that website, not through our server. The request contains only the website's address with the value being looked up, such as an ISBN, a barcode or another value you entered, and standard technical information, such as your IP address and the app's user agent. The answer is used on your device to fill in fields of the mini-app. The websites a mini-app can contact in this way are fixed in the mini-app and listed in its preview, which you see before you install it. The website's own privacy policy applies to that request.
A photo field of a mini-app can also show a picture from a link: a link you paste, a link you keep in the mini-app (for example, to a film poster) or a picture link on a page or in an answer described above. Your device downloads such a picture once, directly from the website that hosts it, and keeps it on the device like your other photos. The request contains only the picture's address and standard technical information, such as your IP address and the app's user agent. The preview of a mini-app that can do this says "pictures by links". The website's own privacy policy applies to that request.
A mini-app can also have buttons that hand data to another app on your phone: open a web page in your browser (its address can contain values from the mini-app), open the phone's dialer with a number, open your mail app with a new email, open your calendar app with a new event, or open the system share sheet with a text. The data comes from the mini-app, for example a client's phone number or the date of an event, and is passed only when you tap such a button. PocketOS does not place calls, send emails or save events by itself: the other app shows the data, and you decide whether to call, send or save. PocketOS does not need access to your contacts, calls or calendar for this. From that point, the terms and privacy policy of the app or website you use apply.
8. Who receives data
We use the following service providers:
- The AI model provider generates mini-apps and answers AI actions. It receives the request text, attached photos without their metadata, the mini-app structure, answers to questions and the content of web pages used to build the mini-app (section 4.4); for AI actions, the instruction, the text and the photo shown in the confirmation and the description of the fields to fill in. It processes this data under its own terms and privacy policy. We currently use DeepSeek (https://platform.deepseek.com); it processes and stores this data in the People's Republic of China. If we change the provider, this page names the new one before requests go to it.
- Google (Google LLC and its affiliates) processes purchases and subscription notifications (Google Play, Google Cloud Pub/Sub), provides the speech recognition service on most Android phones and the ML Kit library.
- Zynoo.com hosts our server in Bulgaria.
Apps and websites you open from a mini-app, and websites where a mini-app looks up a value when you tap a button (section 7), receive the data you pass to them. We do not control them.
We disclose data to authorities only when the law requires it. If the service is transferred to another operator, this policy and your choices continue to apply to your data.
9. International transfers
Our server is located in Bulgaria. AI requests, including AI actions, are processed by the AI model provider in the People's Republic of China. Google may process data in the United States and other countries. These countries may have data protection laws different from those in your country.
10. Legal bases (for users in the EEA, the UK and similar jurisdictions)
- Performance of our contract with you, to provide AI features, limits, subscriptions and extra AI requests (sections 4.1–4.6).
- Our legitimate interests in keeping the service secure, preventing abuse and fixing errors (sections 4.5, 4.7–4.9). You can object to error reports by turning them off.
- Compliance with legal obligations, for example answering lawful requests and handling refunds.
11. How long we keep data
- Anonymous device ID, its usage counters, plans, purchase records and the balance of extra AI requests: while your installation keeps using the service. When a device has not contacted our server for 24 months, we delete its record together with its counters, plans and purchase records, unless a subscription or plan still gives it access or it still has unused extra AI requests.
- Request text, attached photos and what AI actions send: not stored; processed only for the time of the request. Finished results of creating or changing a mini-app: up to 24 hours. Answers to the steps of a build on the phone: up to 1 hour. Answers to AI actions: up to 15 minutes.
- Trial key (its hash made with a server secret): 24 months after the trial ended and the key was last used by an installation.
- Short-lived counters and reservations used for limits: up to an hour; counters of the steps of a build on the phone: up to 6 hours; the counter of returned AI requests: one day.
- Daily totals without device ID: kept for statistics.
- Error reports: 90 days.
- Reports about AI results: 1 year.
- Web server logs: 14 days.
- Server backups: 14 days.
- Support emails: up to 2 years after the conversation ends.
12. Your rights and choices
Depending on where you live, you may have the right to access, correct or delete your data, to restrict or object to its processing, to data portability and to withdraw consent. To use these rights, write to dmitriyzp@gmail.com and include your device ID from Settings → About, because without accounts we can identify your data only by this ID. We answer within 30 days. You can also complain to your data protection authority.
Your choices in the app:
- you decide whether to use AI features and what to attach to a request;
- you see what each AI action will send and decide every time whether to send it;
- you decide whether to open another app or look up a value on a website from a mini-app (section 7);
- you decide which books and catalogs to add;
- you can turn off error reports in Settings;
- you can refuse or withdraw access to the camera, microphone, location, Bluetooth devices ("Nearby devices") and notifications in your phone's settings; the related features then stop working, and the rest of the app keeps working.
13. Deleting your data
- On your device: Settings → Delete all data deletes all mini-apps, records, photos, videos, books and documents in them and cancels scheduled notifications. Uninstalling the app deletes everything, including the device token.
- Delete all data keeps the device ID on purpose, because your subscription and your extra AI requests are linked to it. The server therefore still sees the same device until you uninstall the app or ask us to delete the server data.
- On our server: write to dmitriyzp@gmail.com with your device ID. We delete the device record, its usage counters, plans, the link to purchases, the balance and records of extra AI requests and the reports sent from it. A subscription you paid for can be linked again later with Restore purchases; extra AI requests deleted this way cannot be restored. Error reports are stored without a device ID, so they cannot be found by device; they are deleted after 90 days. Deleted data disappears from backups within 14 days.
14. Children
PocketOS is not designed for children and is intended for people aged 18 and over. We do not knowingly collect data from children. If you believe a child has used the service, write to us and we will delete the related data.
15. Security
The app connects to our server only over encrypted connections (HTTPS). Device tokens are signed and checked on the server, the AI provider's key is kept only on the server, and access to the server and its administration tools is restricted. No method of transmission or storage is completely secure, but we work to protect your data.
16. No sale, no advertising, no tracking
We do not sell or rent personal data, do not share it for advertising and do not use it to build profiles. The app contains no advertising and no third-party analytics SDKs.
17. Changes to this policy
We may update this policy when the app or the law changes. The effective date at the top shows the current version. If a change significantly affects how we use your data, we will tell you in the app before it takes effect.
18. Contact
- Dmytro Yakushev
- 9020, Bulgaria, Varna, Vyara 6b
- Email: dmitriyzp@gmail.com