Privacy Policy

The Company processes personal information only for the following purposes and does not use it for any purpose other than those stated.

• Providing genogram creation and editing features (including auto layout calculation)
• Preventing misuse of the auto layout feature by filtering out automated requests
• Identifying users through Auruda account login and enabling the use of multiple genograms
• Storing logged-in users' genograms and synchronizing them across devices
• Sharing genograms on a view-only basis with members designated by the creator
• Integration with Auruda Verbatim under the same account (storing genograms created by Auruda Verbatim and continuing to edit them, and linking genograms to clients)
• Diagnosing errors and reproducing auto layout errors
• Analyzing usage statistics to improve service quality and usability (for logged-in users, including usage flows across multiple devices and Auruda services)

Account information (when logged in) — the email address, name, profile image and account identifier provided when logging in to Auruda through Google, Naver or Apple social login. Login is handled by the Auruda authentication server. The Service uses this information for member identification and keeping users logged in, display on screen, storing and sharing genograms, and usage statistics (member ID only; see “Usage statistics” below), and of the account information it records only the member ID in server error logs. It is not used for marketing or provided to third parties (Section 5). If a user chooses “Hide My Email” when logging in with Apple, the Company receives only the relay address issued by Apple.

Genogram data (user content) — content the user writes, such as persons, relationships and notes, and the genogram name and layout (coordinates). When logged in, this content is kept on the Company’s servers, and the genogram name, body and layout are stored encrypted with AES-256-GCM. Management values such as creation and modification times, save count, client link value and sharing relationships are not encrypted. The copy kept on the user’s device is encrypted with AES-256-GCM using a key generated on the device. However, if the browser does not support the encryption features (Web Crypto, IndexedDB), it is stored unencrypted.

Auto layout — when a genogram is arranged automatically (when a genogram is opened, when it is edited while auto layout is on, and when the layout button is pressed), the persons and relationships on screen and their content (values the user entered, such as names, ages, dates and notes), together with shape sizes and coordinates, are sent to the Service’s server for calculation, and only the result (coordinates and sizes) is returned. This is sent regardless of whether the user is logged in, and nothing is stored once the calculation is done. Even with auto layout turned off, it is sent when a genogram is opened in order to recalculate shape sizes. The apps (iOS, Android) send it in the same way.

Automated request detection — to check whether an auto layout request comes from a real browser, the detection feature (BotID) of the hosting provider (Vercel) runs a script on the page that examines characteristics of the browser and device, attaches the result to the request, and Vercel makes the determination. If the determination is difficult, one more detection script may be loaded for a closer examination. The Company uses the detection result only to decide whether to accept that request and to monitor abuse, and does not store cookies on the device for this purpose. If too many auto layout requests come from the same IP address within a short time, they are refused for a while.

Device attestation in the apps — auto layout requests from the apps (iOS, Android) are verified by device attestation instead of the detection script. The iOS app creates a key on the device with Apple App Attest, registers it once at first, and signs each later request with that key. The Company’s server only signs the public key received at registration and returns it to the app, and does not store it separately. The Android app obtains a Google Play Integrity token for each request and sends it along, and the Company’s server sends this token to Google to obtain a verdict on whether the app and device are genuine. The verdict is used only to decide whether to accept that request and is not stored.

Auruda Verbatim integration — when a user who uses Auruda Verbatim with the same account creates a client genogram in that service, the genogram appears in the Service’s genogram list as well. The processing that produces the content (extracting family and relationship information from session records) takes place in Auruda Verbatim and is governed by that service’s privacy policy. The Service stores the transferred genogram encrypted in the same way as other genograms and provides editing features. When Auruda Verbatim modifies a genogram automatically, one copy of the immediately preceding body is also kept encrypted so that the change can be undone. When Auruda Verbatim generates a genogram image, it calls the Service’s drawing feature, and the genogram body passes through the Service’s server at that time (it is not stored).

Client link — a genogram can be linked to a client registered in Auruda Verbatim. For this, the client list (pseudonym, counseling type, progress status, number of members) is retrieved and shown, and which client the genogram is linked to is stored on the server. Auruda Verbatim reads a linked genogram as that client’s genogram. When Auruda Verbatim redraws the genogram to reflect session records, it also sends the existing genogram content to an AI processor (Google Gemini). This processing is governed by Auruda Verbatim’s privacy policy. Clients are also registered in Auruda Verbatim.

Sharing — when a user shares a genogram by entering a member’s share code, that member can view the genogram. The member it is shared with sees the creator’s name, and the creator sees that member’s name (the share code is shown if there is no name). Users who have not been designated cannot view it, and the member it is shared with cannot edit or delete the content. Sharing can be revoked at any time, after which that member can no longer open the genogram.

AI features — the Service itself has no AI features, so the Service does not send genogram content to AI processors. As described under “Client link” above, when Auruda Verbatim redraws a genogram with AI, Auruda Verbatim sends that content.

