Privacy Policy
Version 2026-10-23 · Effective October 23, 2026
Who processes your information
The operator is 김현민 (Hyunmin Kim). Privacy officer: 김현민 (Hyunmin Kim), roy@thegram.one, +82 10-8000-2203. Use this email for privacy requests and general contact. The service is the vault.thegram.one web app and vault service; sign-in is at auth.thegram.one. Mac, iPhone, and iPad apps sign in to the same service. The server is in the Republic of Korea.
What we process, why, on what basis, and for how long
Every item below is processed because it is necessary to enter into and perform the service contract (Personal Information Protection Act (PIPA) Art. 15(1)(4)). Contract-necessary items are listed separately from consent-based items as required by PIPA Art. 22(3); there are currently no consent-based processing items.
| Information | Purpose | Basis | Retention |
|---|---|---|---|
| Email, name, profile picture if provided, sign-in method, sign-in account identifier | Identify and sign in | Contract necessity, PIPA Art. 15(1)(4) | Until account deletion |
| Display name and appearance settings | Show the app as set | Contract necessity, PIPA Art. 15(1)(4) | Until account deletion |
| Web sessions and desktop devices (hashed credentials, browser type, IP address) | Keep signed in, sign out other devices, protect the service | Contract necessity, PIPA Art. 15(1)(4) | Until ended or revoked, at most 30 days; ended after 7 days idle |
| Agreement record (agreed Terms and Disclaimer versions, privacy notice version acknowledged, time, time age check passed) | Prove what was agreed | Contract necessity, PIPA Art. 15(1)(4) | Until account deletion |
| Documents saved to vaults | Storage and sharing | Contract necessity, PIPA Art. 15(1)(4) | Until deleted or account deletion; deleted vaults remain in trash for 30 days |
| Connected Google Drive accounts (Google account email and name, encrypted refresh token) | Drive access chosen by you | Contract necessity, PIPA Art. 15(1)(4) | Until disconnected or account deletion |
| Working copies of vault and Drive documents kept on the server when an AI agent is connected (MCP) | Answer agent requests | Contract necessity, PIPA Art. 15(1)(4) | Erased on account deletion |
| Sign-in server records (sign-in time, IP address, browser information) | Detect misuse and protect accounts | Contract necessity, PIPA Art. 15(1)(4) | 90 days |
| Server request records (IP address, path, time) | Security and fault handling | Contract necessity, PIPA Art. 15(1)(4) | Not stored separately; removed when the server is redeployed or the log exceeds a set size |
Date of birth and age check
We ask for your date of birth once at sign-up only to confirm you are at least 14. We never store your date of birth; only the time the check passed is kept. If you are under 14, your account, everything entered, and vaults it owns are erased immediately without going to trash. Sign-in is blocked for 24 hours in that browser.
Unfinished sign-ups
If you choose “Leave without signing up,” the sign-in account and record are deleted immediately. Accounts that never finish sign-up and hold no vault, vault membership or Drive connection are deleted automatically once 7 days have passed. An account that already holds one of those is only signed out, so nothing it holds is lost; delete it in Settings › Account if you no longer want it.
Account deletion and destruction
You can delete your account at any time in Settings › Account › Delete account on the web, Mac, iPhone, or iPad. Vaults you own move to trash and are erased after 30 days; other members lose access. Your memberships in other vaults are removed. Google Drive connections are disconnected and their tokens revoked. Agent working copies are erased. Backups made before the deletion leave as newer archives replace them (see Backups).
Electronic records are deleted so they cannot be restored. Vault trash is purged after 30 days. Backups are not edited afterwards; deleted data leaves them only when the archive holding it is rotated out.
Backups
Vault data, including account records, vault documents, and Drive connection records, is copied once a day into an archive on a separate disk of the same server and, encrypted with a key only the operator holds, uploaded to the operator’s Google Drive (Google LLC, USA; Google data centers). We keep the latest 14 archives, counted by number, not by days. An archive is rotated out only after a newer one is published and uploaded, so when an upload or cleanup fails, older archives stay until the next successful run. Agent working copies are not backed up.
Processors and transfers abroad (PIPA Art. 28-8(1)(iii)(a))
Transfer abroad — Plus Five Five, Inc. (Resend), United States
Items: email address and sign-in code message. Country: United States. When and how: each time a code is emailed, our mail server (mail.thegram.one) relays it through Resend over an encrypted connection. Recipient: Plus Five Five, Inc. (Resend), privacy@resend.com. Purpose: deliver the sign-in code email. Retention: deleted under Resend’s retention once delivered. How to refuse and effect: avoid this transfer by signing in with Google or Apple; otherwise the code email cannot be delivered.
Transfer abroad — Google LLC, United States
Items: encrypted backup archives of vault data, including account records, vault documents, and Drive connection records. Country: United States (Google data centers). When and how: uploaded once a day over an encrypted connection; a day whose upload fails stays only on the server disk. Recipient: Google LLC, Google privacy contact form. Purpose: disaster recovery. Retention: the latest 14 archives by count; older archives can stay longer while uploads or cleanup fail. How to refuse and effect: this transfer cannot be refused separately; deleting your account removes its data from backups as newer archives replace the older ones.
No provision to third parties
We do not provide personal information to third parties except where the law requires. Google and Apple sign-in and Google Drive are services you connect to directly and are governed by those companies’ policies.
Security measures
We use HTTPS everywhere; store session and device tokens only as hashes; encrypt Drive refresh tokens and off-site backups; limit access to servers, logs, and the admin console to the operator; and use a strict Content-Security-Policy. We use no analytics, ad trackers, or session recording. Fonts and scripts are self-hosted.
Cookies and browser storage
| Name | Purpose and duration |
|---|---|
__Host-vault_session | Sign-in; up to 30 days |
vault_login | During sign-in; 15 minutes |
thegram_drive_state | While connecting Drive; 10 minutes |
vault_age_block | After an under-14 entry; 24 hours |
Your browser also keeps display settings and language, panel layout, titles of the last 8 opened documents, and folder permissions locally; these never reach the server. Blocking cookies prevents sign-in.
Sign-in codes and security notices come from noreply@thegram.one. We send no marketing email unless you ask for it. If we ever send marketing email, it will include one-click unsubscribe and a postal address; unsubscribe takes effect within 10 days.
Google Drive and Google API Limited Use
Drive access uses the drive.file scope per account. Google API Services User Data Policy, including Limited Use, applies to Google API data. Google sign-in, Apple sign-in, and Google Drive are directly connected services governed by their providers’ policies.
Your rights and how to use them
You can view or correct your profile, sign out sessions, disconnect Drive, see the agreement record, and delete your account in Settings. For access, correction, deletion, or suspension requests, email the privacy officer at roy@thegram.one. We respond within 10 days.
Remedies
Personal Information Dispute Mediation Committee: 1833-6972, www.kopico.go.kr. Personal Information Infringement Report Center: 118, privacy.kisa.or.kr. Supreme Prosecutors’ Office: 1301, www.spo.go.kr. Korean National Police Agency: 182, ecrm.police.go.kr.
Changes and previous versions
Changes that disadvantage people are posted at least 7 days before they take effect. Other changes take effect when posted. Previous versions remain readable at their version URLs: 2026-10-12, 2026-10-11. This version states that backups keep the latest 14 archives by count (not 14 days) and can keep older archives while uploads or cleanup fail, that sign-in code mail is relayed from our mail server through Resend, and that the sign-in cookie lasts 15 minutes.
Privacy requests and general contact: roy@thegram.one.