Airpost Privacy Policy
- 1. Scope and Responsibility
- 2. Information and Purposes
- 3. Collection Methods and Legal Grounds
- 4. Retention and Deletion
- 5. Visibility and Third-Party Disclosure
- 6. Service Providers and External Services
- 7. International Transfers
- 8. Location and Device Permissions
- 9. Cookies, Automatic Collection and Tracking
- 10. Safeguards
- 11. Rights and Requests
- 12. Age and Sensitive Information
- 13. Automated Decisions and Additional Uses
- 14. Additional Regional Rights
- 15. Privacy Contact and Remedies
- 16. Changes and Effectiveness
Version: 2026-10-15 Last updated: October 15, 2026 Effective date: October 15, 2026 The main changes in this version are listed in Section 16(5).
1. Scope and Responsibility
1. Seungwoo Yang, a sole proprietor operating in the Republic of Korea under the registered trade name 벡터랩스 (VectorLabs) (the “Operator”), establishes this Policy for personal information processed through the Airpost app, related policy websites and customer support. 2. The Operator determines the purposes and means of processing. Providers’ own privacy policies also apply where external sign-in, mapping or other providers independently process information. 3. This Policy describes processing and User rights. Reading it or using the Service does not constitute consent to every activity requiring separate consent. When a User selects Sign in with Apple or Sign in with Google on the sign-in screen, or Continue on the re-acceptance screen, the Operator records, with each version and time, the User’s agreement to the Terms of Use and acknowledgement of this Policy. This record is not consent to this Policy and does not replace any separate consent required for specific processing. 4. In this Policy, “Service”, “User”, “Member” and “Member Content” have the meanings given in Articles 1 and 2 of the Airpost Terms of Use. 5. This Policy is provided in Korean and English, and the two versions are intended to say the same thing. If they differ, the Korean version prevails.
2. Information and Purposes
1. The Operator processes the following information to provide the Service. Information needed only for a specific feature, such as the optional profile, notifications, location, and reports and support, is processed only when the User chooses that feature or submits an inquiry or report.
| Category | Information | Purpose and collection context |
|---|---|---|
| Account and authentication | Account ID, Apple or Google identifiers, email, name and profile image URL supplied by the provider, authentication and session information (including the IP address and device and browser information of sign-in sessions) | External sign-in, account identification, session management, disconnection, and email notices of material matters |
| Registration and profile | Nickname, date of birth, gender, interests, languages and proficiency, avatar, hub airport and related city information, the pen-pal ID assigned by the Service, and the Find Pen Pals visibility and ID-search settings | Eligibility, profiles, Member discovery and service delivery |
| Optional profile | Biography and other additional information entered by the Member | Display of optional additions or updates |
| Interactions and content | Relationships, requests and blocks, private and public letter titles and text, audio and drawings, sender and recipient IDs, sending, arrival and opening times, flight numbers, display information such as stamps, seals, fonts and aircraft, delivery route information (airports and coordinates), and hidden public letters | Member interaction, delivery and storage, public posting and safe use |
| Discovery and recommendation records | IDs of the Member shown a recommendation and of the recommended Member, recommendation score, shared interests and matched language, recommendation status and shown, response and expiry times, declined pen-pal requests (requesting Member, declining Member and time), Find Pen Pals search times and pen-pal ID lookup times | Pen-pal recommendations and discovery, balancing recommendation exposure, avoiding repeat suggestions, limiting repeat requests after a decline, and enforcing hourly search and lookup limits |
| Terms and Policy records | Version of the Terms of Use accepted, version of the Privacy Policy acknowledged, the time of each, and the version, time and withdrawal time of any overseas-transfer consent given under the September 20, 2026 version | Recording the formation of the agreement and the acknowledgement of this Policy (at sign-in or re-acceptance) |
| Stamp and seal collection records | Letter and design IDs, collection type, acquisition time and display information | Showing the stamps and seals a Member has acquired and their collection history |
| Notifications | Push and Live Activity tokens and their environment, recipient, notification title, subtitle and text and their display arguments (such as the sending Member’s nickname and origin and destination airports), for Live Activities the letter ID, flight number, airport codes and departure and arrival times, and the times landing-soon and arrival notifications were sent for each letter | Delivery of service notifications such as letter status |
| Location | Current location (not sent to or stored on the Operator’s servers; coordinates are sent to Apple’s map service for city lookup), selected hub airport and identified city name | Airport suggestions and city lookup when location access is permitted |
| Reports and support | Report target, reason, time and status, the details written by the reporter, the public letter text copied when a report is filed, the reported Member’s nickname and biography copied when a profile is reported, necessary text and attachment evidence, sanction records, inquiry email and content, rights requests and deletion records | Investigation, harm prevention, support and fulfillment of rights requests |
| Access and operations | IP address and the connection country derived from it, request time, path and status, authentication, error and security records, and server job records | Hosting and authentication operations, troubleshooting, security, and checking the connection country when a hub airport is chosen or changed |
2. The Operator does not directly collect external account passwords. Information supplied by a sign-in provider depends on the method and the User’s provider settings. 3. Full dates of birth and authentication email addresses are not shown to other Members. Other Members see only the age calculated from the date of birth; Section 5 describes visibility. 4. The current Service does not directly collect payment card or bank account numbers or behavioral information for targeted advertising.
3. Collection Methods and Legal Grounds
1. Information is obtained from User input and transmission, external sign-in providers, records generated through use of the Service, and support communications. 2. In Korea, processing necessary for account management and the requested Service relies on contract formation or performance under Article 15(1)(4) of the Personal Information Protection Act. Optional processing requiring consent relies on consent under Article 15(1)(1). 3. Processing for safety, security and protection of rights relies on Article 15(1)(6) only where it is necessary to achieve the Operator’s legitimate interest, that interest clearly overrides the User’s rights, and the processing is substantially related to that interest and does not exceed a reasonable scope. Processing to comply with legal obligations, such as retaining access records under the Protection of Communications Secrets Act, relies on Article 15(1)(2). 4. Operating-system permissions for location, microphone and notifications are distinct from legally required consent. A device permission does not replace separate consent where required. 5. Refusing necessary processing may prevent the relevant Service from being provided. Refusal of an optional feature’s information does not restrict unrelated features. 6. For Users outside Korea, the Operator relies on the grounds recognized by the applicable law: entering into and performing the contract to provide the Service the User requested, the User’s consent, legitimate interests in safety, security and protection of rights, and compliance with legal obligations.
4. Retention and Deletion
1. The Operator deletes personal information without undue delay when its purpose or retention period ends. The server’s automatic cleanup runs every minute and, separately, once a day directly in the database. Information in the table below that is subject to the server’s automatic cleanup is therefore deleted once its period ends, normally within minutes and at the latest within one day. However, deleting the stored files of expired uploads and report evidence, and account deletion, are handled by the every-minute cleanup. Information subject to a legal preservation duty is segregated from ordinary service data.
| Information | Retention or deletion rule |
|---|---|
| Accounts, profiles and authored content | On account deletion, the authentication account (email, external sign-in identifiers and sessions), date of birth, gender, biography, interests, languages, avatar, country, city and hub airport, device notification tokens, the titles, text, audio and drawings of letters the Member wrote and the text of their public letters are deleted through the procedure in paragraph 2, and the nickname is replaced with “Deleted User”. Records that remain after account deletion follow paragraph 3; report evidence and other exceptions follow the rules below |
| Public letters | Shown on the public letter board for 7 days after posting, or until the author deletes it. Public letters have no audio or drawing attachments, and replies to a public letter are handled as ordinary letters. When the author deletes a public letter or the 7 days end, automatic cleanup clears its text. While a report about that public letter is submitted or under review, the text is kept and is cleared at the first cleanup after the report is resolved or dismissed. The record left after the text is cleared (author ID, flight number, stamp ID, posting, expiry and deletion times, and status) is deleted one hour after the letter leaves the board. If a reply letter, report or moderation record refers to it, it is kept without text while that record remains. Records of public letters a Member has hidden (the hiding Member’s ID, the public letter ID and the time hidden) are deleted by a cleanup job that runs once a day after the public letter expires or leaves the board, and are also deleted when the public letter record is deleted. The text copied when a report is filed follows the report rules below |
| Unsent attachments | Unused upload reservations are valid for seven days. After that, automatic cleanup deletes the file without undue delay (checked every minute and retried every 15 minutes on failure), and the upload record (uploading Member’s ID, type, storage path, file hash, size, letter ID, state and times) is deleted 30 days after the file is deleted. Files attached to sent letters and their upload records are kept while they remain attached to the letter, and on account deletion they are deleted under paragraph 2, items (3) and (4) |
| Detailed reports and evidence copies | Retained while the report is submitted or under review. Once 30 days have passed after resolution, automatic cleanup deletes the evidence files, the evidence record, the report details and the public letter text copied when the report was filed, in that order. The reported Member’s nickname and biography copied when a profile is reported, and evidence copies made on account deletion (the title and text of the reported letter, the report details and copies of the letter’s attachments), follow the same rule. These copies remain, even if the reported Member or the reporter deletes their account, until they are deleted under this rule. Material for a reopened report is kept again as material under review |
| Report summaries and sanction records | Report records are deleted 90 days after resolution, and sanction records 90 days after the sanction ends. A sanction record linked to an open report is kept until that report is closed, and a report record linked to a sanction record is kept until that sanction record is deleted. Only minimum records necessary to review repeated problems and appeals are retained, and they are deleted without undue delay if no longer needed earlier. Account deletion ends any sanction on that account and its content |
| Discovery and recommendation records | Pen-pal recommendation records are deleted 30 days after their last activity (the later of when the recommendation was shown and when it was skipped, requested or expired). Within that time they are used to balance recommendation exposure over 30 days and to avoid suggesting the same Member again (3 days for a skipped recommendation, 7 days for an expired one, and for as long as the record remains for an open or requested one). Declined pen-pal request records are deleted 30 days after the decline, which is the period during which the same Member cannot be asked again. Find Pen Pals search times and pen-pal ID lookup times are used only for hourly limits and are deleted after one day |
| Terms and Policy records | Kept while the account exists and deleted with the authentication account when account deletion is completed |
| Notification jobs (before sending) | While a job is waiting to be sent or retried (normally seconds to minutes), the notification title, subtitle, text and display arguments (such as the sending Member’s nickname and origin and destination airports) and the push or Live Activity token with its environment are kept; Live Activity jobs also keep the letter ID, flight number, airport codes and departure and arrival times. When a job is sent, cancelled or permanently fails, its content and token are deleted immediately. A job not delivered within its window, one day for ordinary notifications or the expiry set for each Live Activity update (one hour by default), is cancelled and cleared the same way. Retries stop after four attempts |
| Notification job records (after sending) | Only the job ID, recipient’s account ID, letter ID, notification kind, status, attempt count, batch and processing IDs, creation, next-attempt, processing-deadline, expiry and completion times, a short error code (at most 80 characters, such as an APNs reason) and a one-way SHA-256 hash of the de-duplication key remain. The de-duplication key was built from the letter, the notification kind and the token, and the token cannot be recovered from the hash. These records are deleted 30 days after completion; jobs addressed to a Member who has deleted their account are deleted at the first cleanup after they finish, without waiting 30 days |
| Account deletion job records | The account ID, receipt number, step-completion flags, status, attempt count, times and a short error code are deleted 30 days after the job is completed |
| Records remaining after account deletion | Kept under paragraph 3 only while another Member’s records need them, and deleted by automatic cleanup once every related Member has also left |
| Support and notice email and rights-request records | Kept in the Operator’s Gmail account for up to 90 days after the inquiry or rights request is resolved. Notice emails the Operator sends are kept for up to 90 days after sending. Only messages, attachments and replies needed for follow-up are kept, and the Operator deletes them when the period ends or their purpose ends earlier |
| Supabase service logs | API and database service logs are retained for one day; separate authentication-audit service logs are retained for one hour. The authentication access records below are retained separately |
| Authentication access records | For authentication events such as sign-up, sign-in, sign-out, token refresh or revocation, account changes and sign-in disconnection, the event type and category, account ID, authentication email (always recorded for Google sign-in; for Apple sign-in only where Apple supplies an email, and the app does not ask Apple for an email or name), name (only where the sign-in provider supplies one, which applies to Google sign-in), SSO flag, event attributes such as the provider, IP address and time are recorded. These records contain no device or browser information; the device and browser information of a sign-in session is kept only while the session exists and is deleted with the account. Authentication access records are stored separately from the account, are not deleted with it, and are retained for three months, including after account deletion. Records older than three months are deleted by an automatic cleanup job that runs every hour |
| Policy website hosting records | The Operator does not receive or separately store GitHub Pages visitor logs. GitHub independently processes service and website usage records such as visitor IPs, request times and pages for its own security and operations, and retains them for as long as needed for website delivery, security and legal obligations under GitHub’s privacy statement |
| Provider recovery copies | If a service provider retains internal recovery copies, those copies are handled under that provider’s retention and deletion policy |
| Legally preserved records | Internet log records and access-location tracking data for a service that intermediates Member communications are retained for three months under Article 15-2 of the Protection of Communications Secrets Act and Article 41(2)(2) of its Enforcement Decree. The authentication access records above are these records, and the retained items are those listed in that row. The current free Service does not generate payment, cancellation or withdrawal records for paid transactions under Korean e-commerce law |
2. When account deletion is requested, new use is restricted at once, registered notification and Live Activity tokens are deleted, Find Pen Pals visibility and ID search are turned off, and deletion processing begins immediately. Deletion usually completes within minutes of the request but may take longer depending on the amount of attachments or server conditions, and if provider processing or a failure leaves work outstanding, the server retries it automatically. Acceptance and completion are separate stages, and the app shows the processing status. Processing works as follows. (1) For accounts that signed in with Apple, the Operator asks Apple to revoke the sign-in authorization (token revocation). The Operator does not ask Google to disconnect the account, so Users can remove the Airpost connection shown in their Google Account settings themselves. (2) Evidence copies of reported content are made under the report rules in the table in paragraph 1. (3) In the same step, the titles, text, audio and drawings of letters the Member sent are deleted and those letters are made unreadable, and delivery route information (airports and coordinates) is deleted for every letter the Member sent or received. The Member’s public letters lose their text and are withdrawn. Report details the Member wrote, public letter text copied into reports against the Member and the details of duplicate reports involving the Member are cleared. However, details already copied into an evidence copy because the reported Member deleted their account first are deleted under the report-evidence rule in the table in paragraph 1. The Member’s upload records, including those of files attached to letters the Member sent, are queued for file deletion and are deleted 30 days after the files are deleted. Date-of-birth, gender and language records are also deleted. The profile’s nickname is changed to “Deleted User” (“탈퇴한 사람” in Korean), and its biography, interests, country, city, hub airport and avatar are cleared. Pending pen-pal requests are deleted and other pen-pal relationships are ended. (4) After the audio and drawing files the Member uploaded are deleted from storage, the authentication account and the Apple or Google sign-in information linked to it are finally deleted. Sign-in sessions and refresh tokens, Terms acceptance and Policy acknowledgement records and the stored Apple token are deleted with it. 3. After deletion is completed, the following records remain only while another Member’s records need them, so that other Members’ mailboxes, pen-pal lists and block lists stay intact. The departed Member is shown to other Members as “Deleted User”, and letters the departed Member sent are shown as deleted because their author left. (1) Profile record: internal account ID, pen-pal ID (which cannot be searched and is shown to no one), the “Deleted User” label, status, sign-up, onboarding, last-update, deletion-request and deletion times, and the Find Pen Pals visibility and ID-search settings, both turned off (2) Records of letters the Member sent, without titles, text, audio or drawings: letter, sender, recipient, pen-pal relationship and request IDs, flight number, stamp, seal, font and aircraft IDs, public-letter link, moderation state, creation, sending, arrival and opening times, and the times landing-soon and arrival notifications were sent (3) Letters other Members sent to the Member: these include the text those Members wrote and remain as their sent letters, without delivery route information (4) Ended pen-pal relationships: both Members’ IDs, relationship kind and status, requesting Member, and request, creation, activation and end times (5) Block records in both directions: blocking Member, blocked Member and time, used to decide what the remaining Member sees, such as their block list and hidden letters and stamps (6) Public letter records whose text has been cleared, under the public letter rule in the table in paragraph 1 Stamps and seals that other Members received in the departed Member’s letters may continue to appear in their collections through the letter records in item (2). Report and sanction records are kept and deleted separately under the table in paragraph 1. Discovery and recommendation records involving the departed Member, that Member’s seal ownership records, retired friend-invite records and hidden-public-letter choices are deleted at the first cleanup after the content-deletion step of account deletion. 4. The records in paragraph 3 are deleted by automatic cleanup once every related Member has also completed their own deletion. Letters, pen-pal relationships and block records are deleted when every participant’s deletion has finished, but are kept while a report, duplicate-report or moderation record refers to the letter. The profile record is deleted once no letter, pen-pal relationship, block, public letter, report, duplicate-report or moderation record, or App Review demo-room setting refers to it and none of its notification jobs is unfinished. Its pen-pal ID is then kept only as a seven-character code in a list of retired IDs, with no link to any account, and is used only to ensure the same ID is never issued again. Nothing in this paragraph is cleaned up while deletion is still in progress (that is, while the authentication account has not yet been deleted). Letters that still have audio or drawing records, which can only remain for accounts removed outside the in-app deletion flow, such as from an administration console, are excluded from automatic cleanup and are checked and handled individually by the Operator. 5. Private letter drafts stored on the device, letters left in the device outbox after a failed send (including their titles, text, audio and drawings), reports not yet sent to the server and downloaded attachment caches are kept only on that device. A letter that failed to send stays on the device until the Member resends or deletes it, and all of this on-device information is deleted from the device on sign-out or withdrawal. However, a public letter draft in progress (its text and the selected stamp) is kept in the app’s settings storage, which is not separated by account and may be included in device backups, and it is not deleted on sign-out or withdrawal. The draft is deleted when the Member leaves the compose screen without saving or posts the public letter; until then it may also appear on the public letter compose screen of another account signed in on the same device. Revoking a device permission or uninstalling the app does not itself delete server accounts or content. 6. Electronic information is deleted using methods intended to prevent recovery or reproduction. Any physical copies are securely destroyed, for example by shredding. Restoring backups requires reapplying previously completed deletion requests. 7. Deleting information within the Service does not recall copies saved or forwarded outside it. Suspected rights infringements may be reported to the contact in Section 15. 8. Minimum records needed for ongoing reports, disputes or active sanctions are separately managed for a specific purpose and lawful basis, with periodic review of necessity. Once that reason ends, the rules above apply. This is not a general basis for indefinite retention. Separate statutory preservation duties follow the relevant law and period.
5. Visibility and Third-Party Disclosure
1. Information is visible as follows when providing the Service.
| Audience | Information | Purpose |
|---|---|---|
| Members able to view a profile | Nickname, age, gender, biography, interests, languages, avatar, country, hub airport and activity information displayed in the profile | Discovery and interaction |
| The private-letter correspondent | Letter title, text and attachments and profile, delivery and opening information displayed with the letter | Private correspondence |
| Members able to view public letters | Public letter text and author display information | Public posting and interaction |
2. Sensitive information entered in public areas may be exposed to other Members. Users can avoid entering it, edit or delete their biography in the app, and edit or withdraw their public letters. Turning off “Show my profile in Find Pen Pals” in Settings removes the profile from Find Pen Pals, and Users who cannot make a change themselves may ask the contact in Section 15 to correct or remove it. Information sent in a private letter is still disclosed to its recipient. 3. The Operator does not sell personal information or disclose it for third parties’ independent advertising purposes. Disclosures outside service delivery require separate consent or another applicable lawful basis. 4. Requests from authorities are assessed for legal authority and scope and fulfilled only as lawfully necessary. Processing on behalf of the Operator and providers’ independent processing are distinguished in Section 6. 5. Other Members may be outside Korea. The information in paragraph 1 that is shown or delivered to them is limited to what the User publishes in a profile or public letter or sends in a letter, and what the Service displays alongside it as part of the service the User requested (such as the age calculated from the date of birth, a letter’s delivery information and whether and when it was opened, and the activity information displayed in the profile). Because this is the User publishing or sending information through the Service, together with what is displayed as part of that service, the Operator does not treat it as its own international transfer (Section 7) and does not provide personal information to Members abroad for any other purpose. A Member’s country and hub airport appear on their profile. Profiles appear in Find Pen Pals by default and stop appearing there when the User turns off “Show my profile in Find Pen Pals” in Settings; Members who know the User’s pen-pal ID can still send a pen-pal request. Block and report features can restrict contact with a particular Member.
6. Service Providers and External Services
1. The external providers used to provide the Service and their processing relationships are as follows.
| Provider or service | Work and information | Relationship |
|---|---|---|
| Supabase Pte. Ltd. and its subprocessors (including Amazon Web Services, Inc. and Cloudflare, Inc.) | Accounts, content and access information needed for database, authentication, file storage and server functions | Processor for service delivery. The published DPA forms part of Supabase’s service terms and addresses purpose limitation, security, subprocessors and deletion. The primary data region is the Seoul, Republic of Korea region of Amazon Web Services, and service requests pass through Cloudflare’s network. The full subprocessor list is at supabase.com/legal/customer-resources/subprocessor-list |
| Google Gmail | Support email addresses, messages, attachments and replies, and the recipient address and content of notice emails the Operator sends | The Operator sends, receives and keeps support email, and sends notice emails, in a standard (personal) Gmail account. Google provides the email service independently under the Gmail terms of service and Google’s privacy policy, and there is no data processing agreement between the Operator and Google |
| GitHub, Inc., GitHub Pages | Access information such as visitor IPs when the policy website is visited | Policy website hosting provider. When a User opens the policy website, the User’s device connects directly to GitHub’s servers, and GitHub collects and processes the access information for its own security and operations. The Operator does not receive or store this information |
| Apple sign-in, maps and push services | Sign-in information, mapping requests, device tokens and notification display information | Feature provider; independent processing follows Apple’s policy |
| Google sign-in | Sign-in identifiers and approved basic profile information | External authentication provider; independent processing follows Google’s policy |
2. Processing by Supabase on the Operator’s behalf is governed by the DPA that forms part of Supabase’s service terms. The DPA covers purpose limitation, safeguards, subprocessing, supervision and responsibility, and the Operator checks that it is applied. Under the DPA, Supabase and its subprocessors give personal information the same or an equivalent level of protection as this Policy describes. 3. Apple’s and Google’s sign-in, maps and push services are used under the standard terms each provider publishes. Gmail and GitHub Pages are not operated as processing on the Operator’s behalf; each provider processes information independently under its own terms and privacy policy. For providers other than Supabase, the Operator ensures that only the minimum information needed for the relevant feature reaches them and uses providers that publish their privacy protections and privacy policies. Each provider’s privacy policy applies to information it processes for its own purposes. 4. Providers’ policies do not replace this Policy. Relevant materials include the Supabase DPA and subprocessor list and the Apple, Google and GitHub privacy policies.
7. International Transfers
1. The primary database region is Seoul, Republic of Korea. Overseas support, authentication, mapping, notifications, email and hosting may nevertheless involve international transfers, so the primary database location does not establish that all processing takes place in Korea. Information transferred to or processed in another country is subject to that country’s laws and may be accessed by its courts, law enforcement and national security authorities as permitted by those laws. Information shown or delivered to Members in other countries follows Section 5(5). 2. Any transfer of personal information outside Korea by the Operator, through provision, outsourced processing or storage, requires a lawful basis under Article 28-8 of the Personal Information Protection Act, whatever the User’s nationality or residence. Disclosure or notification for necessary outsourced processing or storage is distinct from transfers requiring separate consent. Publication of this Policy does not establish consent to every transfer.
| Recipient and purpose | Information, timing and method | Countries, contact, retention and basis |
|---|---|---|
| Supabase Pte. Ltd., Supabase, Inc. and subprocessors (Amazon Web Services, Inc., Cloudflare, Inc. and the companies on Supabase’s subprocessor list): hosting, authentication, files and support | Necessary accounts, content and access information; encrypted transmission or authorized access during requests, storage or support | Primary data storage is in the Seoul, Republic of Korea region of subprocessor Amazon Web Services, Inc. (a US company; contact: aws.amazon.com/privacy). Service requests pass through the network of Cloudflare, Inc. (a US company; contact: cloudflare.com/privacypolicy) and may be processed at a location in a country near the User. Possible access for contracting and support is in Singapore (Supabase Pte. Ltd.) and the United States (Supabase, Inc.); contact: privacy@supabase.io. The names, processing countries and functions of other subprocessors are listed on Supabase’s subprocessor list (supabase.com/legal/customer-resources/subprocessor-list). Processing continues during the service agreement, and the DPA requires deletion after the 30-day return-request period following expiry. The basis is outsourced processing or storage necessary to perform the User’s service contract, disclosed in this Policy under Article 28-8(1)(3)(a) of Korea’s Personal Information Protection Act |
| Apple Inc. and Apple Distribution International Limited: sign-in, maps and push | Feature-specific identifiers, mapping requests, tokens and notification content; encrypted network transmission when used | United States and Ireland; contact: apple.com/privacy/contact. Apple processes the information until the feature purpose is fulfilled and there is no further legal or business need under its policy. The basis is outsourced processing necessary for sign-in or notifications chosen by the User, the maps required for the Service’s screens, and performance of the service contract, disclosed under Article 28-8(1)(3)(a) |
| Google LLC: Google sign-in | Sign-in identifiers and approved basic profile information; encrypted network transmission during sign-in | United States. Privacy inquiries may be made through the process at policies.google.com/privacy. Information is processed while the account link remains. The basis is outsourced processing necessary for the User’s chosen sign-in and performance of the service contract, disclosed under Article 28-8(1)(3)(a) |
3. The following overseas providers process information under their own terms and privacy policies, not on the Operator’s behalf. Information reaches them at the times and by the methods stated in the table below.
| Provider and purpose | Information, timing and method | Country, contact and retention |
|---|---|---|
| Google LLC: Gmail support and notices | Address, text and attachments of inquiry email the User sends, the Operator’s replies, and the recipient address and content of notice emails the Operator sends to a Member’s authentication email address; sent by the User’s email service to Gmail when the User emails the support address, and composed and sent from Gmail when the Operator replies or sends a notice | United States. Privacy inquiries may be made through the process at policies.google.com/privacy. The Operator deletes inquiry email within 90 days after the inquiry is resolved and notice email within 90 days after sending; Google’s policies then govern its deletion processing and any limited legal retention |
| GitHub, Inc.: GitHub Pages policy website hosting | Visitor IP, request time and page, and device and browser information; an encrypted connection between the User’s device and GitHub’s servers when the User opens the policy website | United States; contact: privacy@github.com. GitHub retains information for as long as needed for website delivery, security and legal obligations under its privacy statement. The Operator does not receive or store this information |
4. Users may ask the contact in Section 15 for information about international transfers or refuse a transfer. The method, procedure and effect of refusal for each transfer are as follows. (1) Supabase: this transfer is necessary for the database, authentication and file storage. To refuse it, do not register, or withdraw with the account deletion function in Settings. The Service cannot then be used. (2) Apple or Google sign-in: choosing the other sign-in method on the sign-in screen means no sign-in information is transferred to the provider not chosen. (3) Apple push notifications and Live Activities: if notification permission is not allowed, no device token or Live Activity token is registered and no notification content is sent to Apple. For a device that is already registered, signing out removes the registration, and signing in again with notification permission turned off in device settings does not register it again. Notifications are then unavailable, but letter status remains visible in the app. (4) Apple Maps: map display, airport and place search, and city-name lookup for map positions are necessary for the Service’s screens and cannot be refused separately; a User who does not want them must stop using the Service. If location permission is not allowed, the current location is not used and the User can choose an airport manually. (5) Gmail support and notices, and GitHub Pages (paragraph 3): inquiries and rights requests may instead be made by post or by the business telephone number in Section 15, and copies of the Terms of Use and this Policy may be requested through the same contacts instead of opening the policy website. A Member who does not want notice emails may tell the Operator through the same contacts, and the Operator will then give notices by other means such as in-Service announcements. Refusals may be requested at forwoobusiness@gmail.com or by post or telephone using the details in Section 15. If the Operator introduces a transfer that requires separate consent, its effects will be explained in that consent process.
8. Location and Device Permissions
1. If location access is permitted, the current location is used only on the device to suggest nearby airports. To look up the city name of the current location or of a point chosen on the map, those coordinates are sent to Apple’s map service. Current-location coordinates are not sent to or stored on the Operator’s servers; the Operator stores only the hub airport the User selects and the city name identified this way. 2. The microphone is used when the User records audio. Recordings are made on the device, and only a recording attached to a letter is uploaded while that letter is being sent. Recordings in letters that fail to send stay in the device outbox until the letter is resent or deleted (Section 4(5)), and unsent uploads left on the server follow the rule in Section 4(1). 3. Notification permission enables service alerts. Permissions can be changed in device settings; this does not automatically delete content stored on servers. 4. To keep the country shown on profiles reliable, whenever a hub airport is chosen or changed the Service checks the connection country that the hosting provider derives from the IP address, whether or not location access is permitted. If airports are available in that country, only those airports can be chosen. If the country cannot be determined or has no available airport, this restriction does not apply. The connection country is used only for this check and is not stored with the account.
9. Cookies, Automatic Collection and Tracking
1. The Airpost app does not use advertising SDKs or SDKs that track users across other apps or websites for advertising. The Operator does not sell or share personal information for targeted advertising. 2. Local session storage and necessary operational records are handled separately from advertising tracking. The Operator does not add separate advertising or analytics scripts to the policy website. 3. External sign-in pages and hosting providers may use their own cookies or technical records under their policies. Browser cookie restrictions may affect external sign-in and similar functions. 4. The Operator does not track Users’ activities over time and across third-party apps or websites through the app or the policy website, and does not place third-party tracking tools in them. Because no such tracking occurs, the Service does not respond differently to browser “Do Not Track” signals. Information processed by providers on external sign-in pages is covered by paragraph 3.
10. Safeguards
1. The Operator applies the following measures. (1) Administrative: authority to process personal information is limited to the Operator, and report-review material is handled only in a restricted review screen. (2) Technical: encrypted communications, account-based authorization and row-level access control in the database, private file storage, protection of authentication information and necessary access management. Letters kept in the device outbox are protected so they cannot be read before the device is first unlocked after it restarts, and are excluded from device backups. (3) Physical: no separate server room is operated; servers and databases run in data centers managed by Supabase and its subprocessors. 2. Operational and report-review access is limited to necessary information and purposes. The Operator works to keep unnecessary letter text and authentication secrets out of logs. 3. Private letters are not end-to-end encrypted. The Operator and processors authorized by the Operator may handle them as needed for service delivery or lawful safety review. 4. For a personal information incident, the Operator investigates, takes protective action and provides User and regulator notifications required by applicable law.
11. Rights and Requests
1. Users may request access, correction, deletion, suspension of processing, withdrawal of consent and applicable transmission or portability rights under the relevant law. 2. Requests can be submitted through account management functions in the app, to forwoobusiness@gmail.com, or by post or telephone using the details in Section 15. Incomplete registration, restrictions or inability to sign in do not prevent requests by email or these other means. 3. Representatives’ requests are verified using the minimum information needed to establish identity and authority. Excessive identity information relative to the request is not required. 4. Requests are handled within applicable statutory time limits and procedures. Restrictions, refusals or extensions will be accompanied by the permitted basis, reasons and available remedies. 5. Other Members’ rights, legal preservation obligations or other lawful exceptions may limit particular requests. Users will not be unfairly discriminated against for exercising rights.
12. Age and Sensitive Information
1. The Service is intended for people aged 18 or older and does not permit underage registration. Suspected underage use is assessed using the minimum necessary information and followed by appropriate restriction and deletion measures. 2. The Operator does not collect resident registration numbers or unmasked identity-document copies. If documents are requested to check age, everything other than the date of birth (such as the back digits of a resident registration number, the address and the photo) must be masked, and the documents are deleted without undue delay after the check. Audio and drawings are not analyzed as biometric identifiers. 3. Content entered by Members may include health, religious, sexual or other sensitive information. Some jurisdictions also classify private correspondence or precise location as sensitive. Some information processed in the Service may therefore be sensitive. 4. The Operator processes sensitive information that requires additional legal conditions, such as separate consent, only when those conditions are met. The Operator does not ask for unnecessary sensitive information and accepts inquiries about its exposure or deletion.
13. Automated Decisions and Additional Uses
1. The Service uses automated processing for discovery, delivery calculations and abuse prevention. For example, profile text, public letters and private letter titles and text are automatically checked for blocked terms before they are saved, and text containing a blocked term is not saved or sent. The current Service does not operate solely automated decision-making that produces legal or similarly significant effects on Users. 2. The Operator does not use Member Content for advertising profiling or general-purpose AI model training. 3. The Operator does not use or disclose personal information without consent on the ground that the use is reasonably related to the original purpose of collection. Before introducing any such use, the Operator will publish in this Policy its criteria for the factors in Article 14-2(1) of the Enforcement Decree of the Personal Information Protection Act: relation to the original purpose, foreseeability, whether the User’s interests are unfairly harmed, and safeguards such as pseudonymization or encryption.
14. Additional Regional Rights
1. This Section applies where the relevant jurisdiction’s legal conditions are met. It does not reduce any mandatory rights. 2. United States: applicable state laws may grant rights to know and obtain copies, correct or delete, opt out of sale, sharing, targeted advertising or certain profiling, limit sensitive information uses, use authorized agents and appeal refusals. Applicability depends on residence and statutory business thresholds. Categories, sources, purposes and recipients are set out in Sections 2–7. The Operator does not sell information or share it for cross-context behavioral advertising. 3. Canada, Australia, Brazil and other regions: the Operator honors applicable information, access, correction, deletion, consent withdrawal and regulatory complaint rights. Users may write to the contact in Section 15, stating their country of residence and their request, and the Operator will handle it under the relevant law.
15. Privacy Contact and Remedies
Registered trade name: 벡터랩스 (VectorLabs), a sole proprietorship Proprietor: Seungwoo Yang Business registration number: 251-43-01545 Business and mailing address: Room 306, 10-7 Myeongnyun 3-gil, Deokjin-gu, Jeonju-si, Jeonbuk State, Republic of Korea Privacy officer and complaints contact: Seungwoo Yang (Proprietor) Privacy inquiries and rights requests: forwoobusiness@gmail.com Business telephone: +82-10-5059-7322 Korea Privacy Infringement Reporting Center: privacy.kisa.or.kr · 118 Korea Personal Information Dispute Mediation Committee: www.kopico.go.kr · 1833-6972 Overseas Users may seek relief directly from their competent privacy authority.
16. Changes and Effectiveness
1. Changes and effective dates will be published in advance. Material changes affecting rights will also be communicated by appropriate means such as email, and separate consent will be obtained where required. 2. The effective Policy is this page, and previous versions from version 2026-09-27 onward are listed under “Previous versions” at the bottom of the policy website. The text of each version is fixed on its own archive page and does not change. Earlier versions are provided on request to the contact in Section 15. 3. Before introducing new processing activities or automated decisions, the Operator will establish the necessary legal grounds, notices, consent, explanations and objection procedures. Any introduction of the sale or sharing of personal information for advertising will also include the opt-out mechanisms and browser-signal handling required by applicable law. 4. This Policy takes effect on October 15, 2026. The previous Policy (version 2026-09-27) applied until October 14, 2026. 5. Compared with the previous Policy, the main changes in this version are as follows. (1) The minimum age for the Service is raised from 16 to 18 (Section 12(1)). (2) The effective date is set to October 15, 2026 to match this version, and how to find previous versions is stated (header, Section 16(2) and (4)). (3) The records made at sign-in and re-acceptance are explained as agreement to the Terms of Use and acknowledgement of this Policy, not consent to this Policy, and the meaning of terms and the rule for differences between the Korean and English versions are stated (Section 1(3)–(5)). (4) Pen-pal IDs and settings, discovery and recommendation records, Terms and Policy records, sign-in session information, notification content and the times notifications were sent, delivery route information, the connection country, report details and the information copied when a profile is reported are added to the processed information (Section 2). (5) The legal grounds for legitimate-interest and legal-obligation processing and for Users outside Korea are completed (Section 3(3) and (6)). (6) The cleanup schedule, clearing of public letter text, periods for discovery and recommendation records, minimization of notification job records, deletion timing for uploads and report material, the items and period (three months) of authentication access records, and the records remaining after account deletion and when they are deleted are stated to match actual processing (Section 4(1), (3) and (4)). (7) Account deletion starting immediately on request, and how Apple and Google sign-in connections are handled, are explained (Section 4(2)). (8) Letters that failed to send and remain in the device outbox, and public letter drafts left on the device, are described (Section 4(5) and Section 8(2)). (9) Information shown or delivered to Members in other countries is described as disclosure between Members and removed from the international transfer table; there is no separate overseas-transfer consent step (Section 5(5) and Section 7). (10) Gmail and GitHub Pages are described as independent providers, and the notice emails the Operator sends through Gmail and Supabase’s subprocessors and level of protection are stated (Section 6 and Section 7(2) and (3)). (11) The method, procedure and effect of refusing each international transfer are set out (Section 7(4)). (12) The scope of location processing and the connection-country check are explained (Section 8(1) and (4)). (13) Do Not Track signals, the categories of safeguards, non-collection of resident registration numbers, automated blocked-term checks and additional uses are addressed (Section 9(4), Section 10(1), Section 12(2) and Section 13(1) and (3)).