Error information — when an error occurs on the Service’s screens or in its drawing feature, the following are sent to an error analysis service (Sentry): the error message (long messages are truncated), the code location where the error occurred, the browser and operating system type, language and time zone, the page address and the screen navigation history leading up to it, and network request records (request method, response code, and addresses with identifiers such as document numbers removed). Query parameters are removed from all addresses. The beginning of an error message may contain part of the genogram content that caused the error. Clicks and input, console logs, and the addresses of referring sites (Referer) are not sent, and the feature that sends usage status (sessions) when there are no errors is turned off. For errors on the Service’s server, only the request path with query parameters removed is recorded, and request headers, cookies and bodies are not sent. The setting that sends personal information by default is also turned off. If a problem such as overlapping persons is found in an auto layout result, the structure needed to reproduce it (relationship types, gender, shape markings such as death, adoption and pregnancy loss, and coordinates) is sent as well. Person names, notes, ages and dates are excluded, persons are replaced with numbers such as P1 and P2, and no account or genogram identifiers are attached. Because this reproduction data is sent by the Service’s server that calculated the auto layout, it cannot be blocked in the browser.

API server error information — when a server error occurs, the Auruda API server (the server that handles login checks, genogram storage and sharing) sends the error details, the request path and the member ID (if logged in) to Sentry.

Usage statistics — Google Analytics collects usage flows such as page views and screen navigation (including page addresses; links to genograms coming from Auruda Verbatim carry a document number), the device, browser and operating system type and screen size, approximate access location (country and city level), and the referral source. To distinguish return visits, a random identifier is stored in a cookie for each browser. Feature usage records are also sent (opening the editing screen; creating, saving, exporting as an image and copying a genogram; starting and completing login and the login method chosen; opening a genogram coming from Auruda Verbatim; and clicks on links to other Auruda services, with the link address minus its parameters). When logged in, the member ID (a value derived from the Auruda account number) is sent as well, to see the same user’s use across multiple devices and Auruda services together. It is not sent after logging out. Account information other than the member ID (such as name and email) and genogram content are not sent.

Access logs — when users access the Service, the IP address, browser information (User-Agent), and the requested address and time are recorded on the hosting provider’s servers.

Genogram data (server) — server copies of logged-in users’ genograms are kept while the account exists. When a user deletes a genogram, it immediately becomes unavailable, and it is permanently deleted 30 days after deletion (it is kept only for that period to pass the deletion on to other devices). If the user deletes their Auruda account, the genograms on the server, including those awaiting deletion and sharing settings, are destroyed immediately.

Genogram data (device) — remains on the device until the user deletes it. It disappears when browser data is deleted or the app is removed. Genograms created while not logged in cannot be recovered because the Company has no copy.

For auto layout requests, the genogram content is in server memory only during the calculation and is not stored. The Company does not store detection results separately. For requests that were blocked or that skipped detection, that fact is recorded in the server execution logs (Vercel) together with the access log, and request rate limiting and detection records follow Vercel’s retention settings.

Account information is kept while the Auruda account exists, and when the account is deleted it is destroyed without delay, except for items that must be retained under applicable laws.

Error information is kept and then deleted according to Sentry’s retention settings, usage statistics according to the Google Analytics property’s retention settings, and access logs according to Vercel’s retention settings. Quality-check images posted to Discord up to October 5, 2026 (see the change history) remain in the channel until they are cleaned up, and users may request their deletion (Section 11).

When the retention period ends or the purpose of processing has been achieved (including termination of the Service), the information is destroyed without delay.

• Genograms and account information on the server are deleted from the database. For deleted genograms, a cleanup job that runs once a day deletes those that are more than 30 days old.
• Copies remaining in the database records kept for disaster recovery disappear when their retention cycle ends.
• Genograms remaining on the device disappear when they are deleted in the Service or when browser data is cleared.

The Company does not provide or sell users’ personal information or genogram data to third parties and does not display advertising. The only exception is where laws specifically provide otherwise. Sharing under Section 2 is opened only to members the user designates and is not provision to third parties by the Company.

The Company entrusts the following tasks needed to operate the Service to providers outside Korea, and personal information is transferred to and stored outside Korea in the process. This is disclosed in this Policy as outsourcing and storage necessary to perform the service agreement (Article 28-8, Paragraph 1, Subparagraph 3 of the Personal Information Protection Act (Korea)). All transfers are made over the network (encrypted communication such as HTTPS).

How to refuse and the effect of refusal — usage statistics can be refused by the methods in Section 7, and refusing does not affect use of the Service. If transmission to error analysis (Sentry) is blocked with the browser’s tracking protection or an extension, the Service still works. Without logging in, genograms are not recorded in the database or in the request rate-limit records. Hosting (Vercel) is essential to providing the Service, so if it is refused the Service cannot be used. If automated request detection is blocked, for example by blocking scripts, auto layout cannot be used, but drawing and editing still work. There is no setting that stops auto layout requests from being sent; when offline, genograms are drawn without auto layout. Anonymous reproduction data from auto layout results is sent by the server and cannot be blocked in the browser. Users can request deletion of the quality-check images remaining on Discord through the contact in Section 11.

