Privacy Policy
The Leti service (the "Service") is run by Leti ("we", "us"; see section 11) in compliance with the Personal Information Protection Act of Korea (PIPA) and other applicable laws, and this Privacy Policy explains how we handle your personal information. Because Leti is used in many countries, it also describes the rights of users in other regions, including the EU/UK (GDPR) and California (CCPA/CPRA).
At a glance
- We collect only what we need for sign-up and the Service. We do not collect your device's location, and we remove location and other metadata from photos before storing them.
- We do not sell your personal information or use it for targeted advertising.
- Your cards are shown to others only within the visibility and link settings you choose. Section 4 explains what others can see.
- Our servers and storage run in the cloud, and some providers are outside Korea. Section 6 explains where data goes.
- You can edit your profile, turn off marketing messages and delete your account in Settings.
1. What we process and why
Sign-up and sign-in
| Category | Items | Purpose |
|---|---|---|
| Email sign-up (required) | Email, password (stored only as an irreversible hash), name, @username | Identifying members, sign-in, sign-up verification, password recovery, important notices |
| External account sign-up (required) | Account identifier, email verified by the provider, and name, provided by Google, Apple or Kakao | Same as above. You can connect and disconnect external accounts in Settings |
| Sign-up checks (required) | Confirmation that you are 14 or older and when; record of agreeing or declining each version of the Terms and Privacy Policy, with time | Legal compliance, proof of consent |
| Account management | Verification codes sent when you change your email or password; list of connected external accounts | Verifying it's you, protecting your account |
| Profile (optional) | Profile photo, bio | Showing yourself to other members |
| Marketing (optional) | Email; whether and when you consented | Sending news about features and events (Marketing consent) |
Information created while you use the Service
| Items | Purpose |
|---|---|
| Cards (text, stickers, backgrounds, places on maps), images you upload to cards (My images), card thumbnails | Creating, showing and sharing cards |
| Event details (title, description, date, time, time zone, place). The time zone starts as the time zone of the device that created the event, and you can change it | Showing events in local event time, scheduling reminders |
| Visibility and link settings, questions (answers stored only as hashes, never in plain text), "Show who added it" setting | Deciding who can see a card |
| Members you select for "Selected people" visibility, or other people's email addresses you enter | Letting only those people open the card; sending them verification codes |
| Follows, follow requests, blocks, "Hide from timeline" | Timeline and relationship features |
| Reactions (who, on which card, which reaction, when) | Leaving a reaction on a card, notifying the card's creator |
| Together invitations, acceptances and declines (who invited whom, on which card, when) | Together, preventing repeated invitations to the same person |
| Covers (which card you covered and when) | Covering that card on your own timeline |
| Save (Saved list) and Add to timeline records (who, which card, when) | Showing your Saved list and timeline; notifying you when an event changes or is coming up |
| Card and profile view records (for members, your account; for non-members, the one-day hash below; which card or web profile page was opened, when and how often) | Operating statistics (seen only by administrators, never by the card's creator, the profile's owner or other members) |
| Notification records (recipient, type, read status); the push token (the address an app or browser creates to receive notifications) and device type of devices with notifications turned on | In-app and push notifications |
| Reports (reason, note, reported card or member) and moderation records (hiding cards, resetting profiles, restrictions and their reasons) | Responding to Community Guidelines violations, disputes and appeals |
| Account deletion requests (time of request, reason for leaving (optional)) | Deleting or restoring accounts, improving the Service |
| Feedback (your message, app version, app or web, device type and screen language; we do not collect device model names or identifiers) | Improving the Service and finding bugs (we do not reply) |
| Emails to us (email address, message) | Answering questions, reports and privacy requests |
| Place search terms | Finding places through an external map service (we do not store search terms ourselves) |
- If you enter someone else's email for "Selected people" visibility, you must only do so to the extent needed to send them the card. We use that email only to check access to the card and to send verification codes, and if that person signs up with the same email, we link it to their account.
- Before storing photos you upload, we remove metadata in the file such as where the photo was taken and the device used. Photos you don't use on a card are never uploaded, and photos removed from a card, or on a deleted card, are deleted from our servers too.
- Card images from Share image and Save image, and calendar files from Add to calendar, are created on your device and passed straight to the app or calendar you choose. We do not store them on our servers.
Non-members
| Items | Purpose |
|---|---|
Device identifier (a random value stored on the device, leti-device in section 9), record of answering a share link's question (a signed token per card) | Not asking again; preventing brute-force guessing |
| Number of wrong answers (hash of the device identifier and IP address) | Preventing brute-force guessing |
| Email and verification code when verifying by email | Checking whether a person may view a "Selected people" card |
| Card and profile view records: a hash of the IP address and browser information made with a secret that is used for one day only (we never store the IP address itself, and after the day ends we cannot tell whether two views came from the same person) | Operating statistics (counting each browser once per card or profile per day) |
Information generated automatically
| Items | Purpose |
|---|---|
| Access logs (IP address, access time, browser and device type, app version, error logs) | Security, fraud prevention, troubleshooting |
| Visit statistics (pages viewed, referrer, country, browser and device type, page load speed; aggregated without cookies and without identifying individuals) | Understanding and improving how the Service is used (Cloudflare Web Analytics) |
| Error reports (error details and where they occurred, app version, browser and device type, page address without search values, a pseudonymous member number; never email, name, card content or IP address) | Finding and fixing app errors (Sentry) |
| Your device's language and time zone settings | Choosing the display language and the default time zone for new events (we do not store the device settings themselves) |
| Cookies and device storage (sign-in session, language, display settings, card drafts and My images) | Keeping you signed in, remembering settings (section 9) |
What we do not process
- We do not collect your device's location (GPS, etc.). A card's place is an event venue you search for and choose yourself, not your current location.
- We do not ask for national ID numbers or sensitive information such as health or religion. However, anything you write on a card yourself (for example, funeral details in an obituary) is shown within the visibility you choose.
- We do not collect behavioral data for targeted advertising and do not use third-party advertising or analytics cookies.
2. Legal bases
- Performance of a contract: information needed to provide the Service, such as sign-up, sign-in, creating and sharing cards, Save and Add to timeline, and notifications (PIPA Art. 15(1)(4); GDPR Art. 6(1)(b)).
- Consent: marketing messages, optional profile items, and push notifications you allow on your device (PIPA Art. 15(1)(1); GDPR (a)). You can withdraw consent at any time.
- Legal obligation: consent records and records the law requires us to keep (PIPA Art. 15(1)(2); GDPR (c)).
- Legitimate interests: security, fraud prevention, handling reports and operating statistics such as card and profile view counts (PIPA Art. 15(1)(6); GDPR (f)). You can object to this processing (section 7).
- Information marked "required" is needed to use the Service. Without it, you cannot sign up or use the related feature.
3. Retention and deletion
- We keep member information and cards until you delete your account. However, an account that has not been used for 3 years or more is deleted. We email the sign-up address 30 days before deletion, and the account is not deleted if you sign in during that time. The information deleted is the same as in 2.
- When you delete your account, you are signed out on all devices right away and your profile and cards are hidden from others. In case you deleted it by mistake, you can restore it for 7 days; after that we delete your account, cards, saves, Add to timeline records, reactions, Together, covers, follows, blocks, notifications, photos, connected external accounts, push tokens, card and profile view records and feedback. Outside the app, you can request deletion as described at
leti.page/account-deletion. - Deleting a card cannot be undone. We also delete other members' saves, Add to timeline records, reactions and covers of that card, its Together members and invitations, its question and verification records, its view records and its photos.
- Copies of deleted information in backups are overwritten within 30 days.
- We keep the following separately for the periods below, and then delete them or make them no longer identify you.
| Information | Period | Reason |
|---|---|---|
| Access logs | 3 months | Protection of Communications Secrets Act of Korea |
| Consent records | 1 year after account deletion | Proof of consent, disputes |
| Account deletion requests (@username, name, masked email, reason for leaving) | 1 year after handling | Proof of deletion, disputes |
| Restriction records (email hash of restricted accounts) | 1 year after the restriction ends | Preventing abuse by signing up again |
| Report records (if a reported member deletes their account, we keep their @username and name with the report) | 1 year after handling | Disputes and appeals |
| Feedback | 1 year after sending | Improving the Service |
| Moderation records (actions taken by administrators and their opening of cards not set to Everyone) | 2 years | Korean security standards for personal information, disputes and appeals |
| Notifications | 90 days (pending follow requests until they are handled) | In-app notifications |
| Card and profile view records | 90 days after the last view (only per-card and per-profile totals are kept after that) | Operating statistics |
| Together invitations | Pending invitations: 14 days or until the event ends; declines: 30 days | Together, preventing repeated invitations |
| Non-member verification codes | 10 minutes (deleted right after verification) | Verification |
| Push tokens | Until you turn off notifications or sign out, the token expires, or it goes unused for 270 days | Sending notifications |
- We cannot delete copies other users have already taken (screenshots, card images, events added to their calendars and so on).
- Electronic files are deleted in a way that cannot be recovered, and paper documents are shredded.
4. What others can see, and disclosure to third parties
- We do not provide or sell your personal information to third parties, except where the law specifically requires it or investigative authorities request it through legal procedures.
- The information below is visible to other users as you set it while using the Service. This is publication you control, not disclosure to third parties.
| Information | Who can see it |
|---|---|
| Name, @username, profile photo, bio, follower/following counts | Any user (Find people, profile pages, the creator line on cards). Profile photos are stored where anyone with the address can see them. Profile pages of public accounts may appear in search engines |
| Cards | Within the visibility (Everyone, Followers only, Selected people, Only me) and link setting (Block, Question) you choose. Link previews in messengers and social networks show the title, date and card image only for Everyone cards and hide everything for other cards. Pages of Everyone cards made by public accounts may appear in search engines; other card pages are not listed in search engines |
| That you added a card to your timeline (name, @username, profile photo) | Always visible to the card's creator. If the creator leaves "Show who added it" on (on by default), people who can see the card see it too, and the card may appear on your followers' timelines |
| Reactions (name, @username, profile photo, the reaction you left) | People who can see the card. If the card's creator turns off "Allow reactions", all reactions are hidden |
| Together (name, @username, profile photo) | Once you accept an invitation, you appear on the card's creator line for anyone who can see the card, and the card joins your timeline and profile, where your followers may see it. A "Followers only" card with people you're with can also be seen by their followers. Before you accept, only the creator and you know about the invitation |
| Saves | Only you. Not even the card's creator can see them |
| Reports, blocks, "Hide from timeline", covers, card and profile view records, declining a Together invitation and leaving Together | Never shown or announced to the other person |
- Our administrators may view any card regardless of its visibility (including Only me cards and their photos) when needed to handle reports, check for violations of our policies or the law, respond to lawful requests from investigative authorities and others, or answer user inquiries and fix errors. This is processing to operate the Service, not disclosure to third parties. When an administrator opens a card that is not set to Everyone, we log who opened it and when in our moderation records.
5. Service providers and external services
- We entrust the following companies with processing personal information to operate the Service. Our contracts limit them to the entrusted work, and we supervise them.
| Provider | Work |
|---|---|
| Supabase, Inc. | Database, authentication, server functions |
| Cloudflare, Inc. | Website and app hosting, image storage, content delivery (CDN), security (DDoS protection), visit statistics (no cookies) |
| Google LLC | Place search (Google Maps Platform), push delivery to the Android app (Firebase Cloud Messaging) |
| Apple Inc. | Push delivery to the iPhone app (Apple Push Notification service) |
| 650 Industries, Inc. (Expo) | Sending app push notifications |
| Sendinblue SAS (Brevo) | Sending verification codes and notices |
| Functional Software, Inc. (Sentry) | Collecting and analyzing app and website error reports |
- If you receive notifications in a browser, that browser company's push service (such as Google, Apple or Mozilla) delivers them. Notification content is sent encrypted.
- We connect with the external services below, which process information under their own privacy policies.
- Sign-in with external accounts (Google, Apple, Kakao): we receive the information you agree to share on that company's screen (the identifier, email and name in section 1).
- Maps (Google Maps): when a card has a map, the viewer's device loads it directly from Google, and Google may process the device's IP address and set cookies.
- Send to other apps, Share image, Add to calendar: content goes to the app or calendar service you choose and is then governed by that service's policies.
6. International transfers
Because the Service runs in the cloud, personal information is transferred abroad as follows (PIPA Art. 28-8). These transfers are entrustment and storage necessary to perform our contract with you, so we disclose them in this Policy.
Supabase, Inc.
- Country: Korea (Seoul region)
- Items: All items in section 1
- When and how: Over the network whenever you use the Service
- Purpose: Storage, authentication, server processing
- Retention: Same as section 3
Cloudflare, Inc. (privacy@cloudflare.com)
- Country: The US and other countries with Cloudflare data centers
- Items: Access logs, content in transit, images members upload (profile photos, card photos, thumbnails)
- When and how: Over the network whenever you use the Service
- Purpose: Hosting, image storage, delivery, security, visit statistics
- Retention: Uploaded images as in section 3; otherwise immediately after processing, or short-term under the provider's policy
Google LLC
- Country: US
- Items: Place search terms, IP address of the device showing a map, Google sign-in information, push tokens and notification content for the Android app
- When and how: When searching places, showing maps, signing in or sending notifications
- Purpose: Place search, maps, sign-in, push delivery
- Retention: Under the provider's policy
Apple Inc.
- Country: US
- Items: Sign in with Apple information, push tokens and notification content for the iPhone app
- When and how: When signing in or sending notifications
- Purpose: Sign-in, push delivery
- Retention: Under the provider's policy
650 Industries, Inc. (Expo) (privacy@expo.dev)
- Country: US
- Items: App push tokens, notification content
- When and how: When sending notifications
- Purpose: Sending app push notifications
- Retention: Short-term after sending, under the provider's policy
Sendinblue SAS (Brevo) (dpo@brevo.com)
- Country: France and other EU countries
- Items: Email address, message content
- When and how: When sending email
- Purpose: Sending email
- Retention: Short-term after sending, under the provider's policy
Functional Software, Inc. (Sentry)
- Country: Germany and other EU countries
- Items: Error reports (error details and where they occurred, app version, browser and device type, page address, a pseudonymous member number)
- When and how: Over the network when an error occurs in the app or website
- Purpose: Finding and fixing app errors
- Retention: 30 days after collection (provider's retention period)
If you do not want your information transferred abroad, you can stop using the Service or delete your account; you will then not be able to use the Service. If you only want to avoid push notifications, turn them off in your device settings. For transfers of EEA/UK users' data, we rely on appropriate safeguards such as Standard Contractual Clauses (SCCs).
7. Your rights and how to exercise them
- You can access, correct or delete your personal information, ask us to stop processing it, and withdraw consent at any time.
- Profile (photo, name, bio): edit it directly in Settings → Profile.
- @username, sign-in email, password and connected accounts: change them in Settings → Account.
- Marketing messages: turn them off in Settings → Terms & policies, or with the unsubscribe link in any email.
- Push notifications: turn them off in your device or browser settings.
- Cards: edit or delete them from the card view.
- Account deletion: Settings → Account → Delete account, or outside the app as described at
leti.page/account-deletion. - Other requests (such as a copy of your data): email support@leti.page. After verifying your identity, we will reply within 10 days.
- You can also exercise your rights through a legal representative or an authorized agent (a power of attorney is required).
- We may refuse part of a request where the law allows, for example if it would infringe someone else's rights, and we will tell you why.
- We do not make automated decisions that have legal effects on you. Hiding a reported card, resetting a profile or restricting an account is decided by a person after review.
Additional rights for users in other regions
- EEA/UK (GDPR): in addition to the rights above, you have the right to data portability (receiving your data in a machine-readable format), to restrict processing, and to object to processing based on legitimate interests. You can lodge a complaint with the supervisory authority in your country.
- California (CCPA/CPRA): you have the right to know the categories, sources, purposes and retention of the personal information we collect (sections 1 to 3 of this Policy), and to delete and correct it. We do not sell or share personal information for cross-context behavioral advertising, and we do not use sensitive personal information to infer characteristics about you. We do not discriminate against you for exercising your rights.
- Other regions: you can exercise any rights the law of your country gives you in the same way.
- You can exercise these rights as described in 7-1 or at support@leti.page.
8. Children
You cannot create an account if you are under 14 (or a higher age required by the law of your country). We check age at sign-up, and if we learn that a child under that age has signed up, we delete the account and its information.
9. Cookies and device storage
- We use only cookies and device storage that are strictly necessary for the Service to work. We do not use advertising or analytics cookies.
| Name | Type | What it does | Duration |
|---|---|---|---|
Sign-in session cookie (.leti.page) | Necessary | Keeps you signed in across the website and the app | Until you sign out or your sign-in expires |
leti-locale | Necessary | Remembers your language | 1 year |
leti-device | Necessary | A random value that tells this device apart, used only to limit wrong answers to questions on devices that are not signed in | 1 year |
leti-access-<card> | Necessary | Remembers cards you unlocked with a question or email verification on a device that is not signed in | 30 days |
| Device storage (localStorage, IndexedDB) | Necessary | Display settings, card drafts and My images, custom colors | Until deleted |
- When a card has a map, Google Maps may set cookies under Google's policies (5-3).
- You can block or delete cookies in your browser settings, but you cannot sign in if the session cookie is blocked.
- If we ever start using analytics or advertising cookies, we will update this Policy first and ask for consent where the law requires.
10. Security measures
- Passwords and question answers are stored only as irreversible hashes.
- All traffic is encrypted (HTTPS), and data is encrypted at rest.
- The database uses row-level access control (RLS) so that, among users, only people who may see a card can read it. Card photos are shown only to people who may see the card, through addresses that are valid for a short time. Administrator access to cards is described in 4-3.
- We keep the number of staff handling personal information to a minimum. Administrators sign in with two-factor authentication and have role-based permissions, and every administrator action, as well as every time an administrator opens a card not set to Everyone, is logged.
- We limit sign-in and verification attempts to prevent brute-force attacks.
- If personal information is breached, we notify affected users and report to the authorities without delay as the law requires.
11. Privacy team
| Operator | Leti |
| Privacy team | Leti Operations Team |
| Contact | support@leti.page |
Users in Korea can also contact the following for help with privacy violations:
- 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)
12. Changes to this Policy
When we change this Policy, we announce it in the Service at least 7 days before it takes effect (30 days for significant changes), and ask for your consent again when a change requires it. Previous versions are available on this page by version.