1. Information stored on your device

Aldang stores notifications only from apps you have turned on for collection. Notifications from apps you turned off are discarded immediately without being stored. Finance and health apps are off from the start.

• Package name and display name of the app that sent the notification
• Notification title, body, and sub-text
• Conversation name, when the sending app provides one
• Time the notification arrived
• The notification category assigned by Android
• Photos attached to a notification (scaled down to 512 px on the long edge; never sent off the device)
• Identifiers used to group notifications from the same conversation
• Names and icons of apps installed on your device, used only to show the collection list
• Times the notification listener connected and disconnected, recorded so the app can tell you when collection was interrupted
• AI briefing results you created, and app settings

This information is used for the inbox, search, categorisation and statistics, all of which run on the device. The only time any of it leaves the device is an AI briefing (section 2).

Aldang has no accounts. It does not collect your name, phone number, email address, contacts or precise (GPS) location, and it does not collect the advertising ID. Emails you send us yourself are covered in section 14.

2. AI briefing: the one case where notification content leaves the device

Data is sent only when you pick a day and tap Generate briefing. Nothing is sent automatically. The first time, the app explains what goes where and asks for your consent; if you do not agree, or do not tap, nothing is sent. Uninstalling the app or clearing its data also removes the consent record.

• What is sent: notifications from the day you picked (or from after that day's previous briefing), excluding apps you left out of the briefing, up to 512 of them. For each notification, the time it arrived, the sending app's package name, the sender, the title and the text are joined and cut to 800 bytes. One request stays under about 200 KB in total. The app language, time zone and reference time are sent too, along with a hash of each notification's on-device number. Photos are never sent.
• Where it goes: from the device to the Aldang server (run on Cloudflare), from there to OpenRouter, and from OpenRouter to the AI model provider. Every leg is encrypted with HTTPS. The Aldang server asks OpenRouter to use zero-data-retention endpoints only. Briefings are currently made by an OpenAI model run on Microsoft Azure.
• What is kept: neither the Aldang server, OpenRouter nor the AI model provider keeps the notification text or the summary. OpenRouter keeps request metadata such as the time, the model used and token counts. OpenRouter also samples a small share of requests and has a model that keeps no data classify only their topic, keeping only the classification results, which are not linked to any account. What the Aldang server keeps is listed in section 4.
• The result: the summary comes back to the device and is stored only there.

3. Subscription and membership codes

AI briefing comes with the Aldang Pro subscription or a membership code. You subscribe without creating an account: payment goes through Google Play with the Google account signed in on your device. Google handles payment details such as card numbers; Aldang never receives them. When you request a briefing, the app sends the purchase token issued by Google Play to the Aldang server, which asks Google Play for the subscription's status. The server keeps only a hash of the token, the subscription's expiry time and when it last checked, never the token itself.

When you enter a membership code, the app sends it to the Aldang server to check it. The server records which code was entered and when, and a hash of the access token it issues to this installation. Later briefing requests carry that access token.

4. Records kept on the Aldang server, and for how long

The Aldang server keeps no notification text. It keeps the records below, none of which contains a name, email address or anything else that directly identifies you.

• Request fingerprint: an HMAC computed from the briefing request, used so the same request is never processed twice. Notification content cannot be recovered from it. Deleted 12 months after it is created.
• Usage record: request time, the date used to count daily briefings, processing status, token counts and cost, and the request ID assigned by OpenRouter. Used for the three-a-day limit and cost accounting. Deleted 12 months after it is created.
• Subscription check record: a SHA-256 hash of the Google Play purchase token, the subscription's expiry time and the time it was last checked. Deleted 12 months after the subscription ends.
• Membership record: an identifier of the code entered, when it was entered, and a hash of the access token. Deleted 12 months after the membership ends.
• Connection logs: the operational logs of Cloudflare, which runs the server, may contain IP addresses and request times. They are used only to look into errors and abuse, and are kept for up to 7 days.

After these records are deleted, they can remain recoverable for up to 30 days in the server database's point-in-time backups (Cloudflare D1 Time Travel).

5. Usage statistics (Firebase Analytics)

To learn which features are used and where people get stuck, so the app can be improved, Aldang uses Google's Firebase Analytics (Google Analytics for Firebase).

• Events Aldang sends: setup finished, notification access granted, subscription screen viewed (and whether from setup, Today or Settings), sample briefing viewed, free trial started (and from where), briefing completed. None of them contains notification content, senders, titles, text or app package names.
• What Firebase collects automatically: a random identifier for each app installation (the app instance ID); basic events such as first open, sessions, screen views and app updates; in-app purchase and subscription events (product ID, product name, price); device type (model), OS version, language and app version; where the app was installed from (the Google Play install referrer); and approximate location (country, region, city) derived from your IP address, which Firebase masks before using it.
• Google Play link: Firebase is linked to Google Play, so Google Play sends subscription status changes (free trial started, charged, renewed, cancelled, refunded) and their amounts to usage statistics. This tells us how long subscriptions last. It never includes notification content or payment details such as card numbers.
• What is not collected: advertising ID collection is turned off, and so are ad personalisation signals. Usage statistics are not used for advertising.
• Turning it off: in most countries it is on from the start, and you can turn it off at any time under Settings › Send usage statistics. Nothing is sent after you turn it off.
• EEA, UK and Switzerland: if your device's region setting, SIM country or mobile network country is in one of these, the app asks for your consent first and sends nothing until you agree. You can turn it off later in the same setting.
• Retention: user-level and event-level data in Google Analytics is set to be deleted after 2 months. Aggregated report figures remain after that.

6. Service providers and transfers abroad

Aldang uses the companies below to process data. Data the app sends reaches them over HTTPS when you use the related feature; support emails travel as described in section 14. These companies may process data outside your country.

• Cloudflare, Inc. (United States and other countries, wherever the Cloudflare data centre that receives the request is): runs the Aldang server. AI briefing requests, subscription checks and membership code checks pass through it, and it holds the records in section 4. It also receives support emails (section 14) and forwards them to Gmail without storing their content.
• OpenRouter, Inc. (United States): passes AI briefing requests to the AI model provider. Keeps no notification text, only request metadata.
• Microsoft Corporation (Microsoft Azure data centres in the United States and other countries): generates the briefing summary. Requests go to zero-data-retention endpoints only.
• Google LLC (United States and other Google data centres): Firebase Analytics usage statistics, Google Play billing and subscription checks, and sending, receiving and storing support emails (section 14) in Gmail.
• Anthropic, PBC (United States and other countries): the AI tool (Claude) we use to summarise support emails (section 14) and draft replies.

If you do not want any of this, do not use AI briefing and turn usage statistics off. The inbox, search and statistics keep working. For support emails, see section 14.

7. Storage and safeguards

• Notifications and briefing results are stored in a database inside your device's app-private storage, which Android keeps inaccessible to other apps.
• When a screen lock is set on the device, Android's storage encryption also applies to this data.
• Everything sent off the device is encrypted with HTTPS.
• The Aldang server stores purchase tokens and access tokens only as hashes, never in their original form. Membership codes are checked by their hash. Shared codes, which are given out publicly to many people, also keep the code text for management; personal codes, given to one person, keep only their last four characters.
• Notification content is never sold or used for advertising. The app includes no advertising or crash-reporting tools.

8. Retention and deletion on your device

• Stored notifications stay on the device until you delete them.
• Under Settings › Data you can delete notifications older than 7, 30 or 90 days, or delete all stored notifications at once.
• Uninstalling the app removes all stored data from the device permanently.

9. Your rights and deletion requests

Your notifications, briefing results and settings stay on your device, so you can view, correct and delete them yourself, immediately, inside the app. ByteCreo has no means of accessing data on your device and therefore cannot act on it for you.

Requests to see or delete the server records in section 4 can be sent to support@bytecreo.com. Those records contain no name or email address, so a request alone does not tell us which records are yours. Subscribers, please include your Google Play order number (it starts with GPA); membership users, please include the code you entered. If we can find the records with that, we delete them and tell you. Records we cannot find are still deleted when the periods in section 4 run out.

You can also ask to see, correct or delete your support emails (section 14), or ask us to stop processing them, at support@bytecreo.com. We check that the request comes from the address you emailed us from, act on it without delay and tell you the result.

You can turn usage statistics off under Settings › Send usage statistics. Statistics are linked only to a random identifier for each installation; clearing the app's data or reinstalling starts a new one.

You can cancel a subscription in Google Play. For questions about this policy, write to support@bytecreo.com.

10. Permissions the app uses

• Notification access (required): used to read and store notifications. Without it the app cannot do what it exists for. You can revoke it in Android settings at any time; collection stops from that moment.
• Installed app list: the app queries only apps shown in the launcher, to build the list of apps you choose to collect from.
• Post notifications (optional): used to tell you when collection has stopped.
• Request to ignore battery optimisation (optional): asks, through a system dialog, to let the app avoid being put to sleep so collection does not stop. Declining leaves every other feature working, and you can undo it in Android settings at any time.
• Internet: used for AI briefings and the subscription check that comes with them, for entering a membership code, and for sending usage statistics while they are on. Notification content goes nowhere except an AI briefing.
• Google Play billing: used to pay for Aldang Pro and, when the app starts, to check this device's Google account subscription with Google Play again. That check carries no notification content.
• Permissions added by libraries: the Firebase SDK adds network state, wake lock and Google Play install referrer permissions, and the Google Play billing library adds the BILLING permission. The app does not ask for these.

11. A note on exported files

The app's export produces a JSON file containing the full text of your notifications. Once you share that file with another app or a cloud service, that service's policies apply to it, so please share it with care.

12. Children

Aldang is not directed at children under 14 and does not knowingly collect their personal information.

13. Changes to this policy

If this policy changes, the updated text and its effective date will be posted on this page and announced inside the app.

• Effective 11 October 2026 (posted 4 October): added how support emails are handled (section 14), added Anthropic, PBC (Claude) to section 6 together with support email forwarding for Cloudflare and Gmail for Google, and moved Contact to section 15. The previous version took effect on 1 October 2026.

14. Support emails

If you email us about Aldang at support@bytecreo.com, or at bytecreo@gmail.com (the address our replies come from), we handle your email as below so that we can reply. This covers only emails you send yourself, not anything the app sends.

• What we receive: your email address and name (if shown in the email), and the content and attachments of your email
• Why: to read and answer your question
• Legal basis: we need it to answer the request you made, so we do not ask for separate consent (Article 15(1)(4) of Korea's Personal Information Protection Act)
• How long: permanently deleted from our mailbox, including the bin, within one year of receipt
• Service providers and transfers abroad: email sent to support@bytecreo.com passes through Cloudflare to Gmail as soon as it arrives, and your email is sent to Anthropic when we read it and draft a reply. Mail servers encrypt it with TLS when your email provider supports this, and the connection to Anthropic uses HTTPS.
  • Cloudflare, Inc. (United States and other Cloudflare data centres, wherever the email is received, 101 Townsend St., San Francisco, CA 94107, USA, dpo@cloudflare.com): receives email sent to support@bytecreo.com and forwards it straight to Gmail (Email Routing). It does not store its content.
  • Google LLC (United States and other Google data centres, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA, policies.google.com/privacy): sending, receiving and storing email (Gmail), for the period above.
  • Anthropic, PBC (United States and other countries, 548 Market St, PMB 90375, San Francisco, CA 94104, USA, privacy@anthropic.com): the AI tool (Claude) we use to summarise your email and draft a reply. Because model training is turned off on our account, what we put into Claude is deleted after 30 days and not used to train AI models. However, if Anthropic flags a conversation for a usage-policy review, it may keep it for up to 2 years and use it to improve its models for safety purposes, and it may keep data longer where the law requires.
• If you do not want this: please do not email us. As we only take questions by email, we cannot answer your question without one. If you already have, ask us and we will delete your email and our records of it without delay; any copy Anthropic holds is deleted after the period above.

15. Contact

Data controller: ByteCreo
Contact: support@bytecreo.com