Google, Naver and Apple are not outsourcing recipients but login methods chosen by the user, and they provide account information to the Company only when the user chooses to log in. Each provider’s processing is governed by that provider’s privacy policy (Vercel, Databricks, Upstash, Google, Sentry, Discord).

The Company stores the following on users’ devices.

• auruda.sid (cookie) — keeps the login session. It is issued by the Auruda authentication server and created only when logged in. It is deleted on logout or account deletion.
• genogram-locale (cookie, local storage) — the display language the user chose. It is also used to send users who arrive at the first page to the address for the chosen language. It holds only a language code and does not track users. The cookie is kept for 1 year.
• _ga and cookies starting with _ga_ — Google Analytics usage statistics. They hold a random identifier that distinguishes return visits.
• genogram-mvp-v1 (local storage) — the device copy of genogram bodies and layouts, the recent genograms list, and login information (member ID and the name, email and profile image address for display). It is stored encrypted with AES-256-GCM (except where the browser does not support the encryption features; see Section 2).
• genogram-secure (IndexedDB) — the device key used for the encryption above. It is not sent off the device.
• genogram-tab-owner-v1 (local storage) — a tab identifier that keeps data from being overwritten when the same work is edited in several tabs at the same time.
• genogram-archive-cursor-v1 (local storage, when logged in) — the time of the last retrieval from the server and the account identifier. It is discarded when logging in with a different account.
• auruda.analytics.loginMethod (session storage) — the login method chosen when starting login (Google, Naver, Apple). When login completes, “login completed” is sent to usage statistics and the value is deleted. It disappears when the tab is closed.
• genogram-policy-notice-dismissed-until (local storage) — the time at which a revision notice closed with “Dismiss for today” is shown again.

Usage statistics can be refused through browser settings or the Google Analytics Opt-out Browser Add-on. Cookies and local storage can be deleted or blocked in browser settings, but if they are blocked, basic features such as staying logged in and keeping work will not work.

Users may exercise the following rights at any time, including through a legal representative or an authorized agent.

• Deleting genogram data — deleting a genogram in the Service deletes both the device copy and the server copy (the server copy is permanently deleted after 30 days)
• Deleting the Auruda account — available from “Delete account” in the account menu at the top right of the screen. It can also be requested from “Delete account” in the Auruda Verbatim app settings or through the contact in Section 11. Because the Auruda account is shared with other Auruda services such as Auruda Verbatim, deleting it also deletes the records in those services (such as Auruda Verbatim session records and clients), and the genograms and sharing settings on the server are destroyed immediately. Genogram copies remaining on this device are not erased, so delete them separately in the Service if needed
• Logging out — log out from the account menu at the top right of the screen
• Refusing the collection of usage statistics — by the methods in Section 7 above
• Requests for access, correction, deletion or suspension of processing — submitted through the contact in Section 11 below

• All communication is transmitted encrypted with TLS (HTTPS).
• Genograms stored on the device are encrypted with AES-256-GCM using a key generated on the device (except where the browser does not support the encryption features).
• Server copies store the genogram name, body and layout encrypted with AES-256-GCM, so their content cannot be read by viewing the database alone without the encryption key.
• The encryption key for server copies is held only by the server and is managed separately from Auruda Verbatim. The server decrypts content with this key when handling save, retrieval and sharing requests.
• All retrieval and modification is limited to the scope of the logged-in account, so other people's genograms that have not been shared cannot be accessed.
• The login session cookie is issued as httpOnly so that scripts cannot read it.
• The number of genogram storage requests is limited per account to block abnormal bulk requests.
• Auto layout requests are checked to confirm that they come from a real browser, filtering out automated requests; the number of requests per IP address is limited; and the genogram content received is not stored after calculation.
• Error reports from the Service do not include clicks, input or console logs, and parameters and identifiers are removed from network records and addresses. Reproduction data for auto layout errors does not include person names, notes, ages or dates (Section 2).

The Service is intended mainly for psychological counseling practitioners and is not directed at children under the age of 14 as users. Where a user creates a genogram that includes minors in the course of counseling, the user is responsible for the lawful collection and use of that information, and the Company does not view its content unless necessary to operate the Service.

Officer: Chaesung Lim (General Development Manager)
Department: Auruda Operations Team
Email: privacy@auruda-j.com
Handling: replies within 7 business days on average

To report or seek advice on an infringement of personal information, users may contact the following agencies.

• Personal Information Dispute Mediation Committee: (no area code) 1833-6972 (www.kopico.go.kr)
• Personal Information Infringement Report Center: (no area code) 118 (privacy.kisa.or.kr)
• Supreme Prosecutors' Office: (no area code) 1301 (www.spo.go.kr)
• Korean National Police Agency: (no area code) 182 (ecrm.cyber.go.kr)

If this Policy changes, the change will be announced on this page at least 7 days before it takes effect. Important changes, such as adding outsourcing recipients or collecting new items, will be announced 30 days in advance, and consent will be obtained separately where required. The changes are recorded in the change history below.