Skip to main content
Pukae

Speak clearly. Connect with confidence.

TranslateTranslation historyPocket dictionaryDaily lessonsConnect Telegram
Developer APIMy account

Administration

Admin dashboardMember managementUsageManage API KeysNotice emailService settingsActivity log
가 អ A

Grow more confident with every phrase.

Pukae

PukaePukae / Privacy Policy
Connecting…
Sign inSign up
KoreanEnglish

Pukae privacy notice — Social sign-in and web accounts

Effective November 19, 2026

Read the full mobile app privacy policy

When you choose a provider

Selecting a provider takes you to its sign-in screen. Enter your provider password and any two-step verification code there. Once the provider confirms your identity, Pukae creates an account on your first visit or opens the account you previously created with the same provider and login. Email registration is also available.

Available providers depend on the interface language and each provider’s approval status. When a button is active, Pukae uses the following information.

ProviderIdentifier used for the accountProfile name
NaverMember identifier issued by NaverNickname, when supplied
Daum (Kakao Account)Kakao service user IDNickname, when supplied
Google · MicrosoftUser identifier in the authentication responseName, when supplied
AppleUser identifier issued for PukaeDefault profile name
Meta (Facebook)App-specific Facebook user IDName, when supplied
LINEUser ID issued for the LINE providerDisplay name, when supplied
TikTokUser ID issued for PukaeDisplay name, when supplied

The provider’s consent screen may mention other basic profile fields, such as a photo. Pukae stores the provider name, an account reference derived from its identifier, and your display name. If the provider supplies no name, Pukae uses a default name. You can change it in your account. Pukae does not automatically combine accounts based on a social email address.

Sessions and retention

Pukae exchanges an authorization code with the provider and uses its access token during sign-in. Provider access tokens are not stored in member profiles. Pukae combines the provider’s user identifier with the provider and app details and hashes them to produce the reference used to find your account. Pukae keeps this reference and your profile for the life of your account.

The website uses a sign-in verification cookie valid for up to 10 minutes and a Pukae session valid for up to 30 days. Signing out ends that session. On mobile, a single-use code valid for three minutes returns the browser sign-in to the app.

Web translation history and deletion

When you translate on pukae.com while signed in, you can revisit or delete the original text and its translation in your history. The free mobile mode manages its on-device history separately.

You can change your display name in your account. Choose the account deletion option and confirm your identity to delete your Pukae membership, associated web records, sessions and API keys. You can also manage Pukae’s authorization in your provider’s settings. If you cannot sign in or wish to request access, correction, deletion or restriction of processing, contact the LastAI operations team. Existing app privacy policy · Account deletion instructions

Who handles the data?

LastAI operates Pukae accounts. Your chosen provider handles authentication on its own service. LastAI hosts the Pukae web server on Vercel and uses Supabase to manage Pukae member profiles and sessions. Contact LastAI at holytasks@gmail.com or +82 70-8289-6001.

Pukae helps you find the right words
Terms of ServicePrivacy PolicyPukae API