Privacy Policy

1. What we collect

Your email address, from Google or Apple when you sign in. Required to identify your account.

The nickname and bio you choose. Your nickname appears on your public posts and profile.

The books on your shelf, your reading state, your posts and comments, lounge membership, and reading-friend connections.

Photos and videos you attach to a post. They are stored with the same visibility as the post they belong to.

If you join the launch waiting list, the address you enter, where you entered it, and your language. It is not linked to an account and is used only to tell you we launched. Write to support@booktobee.com and we delete it.

2. What we do not collect

No location. The app holds no location permission.

No advertising identifier. The AD_ID permission is removed from the app. Internal tester builds show Google's test ads, which read no identifier used for personalisation. Before any real ad serves, this policy changes first.

No microphone or audio. That permission is removed.

No contacts, call logs, or messages.

No payment or financial data.

No exact date of birth. Where an age check is needed we keep only a coarse range and discard the input.

3. Photos taken by the camera

When you scan a book, the frame is processed on your device and deleted as soon as the barcode or text is read. It is never sent to our servers.

The only images that reach our storage are the ones you deliberately attach to a post.

4. Finding book information

If a book is not in our catalogue we send your search terms to Aladin, Google Books, and Open Library to find it.

Only the search terms are sent. Your account identifier, email, shelf, and location are not.

5. Visibility

Your nickname, bio, and public posts are visible to other readers.

Profile and shelf visibility are set separately, and are enforced on the server rather than hidden in the interface.

6. Retention and deletion

Data is kept while your account exists.

Deleting your account removes your profile, shelf, posts, comments, and uploaded media. You can start this in the app or by request on the web.

Safety records tied to reports may remain in a form that cannot identify you.

7. Processors

Supabase — database, authentication, file storage (Seoul, South Korea)

Google — sign-in and Firebase App Distribution during testing

Cloudflare — website delivery

Aladin, Google Books, Open Library — bibliographic lookup

8. Data that leaves Korea

Some of the processors above run outside Korea. Korean privacy law asks us to name who receives the data, in which country, what is sent, why, and for how long. Transfers happen at the moment you use the service, over encrypted connections.

Google LLC (United States) — sign-in, push notification delivery, app distribution during testing. Your email address and device push token. Kept until you delete your account or the arrangement ends.

Cloudflare, Inc. (United States) — website delivery. Your IP address and request details; access logs are discarded after a short period.

Google Books, Internet Archive Open Library (United States) — bibliographic lookup. Only the search term is sent, never your account identifier, email, or shelf.

You may refuse these transfers. Sign-in and push notifications run on them, so refusing limits those features or the service itself.

9. Privacy officer

Korean privacy law asks us to name the person accountable for how personal data is handled, and to publish how to reach them.

정성우, 마케팅본부 실장

yoonho@zoopiter.co.kr / 02-333-3140

10. Business details and contact

Jupiter Soft Inc. · CEO 명윤호

Business registration 105-87-76709

3F, 222 Seokchonhosu-ro, Songpa-gu, Seoul, Korea

support@booktobee.com · 02-333-3140