allob
Privacy Policy
Version 3 · Effective: 2026-11-05
Summary
- What: account information (email), sign-in and access records, business information, connections to outside services and the business data fetched through them, product and bookkeeping records, encrypted items you keep in the vault, activity records, the devices that receive notifications and notification records, Ask conversations and the photos attached to them, problem reports with the screen details sent with them, feedback sent from the phone app, phone app error records, invitation records, and support emails.
- Worth noting: allob also receives and stores usage events, payment notices, store reviews, and app feedback from your products, and comments on social accounts you connect. We process this information on your instructions, and you, as the user who runs the product, inform those people through your own privacy policy.
- Why: sign-in, providing the service, tasks you ask us to run on outside services, answers in Ask, invitations, notifications, security, fixing problems you report and errors in the phone app, and answering questions and feedback.
- Who and where: servers and storage Cloudflare, Inc. (United States), connection relay Oracle Corporation (Japan), delivering phone app notifications 650 Industries, Inc., Apple Inc., and Google LLC (United States), answering in Ask Anthropic, PBC, OpenAI, L.L.C., and OpenRouter, Inc. (United States), support email NAVER Corp. (South Korea). We do not disclose personal data to third parties.
- Google and Meta: we use information from the Google and Meta accounts you connect only to show it to you and to carry out what you ask.
- How long: most data until you delete your account. Usage events are deleted 3 months after they are received, Ask conversations 90 days after the last question, notification records after 30 days, app feedback and feedback sent from the phone app after 2 years, problem reports 1 year after they are received, phone app error records 90 days after they are received, social comments 30 days after a reply or after they are fetched, and access logs within 7 days.
- Your rights: you can ask to access, correct, delete, or stop processing your data, and you can delete your account yourself in Account settings.
Controller and privacy contact
The controller of allob (https://allob.app) is winterlog studio ("we", "us"), and the privacy contact is our owner, Hyungu Kang. Send requests, questions, and complaints about this policy to the contact details below.
- Address: 5-12 Gwangmyeong-ro 347beon-gil, Jungwon-gu, Seongnam-si, Gyeonggi-do, Republic of Korea
- Phone: +82 10 9688 1157
- Email: support@allob.app
- Business registration number: 577-24-02412
Purposes and legal bases
We process personal data on the legal bases below, not on consent.
| Purpose | Data used | Legal basis |
|---|---|---|
| Sign-up, sign-in, and keeping you signed in (including CLI and agent device sign-in and phone app sign-in) | Account information, sign-in records | Performance of a contract (Personal Information Protection Act, Article 15(1)4) |
| Providing the service, such as products, boards, books, legal document drafts, metric alerts, and search visibility checks | Account information, business information, fetched business data, products and records | Performance of a contract |
| Connecting outside services and running the tasks you ask for (fetching data, changing ads, publishing posts, generating images and videos) | Connection information, fetched business data, image and video requests | Performance of a contract |
| The vault | Vault items | Performance of a contract |
| Ask (answering your questions and preparing figure cards and suggested social posts) | Ask conversations, attached photos, fetched business data, products and records | Performance of a contract |
| Sign-in code and alert emails, and web and phone app notifications | Account information, devices that receive notifications, notification records and settings | Performance of a contract |
| Processing data about the users of your products (receiving and totaling events and payment notices, receiving store reviews and app feedback, passing payment events to the ad and analytics tools you turn on, showing social comments) | Data about the users of your products, social comments | Processing entrusted by you (Personal Information Protection Act, Article 26) — we act as your processor |
| Security (activity records, request limits, access logs, confirming it is you when you approve in the phone app) | Activity records, access logs, sign-in records | Legitimate interest: protecting accounts and the service from unauthorized access and abuse (Personal Information Protection Act, Article 15(1)6) |
| Invitations (letting new users in by invitation during the beta, and showing invited people who invited them) | Invitation records (email of the person who invited and of the person who used the invitation, the account created, times) | Performance of a contract |
| Making sure an invitation addressed to an email is used only by that person | The invited person's email | Legitimate interest: making sure an invitation link is used only by someone signed in with the email the inviter entered |
| Receiving problem reports, finding the cause, and fixing it | Problem reports | Performance of a contract |
| Finding and fixing errors in the phone app | Phone app error records | Legitimate interest: finding and fixing problems that close the app or keep a screen from opening (Personal Information Protection Act, Article 15(1)6) |
| Answering questions and feedback sent from the phone app | Support emails, feedback sent from the phone app | Performance of a contract |
What we collect
| Data | Source |
|---|---|
| Account information (email address, sign-up and last sign-in time, display language setting) | You enter it when you sign up or sign in, and it is created as you use the service |
| Sign-in records (sign-in sessions, device name and country of access when you sign in a device, device name and type when you sign in to the phone app, the phone app's approval secret) | Created automatically when you sign in. The approval secret is created by the phone app |
| Business information (business name, owner name, business registration number, business address, public email and phone number, mail-order business number, D-U-N-S number) | You enter it |
| Connection information (connection tokens and API keys, ID, name, and email of the connected outside account) | Provided by the outside service when you connect it |
| Fetched business data (sales and payment totals, ad accounts, campaigns, ad creatives, ad spend and results, analytics reports, ad earnings, store ratings, social posts, engagement stats, and comments with commenter names) | Fetched from the services you connect |
| Products and records (product details and event schemas, release and change records, progress records, bookkeeping records of sales, payouts, and expenses and tax filing materials, legal document drafts and published documents, metric alerts, search visibility check results, app review status, email of the person who created a record) | You enter them, or they are created as you use the service |
| Vault items (encrypted signing keys and documents, passkey public keys and names) | You upload them |
| Image and video generation (request text, reference images, generated results) | You enter or upload them |
| Ask (questions and answers, the account data read to answer, attached photos, daily usage) | You write or choose them, and the answers are made by AI |
| Activity records (email, device name, country, and time of the person who acted, and what they did) | Created as you use the service |
| Devices that receive notifications (web push address or phone app notification token, device name, device type) | Created by your browser or the phone app when you turn on notifications |
| Notification records and settings (notification type, subject, and time; which notifications to get, quiet hours, and morning summary settings; to-do items you put off) | Created as you use the service; you choose the settings |
| Access logs (IP address, browser information, requested address, time) | Created automatically when you visit |
| Data about the users of your products (usage events, random device identifier, country, language, referral source, payment notices, and the IP address, browser information, and ad click markers sent along when passing events to ad and analytics tools; store reviews (title, text, rating, the reviewer's store display name, country, language, app version, device); app feedback (text, rating, the screen it was sent from, the user ID, email, and name your product sends with it, device type and app version, and an IP check value that changes every day)) | Sent by your products, your payment services, and the app stores you connect |
| Invitation records (email of the person who invited, of the invited person if one was named, and of the person who used the invitation; the account created with it; times it was created, used, and canceled) | Created when an invitation is made or used. The invited person's email is entered by the person who invites |
| Problem reports (what you write, the sender's email, role, and account, and the screen details at that moment: screen path and screen version, browser type, screen size, and language, error records, failed requests, and data loading records (name of what was loaded, status, error)) | You write it when you report a problem, and the allob app collects the screen details along with it |
| Feedback sent from the phone app (the text you write, the email for a reply if you enter one, the app version, operating system and version, device model, screen it was sent from, and device language sent with it, country of access, and an IP check value that changes every day) | You write and send it under More › Support in the phone app. The app gathers the details sent with it and shows them on screen before you send. Your signed-in account and email are not sent with it |
| Phone app error records (app version and build number, operating system and version, device model, the kind of screen where the error happened, error name, message, and code location, when and how many times it happened, and whether the app closed. They hold no account, email, what you typed, or data on the screen, and tokens, cookies, and email addresses in the error text are masked) | When an error happens in the phone app, the app notes it on the device and sends it without sign-in details the next time you open the app. It is not tied to an account or email, so we cannot tell whose record it is |
| Support emails (email address, message) | Emails you send us |
We use cookies to keep you signed in and to protect the process of connecting outside services. Both are necessary for the service, and if you clear them you will need to sign in again.
Disclosure to third parties and connected services
We do not disclose personal data to third parties.
You can connect Google (Analytics, AdMob, Google Play), Apple (App Store Connect), RevenueCat, Meta (ads), Instagram, Threads, Facebook Pages, TikTok, Dodo Payments, and fal with your own accounts or keys. We use information received through these connections only to show it to you and to carry out what you ask, and we do not use it for advertising, sale, or AI training.
Tasks you ask for (turning ads on or off and changing budgets, publishing posts and replies, image and video generation requests, passing payment events) are sent to that service. What that service receives is governed by its own terms and privacy policy.
- Google: from a Google connection we receive your account ID, email, and name (to show which account is connected), and read-only Google Analytics and AdMob reports. Analytics report results are stored as a copy of the board, replaced each time the board is recalculated, and deleted when you remove the Google connection or delete the account. AdMob ad earnings are stored by day.
- Meta, Instagram, Threads, and Facebook Pages: we receive the campaigns, ad sets, ads, ad creatives, ad spend, and results of the Meta ad accounts you connect, and the posts, engagement stats, and comments (including commenter names) of the Instagram and Threads accounts and Facebook Pages you connect. We use them only to show them on your boards and to carry out the ad changes, posts, and replies you ask for.
- People read this data only when you ask us to, or when needed for security or to comply with the law.
allob's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy
How to disconnect or delete this data is described in the account deletion section below.
Data that stays in your browser and device
The email address you are signing in with (briefly, after a code is sent) and your display settings are kept only in your browser's storage. Vault items are encrypted in your browser or the CLI before upload, and the keys that open them (unlocked by your PIN, passkey, or recovery code) are not kept on our servers. CLI sign-in details are kept in a settings file on your computer and in your operating system's key store. This data is not sent to our servers, and it is gone when you clear your browser data or sign out of the CLI.
The phone app keeps your sign-in details in the device's secure storage, and your display settings and whether notifications are on in the app's storage. They are gone when you sign out or delete the app. The app receives only the photos you choose in the photo picker, and uploads them, reduced in size, only when you attach them in Ask. Phone app error records wait in the app's storage until they are sent, up to 5 of them, and are deleted once sent.
Face ID, fingerprint, or screen lock (PIN, pattern, or passcode) checks used to approve in the phone app are done by your device, and no face or fingerprint data or screen lock code comes to us. The app creates an approval secret, keeps it in the device's secure storage locked by Face ID, fingerprint, or screen lock, and sends the same value to our server once, where it is stored encrypted. Each time you approve, the app signs the request with that value so we can confirm the approval came from that device, and when you sign out it is deleted from both the device and our server. The phone's key that opens the vault without a PIN is kept separately so that only Face ID or fingerprint can open it; a screen lock alone cannot.
Data about your products' users and other people
allob receives usage events and app feedback from the users of your products through the allob SDK and server code you add to your products (web, app, server), payment notices from the payment providers you connect (Dodo Payments, RevenueCat), store reviews of your products from the app stores you connect (App Store Connect, Google Play), and comments on posts from the social accounts you connect.
The purpose is to show you your products' usage, payments, ad results, reviews, and feedback, and to pass payment events to the ad and analytics tools you turn on (Meta, TikTok, Google Analytics). We do not store IP addresses with events, only the country, and we do not store names or email addresses with payment notices. With app feedback we do not keep the IP address itself, only a check value that changes every day and is used to prevent abuse. When passing payment events to ad and analytics tools, we send the IP address, browser information, and ad click markers from the purchase along with them, but we do not store them and use them only for request limits and for passing the events.
We process this information as a processor on your instructions. The allob user who runs the product informs those people and gets any consent needed, through their own privacy policy. We do not notify them separately. Please send requests about this information to the allob user who runs the product. If you ask us, we will tell you which product the information came from.
The email of an invited person is entered by the user who invites them. Only someone signed in with that email can use the invitation, and an unused invitation is deleted 30 days after it expires or is canceled.
Retention periods
| Data | Retention period |
|---|---|
| Account information | Until you delete your last account yourself or ask us to delete it |
| Sign-in records | Until you sign out, or 30 days after sign-in on the web and 90 days for CLI and agent devices. For the phone app, until you sign out or 90 days after you last used it (at most 1 year after sign-in), together with the approval secret |
| Business information, fetched business data, products and records, vault items, image and video generation, activity records, payment notices and store reviews from your products, notification settings | Until you delete the account |
| Connection information | Until you disconnect (connection tokens and API keys are deleted as soon as you disconnect). The connected account name is kept until you delete the account |
| Generated images and videos you did not mark "Keep" and did not use in ads | 30 days after creation |
| Social comment text and commenter names | 30 days after you reply or skip, or 30 days after they are fetched if not replied to |
| Ask conversations | 90 days after the last question (deleted right away if you delete the conversation). Attached photos are kept until you delete them or delete the account |
| Usage events from your products | 3 months after they are received |
| App feedback from your products | 2 years after it is received (or when you delete it or delete the account) |
| Devices that receive notifications | Until you sign out or turn off notifications (or when notifications stop reaching the device because the app was deleted) |
| Notification records | 30 days after they are created (a notification held during quiet hours is kept until it is sent) |
| Access logs | Within 7 days |
| Problem reports | 1 year after they are received (deleted right away if that account is deleted) |
| Phone app error records | 90 days after they are received. They are not tied to an account or email, so deleting your account does not delete them sooner; they are deleted when the period ends |
| Invitation records | Unused invitations: 30 days after they expire or are canceled. Records of used invitations are kept like account information, and when the person who invited or the person who used the invitation deletes their last account, we delete that person's email (unused invitations they made are deleted, and unused invitations addressed to them are canceled) |
| Feedback sent from the phone app | 2 years after it is received. It is not linked to your account, so it stays after you delete your account; we delete it if you ask us at the details above |
| Support emails | 1 year after we reply |
We do not keep any personal data separately to meet a legal retention duty.
Deletion and deleting your account
When a retention period ends or the purpose is met, we delete the data without delay so that it cannot be recovered.
- Delete an account: the account owner can delete an account in the web app under Account settings › Delete account or in the phone app under More › Delete account. Products, connection information, business information, fetched business data, vault items, records, payment notices, store reviews and app feedback, Ask conversations, notification records and settings, and images and videos are deleted at once and cannot be restored. Usage events already received are deleted 3 months after they were received. If the person deleting has no other accounts, their sign-in email record, sign-in sessions, device and phone app sign-ins, and devices that receive notifications are deleted too, and they are signed out. The steps and what is kept are also on the account deletion page (https://allob.app/account-deletion).
- Leave allob: anyone can leave under Account settings › Leave allob on the web or More › Leave allob in the phone app. They are removed from every account they belong to, and their sign-in email record, sign-in sessions, device and phone app sign-ins, devices that receive notifications, Ask conversations, and notification settings are deleted at once. If they own an account, they must delete that account first. Account records (who changed what) stay with that account.
- Delete only an Ask conversation: delete it from the conversation list in the phone app and it is deleted at once.
- Disconnect only: press "Disconnect" on the Connections screen to delete that service's connection tokens and API keys at once. You can also revoke the access you gave at the outside service (Third-party connections under Security in your Google Account, Business integrations in Meta business settings or Facebook settings, or Website permissions in Instagram and Threads settings).
- Ask by email: to delete a sign-in record left after you no longer belong to any account, to delete only the data received from Google or Meta or the feedback you sent from the phone app, or if you cannot use the app, contact us at the details above. We delete it after checking your request and tell you when it is done.
Use of processors
We use the processors below. Our contracts with them do not allow them to use personal data for anything other than the work we give them.
| Processor | Work |
|---|---|
| Cloudflare, Inc. | Servers, databases, and file storage; storing and totaling usage events; sending sign-in code and alert emails; forwarding support emails; passing Ask requests to AI companies |
| Oracle Corporation | Relaying requests through a server in Tokyo to our origin servers so the site opens quickly in Korea (nothing is stored) |
| 650 Industries, Inc. | Sending phone app notifications (passed to the Apple and Google notification services below) |
| Apple Inc. | Delivering iPhone notifications |
| Google LLC | Delivering Android notifications |
| Anthropic, PBC | Answering in Ask |
| OpenAI, L.L.C. | Answering in Ask (when Anthropic cannot be reached) |
| OpenRouter, Inc. | Passing Ask requests to AI companies (when other routes are blocked) |
| NAVER Corp. | Support email inbox |
Web push notifications are delivered through your browser's push service (Apple, Google, Mozilla, Microsoft). The notification content is encrypted, so those companies cannot read it. The title and text of phone app notifications reach your device through the notification companies above.
International transfers
To provide the service, we need to send personal data abroad to be stored and processed as below (Personal Information Protection Act, Article 28-8(1)3).
| Recipient (contact) | Country | Data | When and how | Purpose | Period |
|---|---|---|---|---|---|
| Cloudflare, Inc. (https://www.cloudflare.com/privacypolicy/) | United States (servers worldwide) | All data under "What we collect" | Over the network each time you use the service | Servers, storage, sending email, passing Ask requests | Same as "Retention periods" |
| Oracle Corporation (https://www.oracle.com/legal/privacy/services-privacy-policy/) | Japan (Tokyo server) | Requests to allob.app | Over the network each time you visit | Connection relay | Not stored |
| 650 Industries, Inc. (https://expo.dev/privacy) | United States | Phone app notification token, notification title and text | Over the network each time we send a notification | Sending phone app notifications | As set out in that company's policy |
| Apple Inc. (https://www.apple.com/legal/privacy/) | United States | iPhone notification token, notification title and text | Over the network each time we send a notification to an iPhone | Delivering notifications (Apple Push Notification service) | As set out in that company's policy |
| Google LLC (https://firebase.google.com/support/privacy) | United States | Android notification token and app installation details, notification title and text | Over the network when you turn on notifications on Android and each time we send one | Delivering notifications (Google Firebase Cloud Messaging) | As set out in that company's policy |
| Anthropic, PBC (https://www.anthropic.com/legal/privacy) | United States | Ask questions, attached photos, earlier questions and answers in the same conversation, and the account data needed to answer (fields such as people's names and emails are removed) | Over the network each time you ask | Answering in Ask | Not used for training; deleted after the period that company sets for abuse checks |
| OpenAI, L.L.C. (https://openai.com/policies/privacy-policy/) | United States | Ask questions, attached photos, earlier questions and answers in the same conversation, and the account data needed to answer (fields such as people's names and emails are removed) | Over the network each time you ask, when Anthropic cannot be reached | Answering in Ask | Not used for training; deleted after the period that company sets for abuse checks |
| OpenRouter, Inc. (https://openrouter.ai/privacy) | United States | Ask questions, attached photos, earlier questions and answers in the same conversation, and the account data needed to answer (fields such as people's names and emails are removed) | Over the network each time you ask, when other routes are blocked | Passing Ask requests to AI companies | Not used for training; deleted after the period that company sets for abuse checks |
If you do not want your data transferred abroad, you can delete your account and stop using the service. If you do not turn on phone app notifications, nothing is sent to the notification companies, and if you do not use Ask, nothing is sent to the AI companies. We cannot provide the service without the other transfers.
Ask and AI
Ask is a feature where AI answers the questions you ask in the phone app. To make an answer, we send the following to AI companies.
- What we send: your question, attached photos, earlier questions and answers in the same conversation, and the account data read to answer it (such as sales totals, metrics, ads, social posts and engagement, review text, and change records). Fields such as people's names, emails, and device identifiers are removed before sending.
- Who receives it: we send it first to Anthropic, PBC (United States), and only when that cannot be reached to OpenAI, L.L.C. (United States). Requests to OpenAI go through Cloudflare, Inc., and when a direct route is blocked, OpenRouter, Inc. passes the request on to the same company.
- Training and storage: under their contract terms, the AI companies use what they receive only to make the answer and do not use it to train models. The services that pass requests on are set not to send them to companies that use them for training. The AI companies keep requests for the period their policies set for abuse checks and then delete them.
- Storage in allob: Ask conversations are kept for 90 days after the last question and then deleted, and you can delete them right away from the conversation list.
- Saying no: if you do not use Ask, nothing is sent to AI companies. Before your first question, the phone app asks for your consent to send, and you can withdraw it at any time in the More tab. This consent is a check before sending, not a legal basis; the legal basis is performance of a contract, as set out in “Purposes and legal bases” above. You can keep using the other features without Ask.
Children
allob is a service for adults who run a business, and only people aged 19 or older in Korea (18 or older elsewhere) may use it. We do not collect personal data from children under 14, and we do not show targeted advertising to children.
Your rights
You can ask to access, correct, delete, or stop processing your personal data. A legal representative or someone you authorize can also make a request.
- Access: you can see your account, business information, connections, and records in the app. For anything else, contact us at the details above.
- Correction: edit your business information on the My business screen.
- Deletion: use Account settings › Delete account or "Disconnect" on the Connections screen, or contact us at the details above.
- Stopping processing: contact us at the details above.
We respond within 10 days of receiving a request, as required by Article 41 of the Enforcement Decree of the Personal Information Protection Act.
Security
- All connections are encrypted in transit.
- Connection tokens, API keys, and full business addresses are stored encrypted with a separate key for each account.
- Vault items are encrypted on your device, so even we cannot open them.
- The phone app keeps sign-in details in the device's secure storage, and approvals are accepted only when signed with a secret opened by Face ID, fingerprint, or screen lock.
- Sign-in codes work only for a short time, and we limit sign-in requests and code attempts.
- Only we can handle account data, and important actions in an account are recorded.
Complaints and remedies
If you need advice or a remedy for a privacy violation, you can contact the organizations below.
- Personal Information Dispute Mediation Committee: 1833-6972, https://www.kopico.go.kr
- Personal Information Infringement Report Center: 118, https://privacy.kisa.or.kr
- Supreme Prosecutors' Office: 1301, https://www.spo.go.kr
- Korean National Police Agency: 182, https://ecrm.police.go.kr
Changes to this policy
This policy is effective 2026-11-05. This version adds feedback sent from the phone app and phone app error records, and removes jsDelivr as a recipient because the docs pages now load their fonts from allob.app itself. If we change it, we will post the changes and the effective date on this page before they take effect.
Language
This document was originally written in Korean. Translations are provided for convenience. If they differ, the original prevails, unless the law of the country where you live says otherwise.