Privacy Policy
Published and effective: August 25, 2026
BuddyStudy processes only the data needed to provide the Service and does not sell personal data. The free public feed may show non-personalized native ads; paid memberships receive an ad-free public feed.
1. Controller and scope
The BuddyStudy Operator (the “Operator”) controls personal data processed through the BuddyStudy iOS app, APIs, notifications, public questions, and related web pages. Public questions can be read without signing in. Personal learning records, statistics, comments, likes, profiles, and notification sync may require an account or device registration.
2. Purposes
- Email, Google, or Apple sign-in, device registration, sessions, and account security
- Study trees, question generation, drafts, AI grading and feedback, translations, records, and statistics
- Notifications, public questions, comments, likes, reports, user blocking, feedback, and profiles
- Quotas, terms acceptance, preferences, App Store subscriptions, and membership fulfillment
- Free public-feed ad delivery, frequency limits, invalid-click prevention, and aggregate measurement
- Reliability, security, abuse prevention, quality, and performance improvement
3. Data processed and collection methods
| Category | Data | When and where |
|---|---|---|
| Account and authentication | User ID, email, password hash, sign-in provider ID, account status, verification code, session expiry | When account features are used · MySQL/Redis |
| Device and notifications | Device ID, hashed client credential, APNs token/environment, platform, app version, language, time zone, preferences | Registration and notifications · MySQL |
| Profile and learning | Display name, bio, pixel character, sharing setting, studies/topics, hierarchy, difficulty, schedule, questions, hints, drafts/submitted answers, scores, feedback, translations, records, statistics, quota usage | When those features are used · MySQL and on-device drafts/cache |
| Community | Sharing state, comments, likes, views, reports, user-block relationships and times, feedback | When those features are used · MySQL |
| Terms and subscriptions | Document/version/action/time/IP/app version, membership/product ID, App Account Token, transaction IDs, environment, renewal/expiration/cancellation/refund state, amount/currency, RevenueCat user/event ID | Consent, purchase, or restore · MySQL, Apple, RevenueCat |
| Ad delivery | Random slot ID, public-feed placement, internal user ID when signed in, slot/last-delivery time, UTC daily count, provider, AdMob impression/click time, first-party selection/impression/open/not-interested history | Eligible free public-feed use · MySQL |
| Operations, analytics, diagnostics | Request/user ID, IP, path/status/time/error, app instance and device/OS/app metadata, screen/feature events, errors/stacks, masked error-session replay | Service use or errors · Loki, Firebase, Sentry |
The Service does not intentionally collect government identifiers, health information, biometrics, or other sensitive data. Apple processes payment-card, bank-account, and Apple ID payment credentials; BuddyStudy and RevenueCat do not store them directly. Data comes from app input, identity providers, API requests, APNs, and SDK automatic collection. Passwords, tokens, and secrets are masked in logs.
4. Public content
When sharing is enabled, questions, topic, difficulty, creation/answer times, score, view/like/comment counts, comments, and public profiles may be visible to others. Content from a blocked user is hidden from the blocker, but the block relationship is not public. Drafts, private answers, emails, credentials, APNs tokens, device IDs, and internal logs are not public.
5. Native ads and privacy choices
When a signed-out or TIER1 free user opens Home's first unfiltered public-feed page, server policy may deliver at most one native-ad slot. Search, liked questions, later pages, and valid TIER2 or TIER3 paid access receive no slot. Ads are also omitted when entitlement cannot be resolved safely.
On each eligible app launch, Google User Messaging Platform (UMP) consent information is refreshed and any required form is shown. Google Mobile Ads starts only after the current-launch refresh and consent gathering succeed and UMP allows ad requests. When the IAB TCF signal says European regulations apply, Purpose 1 consent for storing or accessing device information is also required; applicable US-state decisions are carried by the IAB Global Privacy Platform (GPP) signal written by UMP. Settings exposes a privacy-options entry when UMP permits reopening it. If European Purpose 1 is denied or unknown, regional evidence is missing, a UMP refresh or form fails, an ad fails, inventory is unavailable, or loading times out, BuddyStudy does not request Google Limited Ads and may request one existing first-party fallback.
For ad delivery, Google AdMob may process IP-derived coarse location, app- or developer-scoped device identifiers, advertising data and interactions such as impressions/clicks, and crash, performance, or other diagnostic data. The Operator configures all requests for teen-rated, non-personalized advertising and disables publisher first-party ID and Google Mobile Ads SDK crash reporting. BuddyStudy does not request ATT permission, use IDFA, personalize ads, or track users across apps. It does not put BuddyStudy user/device IDs, email, search terms, study topics, questions, answers, content URLs, or keywords into ad requests. The initial integration contains no mediation-partner SDKs.
SDK-confirmed AdMob impressions and clicks are also recorded idempotently by the BuddyStudy server with the random slot ID. These records support daily caps, minimum intervals, aggregate reporting, and abuse prevention. BuddyStudy does not manually infer viewport impressions and does not auto-refresh ads.
6. Retention
| Data | Retention |
|---|---|
| Account, profile, learning, community | Until item deletion or account withdrawal |
| User-block relationships | Until unblock or either account is deleted |
| Ad slots, delivery state, event history | Cascade-deleted with the account; anonymous records retained only as operationally necessary and used for rolling 30-day aggregates |
| Verification code | Three minutes or until verification |
| Device/APNs data | Until deregistration, withdrawal, or invalidation |
| Terms and transactions | Until withdrawal; dispute, refund, or legally required records are segregated for the applicable period |
| Operational logs / backups | Seven days / up to 14 days |
| Google and Sentry data | Per Operator settings and each provider's policy |
7. Processors and international transfers
The Operator does not sell personal data. Providers include AWS (Seoul: API, databases, backup), Cloudflare (global: DNS, TLS, security), OpenAI (United States and other locations: questions, grading, translation), Apple and APNs (United States and other locations: sign-in, payment, push), RevenueCat (United States and other locations: subscriptions), Google (United States and other locations: sign-in, email, Firebase, Remote Config, UMP, AdMob), and Functional Software/Sentry (United States and other locations: diagnostics). Necessary data is transferred using encrypted transport when the related feature is used and is protected under provider policies and contracts. Declining external processing may limit the corresponding sign-in, AI, push, subscription, analytics, diagnostic, or ad-choice feature.
8. Analytics and diagnostics
Firebase Analytics receives only coarse screen and feature events, without user IDs, email, study content, comments, tokens, or request IDs. Firebase Remote Config retrieves update and maintenance policy. Sentry is used only for error and fatal events; ordinary replay upload is 0%, and text/images in eligible error sessions are masked. Google Mobile Ads SDK crash reporting is disabled.
9. AI and automated processing
Questions, translations, scores, and feedback are generated automatically as study aids and do not make legal or similarly significant decisions. Ad-slot position and frequency are automatically determined by operational policy, without profiling based on sensitive study content.
10. Your rights
You can review, correct, or delete profile data, sharing settings, notification preferences, optional consents, learning records, and your account in the app, and can block another user. When available, Settings lets you reopen UMP ad privacy choices. Access, correction, deletion, restriction, withdrawal, and unblock requests may also be emailed below; identity verification may be required. Subscription change, cancellation, refund, and restore start from Membership and Billing using Apple or RevenueCat interfaces.
11. Deletion
Account withdrawal immediately disables access and sessions. A recoverable asynchronous process removes profiles, learning and community data, block relationships, notifications, consent records, device links, and user-owned ad slots, delivery state, and event history from the active database. Legally required transaction records are segregated and deleted after their period. Backups are not restored for ordinary use and expire within 14 days.
12. Security
- TLS, password hashing, managed secrets, and least-privilege access
- Administrator authentication, network protection, credential masking, and audit logs
- Database constraints, transactional locking, idempotent event handling, and backups
- Masked error replays and minimized ad-request data
13. Children
BuddyStudy is not directed to children under 14. Teen treatment applies to every ad request, but BuddyStudy does not create a separate age gate or guess the UMP “under the age of consent” flag. Contact us if a child's data may have been processed.
14. Contact, complaints, and changes
Privacy contact: BuddyStudy Operator · ghkdqhrbals@gmail.com
Korea Internet & Security Agency Privacy Portal: privacy.kisa.or.kr / 118 · Personal Information Dispute Mediation Committee: www.kopico.go.kr / 1833-6972
Updates show publication and effective dates; material changes are announced separately and renewed consent is requested when required. This version adds free public-feed native ads, Google UMP/AdMob processing, ad privacy choices, and the paid ad-free benefit.