Privacy policy
How records on your phone, information sent to external services, and contact details for testing are handled.
Prepared as of
1. Scope and operator
DamDam is currently an app under development, operated by an individual. No business registration has been completed. The public operator name will be added when confirmed. The email addresses for questions and rights requests are in section 8.
This draft covers the current app and free external testing. Round 0 will be shared directly with about 10 acquaintances. Round 1 is planned to recruit about 100 people through local promotion. Android testers receive an APK link; iPhone testers receive a TestFlight invitation link.
Paid services, payments and cloud accounts, sync or recovery that are not yet available will receive separate notices when offered. A development plan shown on a page is not a promise that the feature is available.
2. Information and purposes
| Information | Purpose and processing route |
|---|---|
| Email, device type, invitation and communication preferences | Delivering installation links, running the test and providing launch news you have agreed to receive. The email, device, launch-news choice and request time you submit in the homepage form are relayed through FormSubmit to the operator’s inbox; the operator sends invitations by hand. |
| Chat messages, replies, calendar, to-dos, documents, journal and memory | Storing and finding records on your phone and enabling contextual AI responses. Chat originals are also stored on your phone. |
| Photos, attachments and saved recordings | Stored on the device with records you choose or create. AI input, transcription and sharing can send relevant content to external services. |
| Microphone audio, transcripts and recognition hints | Dictation and file transcription. Some registered person names and user-entered place words may accompany audio to improve recognition. |
| Health, exercise, sleep and mood records | Displaying records you enter or import with permission. Content included in chat, relevant tools or sharing may also be processed externally. |
| Location, region, places, routes and search queries | Sent to the relevant services when requesting weather, place search, maps, directions or web research. |
| Random installation ID, app build, request type, model, token counts, audio duration, status and latency | Understanding usage, costs and errors. An operator can assign an alias to an installation ID to distinguish tester devices, so these records are not described as fully anonymous. |
| The sender address and content of enquiry emails, and text, images and device information you attach to support requests | Reproducing problems, providing support and replying. Please redact other people’s information and records you do not want to disclose. |
| Website access information | Hosting providers such as Cloudflare may process IP addresses and request information to deliver pages and maintain security. The site code does not add separate advertising trackers or visitor analytics. |
3. External services
What is sent depends on the feature, settings, permissions and chat context. Not every record is always sent, and not all processing happens only on your phone.
The relay forwards requests and records usage. The usage table does not contain raw chat or audio, but AI, speech processing and hosting access handling are separate routes.
| Service | Possible information and purpose |
|---|---|
| Cloudflare | Website hosting, relaying AI and search requests, usage storage, temporary storage for some file transcription, and delivery of encrypted shared files. |
| FormSubmit | Relays the homepage application form’s email, device, launch-news choice and request time to the operator’s inbox. App records and chats are not sent. |
| Cloudflare Email Routing | Relays enquiry emails sent to @damdam.day addresses and homepage application notices to the operator’s inbox. It is used only to forward them, not as a mailbox for keeping messages. |
| Resend | Sends the operator’s replies to enquiries from @damdam.day addresses. The recipient address and the reply content pass through this service. |
| OpenAI and Google | Chat and relevant records or images for the selected AI’s replies, summaries and memory processing. xAI or Anthropic may process requests when selected through settings such as developer options. |
| TypeSafe AI / Jev | User text, parts of recent conversations, sheet titles and column names for expression, feature routing, record suggestions and input decisions. These calls can happen separately from the main AI. |
| Soniox | Audio and recognition hints for live dictation, and recordings for file transcription. Live processing connects directly from the device; file transcription can use a relay or temporary file storage. |
| Exa, Kakao and Open-Meteo | Web research queries, place/map/route requests, and weather regions or coordinates, respectively. |
| Apple and Google health services, and COROS | Importing health and exercise records after connection and permission. Active connections and processing conditions must be checked against the actual test build. |
| Apple TestFlight | iPhone test distribution and Apple’s testing and feedback handling, also subject to Apple’s own notices. |
4. Provider retention and international processing
Using overseas AI, speech and hosting providers can involve processing outside Korea. Recipients, countries, transferred information, purposes, methods, timing, retention, refusal methods and consequences must be confirmed against actual agreements and settings before publication.
Provider training, retention and deletion rules differ by service and account configuration. We do not make a blanket promise that all providers retain nothing or exclude every input from training. Preparing this draft does not complete transfer consent screens or agreement review.
5. Health, mood, location and permissions
Health measurements, exercise, sleep, mood and private journal entries need particular care. Features may request access to health services, microphone, photos, location or device authentication. You can refuse or change unnecessary permissions in device settings; this can affect related features.
Turning off permission is different from deleting information already stored or transmitted. Notices, processing grounds and actual consent and withdrawal paths for health or mood content included in chat or sharing must be confirmed in the test build.
6. Retention and deletion
Contact details are intended to be retained for invitations, test operations and launch news you have agreed to receive. Ending a test alone does not trigger immediate deletion of an email still needed for launch news. Information is deleted when you withdraw or the communication purpose ends and it is no longer needed. Any legally required retention will be explained separately with its scope and basis.
Before collecting contact details, we explain the purposes, retention criteria, types of news and opt-out method, and check the relevant communication preferences.
Submitted application data passing through FormSubmit may be kept by that service for 30 days, according to its official documentation. That is the provider’s own fact, not a retention period set by DamDam. The operator cleans up application emails in the operator’s inbox when you ask to withdraw or the purpose ends.
| Category | Confirmed handling and outstanding checks |
|---|---|
| Records, chats and attachments on the phone | Managed in device storage. Caches, internal backups and shared copies after deletion need separate checks. Uninstalling or changing devices can lose records; complete app recovery is not guaranteed. |
| Recent chat recordings | Unsaved recent recordings are cleaned up under a default 10-minute temporary retention window. Save requests, processing grace periods and app execution can affect this. Recordings you ask to save remain as attachments. |
| Temporary file-transcription audio | Deletion of relay copies and provider files/results is requested after retrieving transcription. Cleanup after interruption or failed requests and operational retention remain to be checked; immediate complete deletion is not guaranteed. |
| Usage and operational records | Installation IDs and request metadata remain on the server. Actual retention, cleanup and ID-specific request handling must be confirmed before publication. |
| External provider records | Deleting device records and deleting provider records have different scopes. Notices will reflect the actual service, agreement and deletion facilities. |
8. Contact, rights and changes
Requests to access, correct, delete or restrict processing of your information, and to withdraw communication preferences, can be sent to privacy@damdam.day. Send installation, usage, bug-report and testing questions to support@damdam.day. The public operator name has not been decided yet and will be added to this document when confirmed.
Important changes will be announced in advance where possible. Urgent or unforeseen situations may require action first, followed by information about the changes and effects as soon as reasonably possible. No fixed advance-notice period is promised. Applicable legal requirements still apply.
Before publication
- Public operator name
- Retention criteria for enquiry emails
- Processing grounds, transfer notices, consent and withdrawal in the actual test build
- Provider agreements, processing countries, retention and international-transfer disclosures
- Operational retention and deletion of usage, error records and temporary audio
- Countries, age range and applicable safeguards for the first recruitment round