OurlogLegal · v1

Ourlog · Privacy

Privacy Policy

This policy explains what Ourlog stores, what it deliberately does not collect, and how saved memories are processed during internal testing.

Last updated
July 9, 2026
Status
Internal testing and pre-release
Contact
hello.ourlog@outlook.kr

01Overview

Ourlog, also called 아워로그, is a mobile relationship-memory app. The app helps users save things they explicitly want to remember for a relationship, then later recommends from those saved memories.

Ourlog is not a generic discovery app. In v1, recommendations are based only on memories the user saved.

02Data We Collect

Ourlog collects and stores data that users explicitly provide or create in the app:

  • Account data: authentication identifiers such as email address and Supabase user ID.
  • Relationship labels: private labels such as 여자친구, 친구, 가족, 혼자, and future user-created labels.
  • Saved memories: text, source URLs, source type, selected relationship, title, description, status, and timestamps.
  • Shared content metadata: user-shared text or URL, URL domain, Open Graph title, description, and image when available.
  • AI-generated memory fields: category, area, intent type, summary, confidence, and related structured fields.
  • Recommendation records: selected relationship, candidate and recommended memory IDs, reasons, status, model name, and usage or cost metadata when available.
  • Operational records: parse job status, recommendation status, error codes, and timestamps needed to operate and debug the service.

03Data We Do Not Collect in v1

Ourlog does not collect the following in v1:

  • Raw KakaoTalk conversation history.
  • Full contacts list.
  • Location history.
  • Full photo library.
  • Full Instagram saved list or other external saved-list data.
  • External place-search results that the user did not save.
  • Payment, reservation, or calendar data.

Ourlog only saves links, text, and relationship labels that the user explicitly enters or shares into the app.

04How We Use Data

We use collected data to:

  • Authenticate users and keep their sessions active.
  • Save, display, update, complete, and archive relationship-scoped memories.
  • Parse user-saved text or links into structured MemoryItem fields.
  • Recommend from already-saved pending memories for a selected relationship.
  • Record recommendation and AI usage logs for reliability, debugging, and cost control.
  • Protect user data through ownership checks, Row Level Security, and server-side validation.

We do not use saved memories to create unrelated external recommendations in v1.

05AI Processing

Ourlog uses OpenAI API services from Supabase Edge Functions for two v1 features:

  • Memory parsing: converting user-saved text or shared link metadata into structured MemoryItem fields.
  • Recommendation reranking: choosing up to three recommendations from candidate MemoryItems that already exist in the user's selected relationship.

The mobile app does not contain the OpenAI API key. OpenAI requests are made server-side.

Ourlog does not send full HTML pages to OpenAI. The parser sends only minimal metadata such as source URL, shared text, domain, Open Graph title, description, and image when available.

Recommendation AI must choose only from provided MemoryItem candidates. It must not invent new places, activities, or external candidates.

06Service Providers

Ourlog uses third-party service providers to operate the app:

  • Supabase: authentication, Postgres database, Row Level Security, and Edge Functions.
  • OpenAI: server-side AI parsing and recommendation reranking.
  • Expo, Apple, and Google: app builds, internal testing, installation, and distribution workflows.

These providers may process data as needed to provide their services.

07Data Sharing

Ourlog does not sell user data.

Ourlog does not share saved memories with other Ourlog users in v1. A relationship is a private user label, not a shared account.

Data may be processed by the service providers listed above to operate the app. Data may also be disclosed if required by law or needed to protect the security and integrity of the service.

08Data Retention

Ourlog retains account data, relationship labels, saved memories, parse jobs, and recommendation logs while the account is active or as needed to operate the service.

Users can mark memories as done or archive them. These actions change app-visible status but may not immediately delete underlying records. Internal testing data may be cleaned up before public release.

09Deletion Requests

Users can request account or data deletion by contacting hello.ourlog@outlook.kr.

Deletion requests may include:

  • Account deletion.
  • Deletion of saved memories.
  • Deletion of relationship labels.
  • Removal from internal testing.

10Security

Ourlog's mobile app uses only public Supabase environment variables. Server-only secrets, including OpenAI API keys and Supabase service role keys, remain in secure server-side environments.

User data is protected through Supabase Auth, Row Level Security, and Edge Function ownership checks. No system can guarantee perfect security. Internal testers should avoid saving highly sensitive personal information during testing.

11Children

Ourlog v1 internal testing is not intended for children. Internal testers should be adults or otherwise authorized by the test owner.

12International Use

Ourlog may use service providers that process data in regions outside the user's country. Internal testing should not be treated as a final public international data-transfer review.

13Changes

This privacy policy may change as Ourlog moves from internal testing toward public release. Material changes will be reflected at this URL.

14Contact

Questions, support requests, and deletion requests can be sent to hello.ourlog@outlook.kr.