Get the app
Back to home

Oa Privacy Policy

Published and effective: October 22, 2026

Designbase (the “Operator”) explains how personal information is processed in the Oa mobile app and official website (https://oabebe.com) and how individuals may exercise their rights. Website visits, on-device records, account synchronization and family sharing have different processing scopes.

1. Operator and Privacy Officer

  • Operator: Designbase
  • Representative and Privacy Officer: Shin YeonSeok / Representative
  • Business registration number: 434-03-02686
  • Registered address: 경기도 용인시 수지구 상현로 5, 4층 402-33호 (4F, Unit 402-33, 5 Sanghyeon-ro, Suji-gu, Yongin-si, Gyeonggi-do, Republic of Korea)
  • Telephone: 0507-0178-2431
  • Inquiries and rights requests: contact@designbase.co.kr

2. Scope and Collection Methods

This Policy covers mobile records, accounts, synchronization, family sharing, advertising, website operations and inquiries. The public website does not provide web sign-in or childcare record entry. Community features are outside the current public launch scope; rights requests concerning test content may also be submitted to support.

Information comes from user entry and photo selection, supported authentication providers, and records and technical requests generated during feature use. Local records can be used without signing in, but advertising, notifications and external resources may still involve network communication.

3. Purposes and Categories

Accounts and authentication

Supported sign-in methods, including Google where available, provide account identifiers, email and any supplied name, profile metadata and photo URL. Login sessions are used for account identification, security and synchronization. Information received depends on provider settings and permissions. Linked methods can be checked in account settings. Passwords or national identification numbers are not required childcare record fields.

Processing of members’ own accounts relies on the applicable grounds for entering into and performing a service contract. This does not automatically extend to all processing of the child’s information entered by a member.

Child profiles and daily records

The app processes a child’s name, birth date or due date and birth status; optional sex, birth time, photograph and time zone; and formula or preparation-device settings. Selected record features may include feeding type, time, volume and breastfeeding/pumping duration, sleep, diapers, bathing, activities and milestones, foods, ingredients and quantities, care reminders and notes. Child and author identifiers, creation, modification and deletion-marker times and synchronization metadata support record management.

Not every item is mandatory. Required fields depend on the selected record and are shown in its entry screen. Optional data is processed when entered or enabled. Records may produce totals, statistics, growth comparisons, summaries, weekly reports, badges and supporting record references.

Sensitive health information

Blood type, growth measurements, temperature, disease, treatment and medication notes and records indicating health may be sensitive health information depending on content and purpose. Consent-based processing of sensitive information requires consent distinct from general personal information. Required legal representative procedures also apply to children under 14.

The grounds for child data processing, legal representative consent and verification, sensitive information and family disclosure are distinct. Reading this Policy, selecting a caregiver relationship or accepting a family invitation is not treated as completion of every required consent or verification.

Family connections and shared records

Invitation codes/links, account identifiers and emails, relationships, roles, permissions and connection/disconnection information support invitations and access control. Connected family accounts may see the child profile, resized photo, childcare records and family account emails/relationships within assigned permissions. Viewing, editing records and managing family members depend on the role.

Shared records may contain health information. Check recipients and permissions before sharing, and do not enter information you do not want shared in a shared profile. Personal recording remains available without family sharing. Sharing settings and rights requests are available through family settings and support.

Notifications, speech and optional tools

Remote notifications may process push tokens, installation identifiers, platform/environment, notification permission, time zone, language and delivery/error status. A notification can contain a child’s name or reminder text; lock-screen display can be managed in device settings.

Speech entry uses microphone and speech-recognition permissions. On-device recognition is preferred where supported; an optional online retry may send speech to the operating system’s speech service. Recognized text becomes part of a record if saved. Not all speech recognition is guaranteed to remain on the device.

Experimental image-analysis features requiring external transmission have feature-specific notices and choices. Ordinary statistics and summaries do not, merely by existing, mean that all records are sent to an external generative AI service.

4. Local Storage and Synchronization

Records are stored locally first. After account connection and applicable consent/permission steps, eligible profiles and records synchronize with the server. Excluded prenatal preparation details and practice records are distinguished from synchronized data.

Original profile photos may remain in the app’s device files. A 320×320 JPEG thumbnail synchronizes with the child profile. Account sessions use secure storage; this does not mean all childcare records are separately encrypted in secure storage. App storage, shared widget storage and server copies may occupy different locations.

Signing out does not delete local records or close the account. App removal, reset or device failure can cause local data loss, while operating-system backups may retain copies. Server account closure does not instantly erase all information on offline devices.

5. Advertising and Affiliate Information

The app may display Google AdMob ads. Native ad requests currently specify non-personalized advertising and do not directly attach child names, account identifiers, childcare records, child age, keywords or location. Non-personalized advertising does not mean no personal information is processed.

Google and businesses involved in ad delivery may process IP addresses, app/device information, available identifiers, ad impressions/interactions and diagnostics for delivery, measurement and fraud prevention. Actual categories depend on operating system, SDK, permissions, consent and provider settings. See Google advertising privacy information. Where a consent screen appears, its purposes, partner list and choices can be reviewed.

The app checks UMP request eligibility before requesting ads. Advertising privacy settings provide the SDK-required choice screen when applicable. Operating-system permissions and tracking settings can also be managed on the device. Ad privacy choices are separate from basic childcare recording, and processing not permitted by the choice is not performed.

Where affiliate placements are active, impression/click measurement may process a persistent device identifier, account identifier when signed in, and product, placement, recommendation reason and child-age metadata. This is not treated as fully anonymous statistics. External sellers apply their own policies; Oa does not directly process those purchases or shipping.

Service notifications and promotional email/push messages are distinguished. Installation, a web visit, an ordinary inquiry or operating-system notification permission is not promotional-message consent.

6. Website and Inquiries

Website requests may include IP addresses, URLs and access times, browser/device headers, responses, errors and execution information for page delivery, security and failure handling. Invitation URLs may contain codes or tokens. Hosting execution logs are stored.

Inquiries are received through Google Workspace. Reply addresses, supplied names, contents, attachments, responses and minimum identity/authority verification information are processed for the request, under the applicable contractual need or legal obligations to handle privacy rights. Do not send passwords, national identification numbers or unnecessary children’s medical documents.

7. Processing Providers and External Services

  • Supabase: authentication, server storage/synchronization, family permissions and notification-related processing. The current primary database is in Seoul. See Supabase privacy information and its subprocessor list.
  • Cloudflare, Inc.: website hosting, content delivery, security and request/execution logs. See Cloudflare’s privacy policy.
  • Google Workspace provider and processors under the applicable agreement: receiving, transmitting and storing inquiry emails/attachments. See Google’s Data Processing Addendum.
  • Expo and push delivery providers: token/message delivery and app updates, with APNs or FCM delivery depending on the platform. See Expo’s privacy policy.
  • Google authentication/advertising and operating-system providers: their processing relationships and policies apply to authentication, ads and selected device services. Not every external service is classified as a processor acting only for the Operator.
  • jsDelivr and similar resource providers: IP and request information may accompany font/icon delivery. See jsDelivr’s privacy policy.

The Operator limits processing to business needs and manages access, retention and deletion. Independent processing by providers under their own purposes and grounds is distinguished from outsourced processing.

8. Family Disclosure and Overseas Processing

Individually connected family accounts receive the sharing data described in Section 3 for joint childcare recording within assigned permissions. Disconnection limits subsequent access; it cannot instantly retrieve copies already saved or erase offline devices. Child photographs and records are not arbitrarily disclosed or sold as advertising material without a lawful basis.

A Seoul primary database does not guarantee domestic-only backups, logs, support or external services. Authentication, ads, push, hosting, email and external resources may be processed in the United States and other countries where providers/subprocessors operate. Categories, timing and methods correspond to authentication information, synchronization data, ad requests, messages/tokens, web requests and emails transmitted through encrypted networks and related delivery systems during feature use.

Overseas disclosure, outsourced processing and storage are distinguished by the actual relationship and applicable grounds. Transfers requiring separate consent are subject to that procedure; reading this Policy is not blanket transfer consent. Provider locations, contacts and subprocessors can be checked in the notices above. Verification, objections and suspension requests may be sent to the Privacy Officer. Restrictions may prevent the related account, ad, remote notification or email service; local recording has a separate scope.

9. Retention and Destruction

  • Accounts, server profiles and records: while account use and the relevant storage/sharing purpose continue. Once unnecessary or following a lawful deletion request, destruction is handled without undue delay except for legally necessary preservation. Shared records require checking the requester’s, child’s and other contributors’ rights and explaining the scope.
  • Local records/photos: may remain until deleted by the user or device storage is cleared; signing out alone does not remove them. Operating-system backups and shared widget copies must be distinguished.
  • Invitations/family administration: while needed for invitations, relationships and access management. A 24-hour invitation expiry or disappearance from a list is not permanent deletion of all associated history.
  • Inquiries/rights requests: until resolution. Information necessary for an ongoing dispute or legal preservation obligation is separated and destroyed when that reason ends.
  • Consent/security evidence: limited to verifying choices, lawful processing and related duties. Entire childcare histories are not retained indefinitely without purpose as evidence.
  • Ads, notifications, affiliate and service logs: for feature delivery, delivery status, errors, security and measurement, within applicable provider retention policies. Cloudflare describes default execution-log retention of three days for Free and seven days for Paid, subject to the actual plan/settings. Provider retention settings can also be queried through support.

Unnecessary electronic information is deleted using methods intended to make recovery or reproduction difficult; paper material, if any, is shredded or equivalently destroyed. Deletion markers, trash and backup expiry differ. A deletion response explains targets, completed scope and lawful preservation reasons. Instantaneous deletion of every backup or copy held by others is not guaranteed. Payment/shipping retention periods are not applied indiscriminately to all free childcare records.

10. Rights and Account Closure

Access, correction/deletion, suspension, withdrawal, account closure and other applicable statutory rights may be requested at contact@designbase.co.kr or 0507-0178-2431. Available record-editing/deletion and family settings can also be used.

The Operator verifies identity, legal representation and authority proportionately and communicates results under statutory procedures and deadlines. Lawful restrictions and objection routes are explained. A family role label alone does not prove legal representation. Identification documents or medical records need not be posted publicly.

Device reset, sign-out, family disconnection and account/server deletion have different effects. Specify the information concerned. Offline copies may require separate local removal even after remote access is revoked.

11. Permissions and Safeguards

Photo selection, speech/microphone and notifications use permissions when needed for the feature. Device settings can change them; refusal may restrict that feature without blocking unrelated basic recording.

Safeguards include HTTPS, secure session storage and server access restrictions based on authentication/family roles. This does not guarantee encryption of every local file or perfect security in all environments. Privacy issues may be reported to the Privacy Officer.

12. Remedies and Policy Changes

External remedies include the KISA Privacy Infringement Report Center, Personal Information Dispute Mediation Committee and Privacy Portal.

Changes to processing or law are announced with their effective dates in the app or website, with separate notice/consent where required. Publishing or displaying a revised Policy does not change historical consent records into new consent.