Privacy Policy
Effective: 2026-11-02
This policy explains how Sakyti handles personal information on our website https://sakyti.com, in the client portal at https://app.sakyti.com, and in email with us (together, the "Service"). It is written for Japan's Act on the Protection of Personal Information ("APPI") and, where they apply, the EU General Data Protection Regulation and the UK GDPR ("GDPR").
Sakyti is a business-to-business service. Most people whose information we hold are staff of game and app studios that use the Service.
1. Who we are
Sakyti is run by Ignas Vilimas, a sole proprietor (個人事業主) in Japan.
- Address: provided without delay on request (email [email protected])
- Email: [email protected] (general questions: [email protected])
We are the business handling personal information (個人情報取扱事業者) for the information described in sections 3.1, 3.2, 3.4, 3.5, 3.7 and 3.8, and its controller under the GDPR.
2. Your content and our role
Customers upload game and app text, glossaries and reference files, and write comments and answers in the portal ("Customer Content"). If Customer Content contains personal information, the customer decides what is in it and we handle it on the customer's behalf, to perform the customer's orders and to test and improve the Service as our Terms (section 8) allow. Under the APPI this is handling entrusted to us (委託) by the customer. Under the EU GDPR we are the customer's processor; our Data Processing Addendum is available on request and applies once we have confirmed it to the customer by email. It covers the EU GDPR only; customers who need UK GDPR terms should ask us.
3. What we collect
3.1 Website visitors (sakyti.com)
- Our website uses no advertising or tracking cookies. It counts visits with Cloudflare Web Analytics (section 3.7).
- If you turn on the page's sound, your browser remembers that choice in its local storage (section 11).
- Links to Discord and to email open those services; what you share there is handled under their own terms.
3.2 Account and business contact data (portal)
- Email address, password (we store only a one-way hash), display name, workspace (organization) name, preferred language.
- Invitations: the invitee's email address and a label.
- Security records: sign-in times, failed sign-in times, account lock state, and a log of account and file actions (who did what, and when).
- The country of the workspace's head office, which we ask for when a workspace is created or before its first paid order.
- If you start signing up but do not confirm your email address, we keep the pending sign-up (email, password hash, workspace name, language) until you sign up again with the same address or ask us to delete it.
3.3 Customer Content
Uploaded files and their names, sizes and check results; files you import from a Google Docs or Google Sheets link (we fetch only the public export of a document shared with "anyone with the link"); project names and guidelines; the translations, reports and delivery files we produce; your comments on strings and our replies; your answers to clarification questions; the project memory kept for each project (section 2 of our Terms); and usage figures such as string and token counts.
3.4 Bug reports
When you report a problem from the portal, we store what you write, your account and workspace, and technical details such as the page address, your browser and recent portal pages and errors in that tab. We do not record what is shown on the page or what you typed into forms. We also email a copy, with your name and account email, to our support mailbox (section 7).
3.5 Email with us
When you email [email protected] or [email protected], we receive your email address, name and whatever you write. The portal also sends you service emails (address confirmation, password reset, invitations, and notices that a delivery is ready or needs your attention).
3.6 Technical data
Our servers and our network provider record technical data such as IP address, browser information, the page requested and the time, to deliver and protect the Service.
3.7 Visit and sign-up statistics
We count visits to our website, and completed sign-ups, with Cloudflare Web Analytics. It sets no cookies and builds no profile. It receives the page address, the referring page, browser and device type, page-load timing and the country derived from your IP address. We see only totals.
3.8 Payments (workspaces on a Paid Plan)
Paid orders are paid by card through Stripe, our payment provider. Card details are entered on Stripe's page and go to Stripe; we never receive card numbers.
- What Stripe holds: the card details, the billing name, email address and billing address entered on its page, and a business tax ID if you give one. Stripe shows us the card's brand and last four digits.
- What we keep for each payment: Stripe's references for the customer and the payment, the order, the amount, the state of the payment and its times, the country of the billing address, and the country that issued the card.
4. Purposes of use
We use personal information to:
- create and manage accounts and workspaces, and sign you in;
- provide the Service: check files, translate, answer your questions and comments, and deliver results;
- send service emails;
- answer inquiries and bug reports, and give support;
- keep the Service secure, prevent misuse, and investigate problems;
- bill paid orders, keep accounting records, and keep the evidence of where each paying customer is established that tax law asks for (the head-office, billing-address and card countries);
- run, test and improve the Service, using usage figures, the visit and sign-up statistics in section 3.7, and Customer Content as our Terms (section 8) allow;
- tell account holders about changes to the Service, these policies or our Terms; and
- comply with law.
We will not use personal information beyond these purposes without your consent, except where the law allows. We do not use Customer Content to train AI models.
5. Legal bases (GDPR)
| Purpose (section 4) | Legal basis |
|---|---|
| 1–3: accounts, providing the Service, service emails | If you are yourself our customer (for example a sole trader), performance of our contract with you (Art. 6(1)(b)). If you use the Service for the organization you work for, our legitimate interest in providing the Service that your organization has chosen to use (Art. 6(1)(f)) |
| 4: support and bug reports | Our legitimate interest in answering requests and fixing problems (Art. 6(1)(f)) |
| 5: security and misuse prevention, server logs | Our legitimate interest in keeping the Service and its users safe (Art. 6(1)(f)) |
| 6: billing and accounting | Performance of the contract with the paying party (Art. 6(1)(b)) and legal obligations to keep records (Art. 6(1)(c)) |
| 7: running, testing and improving the Service | Our legitimate interest in running and improving the Service (Art. 6(1)(f)) |
| 8: notices of changes | Our legitimate interest in keeping customers informed (Art. 6(1)(f)), or a legal obligation where one applies (Art. 6(1)(c)) |
| 9: complying with law | Legal obligation (Art. 6(1)(c)) |
| Website (section 3.1) | Our legitimate interest in showing the website as designed (Art. 6(1)(f)) |
Where we rely on legitimate interests, you may object (section 12). For personal data in Customer Content covered by our Data Processing Addendum, we act on the customer's instructions as processor.
6. AI providers
Translation, file checks and replies to comments are done by AI models. Only the files and text in your projects are sent to them, not your account data, bug reports or email.
6.1 During the Free Pilot
For translation, and for testing and improving the Service as our Terms (section 8) allow, we use the service of OpenAI OpCo, LLC (United States) under OpenAI's own terms. OpenAI decides how it handles the content (it is a controller, not our processor) and may keep it for its own safety, security and legal purposes (OpenAI Privacy Policy). We have turned off OpenAI's use of our content for model training.
6.2 Paid orders
We use OpenAI's business service under its data processing addendum, as our processor. It does not train on the content.
6.3 Investigating problems
To investigate a problem with your account or order, we may use AI tools from OpenAI and from Anthropic PBC (United States) on the same basis as the Free Pilot: each provider is a controller, training is turned off, and the tools get only what the investigation needs (Anthropic Privacy Policy).
7. Who receives personal information
We do not sell personal information. We share it only:
- with service providers that run the Service for us (hosting network and security, email delivery, business email and backup storage, AI models, and payment processing), listed on our Subprocessors page;
- with Stripe, which also uses payment data for its own purposes, such as preventing fraud and meeting legal duties, under its own Privacy Policy;
- when the law requires it, or to protect life, body or property where the law permits; and
- with a successor to the Sakyti business, under this policy.
Inside your organization, members of the same workspace can see its projects, files and comments, as their permissions allow.
8. Transfers to other countries (APPI Article 28)
All of our providers are companies in the United States, except that we contract with Stripe through Stripe Japan, Inc., while Stripe processes payment data in the United States. Our providers may also handle data in other countries; our network provider handles traffic at the data center nearest the user.
Our measures, by provider:
- Providers acting for us (network and security, email delivery, business email and backups, OpenAI for paid orders, and Stripe for the processing it does for us): we rely on APPI Article 28(1) on the basis that each provider has, by contract, a system meeting the standards set by Japan's Personal Information Protection Commission (PPC) (基準適合体制). Each provider's terms limit its use of the data to providing its service, require security measures and confidentiality, and control its own subprocessors. We check these terms when we add a provider and at least once a year, and stop using a provider that no longer meets them. On request we will give you more information about these measures (APPI Article 28(3)). Card details and billing details are entered on Stripe's own payment page, so Stripe collects them from you directly; Stripe's use of payment data for its own purposes is governed by Stripe's Privacy Policy.
- OpenAI during the Free Pilot, and OpenAI and Anthropic when we investigate a problem (sections 6.1 and 6.3): these providers handle content under their own terms as controllers, so we rely on your consent (APPI Article 28(1)). You give it once, when you create an account, accept an invitation or accept our Terms in the portal: the page links to this policy, and by accepting it you consent to the transfers to the United States described in sections 6 to 8. The country is the United States (see "About the United States" below); the recipients are OpenAI OpCo, LLC and Anthropic PBC; each describes the measures it takes to protect personal information, including security, in its privacy policy linked in section 6. For personal information about other people in Customer Content, the customer must have their consent (our Terms, sections 5.3 and 7).
About the United States. According to information published by the PPC (survey of October 2021), the United States has no comprehensive federal law on the protection of personal information; sector-specific federal laws apply, such as the Electronic Communications Privacy Act, the Gramm-Leach-Bliley Act (financial institutions) and HIPAA (health information). The United States takes part in the APEC Cross-Border Privacy Rules (CBPR) system. In addition, several US states have their own privacy laws, such as California's Consumer Privacy Act.
For personal data in Customer Content that a customer sends us from the EU: Japan has an EU adequacy decision. We do not accept such data during the Free Pilot (Terms, section 5.3). When we pass it to providers in the United States, we do so under contracts that meet the PPC's Supplementary Rules.
9. How long we keep personal information
- Customer Content and account data: while your account is open. Deleted within 30 days after you ask or your account closes; backup copies within a further 30 days. We keep only records the law requires (for example accounting records) or that we need to settle a dispute.
- Payment records: as long as Japanese tax law requires (currently up to seven years).
- Removing a file in the portal hides it but does not erase it. To erase files, projects or your account, email [email protected].
- Bug reports and email: as long as needed to deal with them; deleted on request and with your account data.
- Server logs: kept for a limited time and overwritten automatically.
- Providers: AI providers, email providers and our analytics provider keep data under their own terms (sections 3.7 and 6).
10. Security measures (安全管理措置)
- Policy and rules: this policy is our basic policy, and written internal rules cover access, storage, transfer, deletion and incidents.
- Organization and people: a responsible person oversees personal information and incidents. Everyone with access is bound by confidentiality.
- Physical: equipment holding personal information is kept in Japan in access-controlled premises.
- Technical: access control, password hashing, separation of each customer's data, encryption in transit, protection of our servers against unauthorized access from the internet, and encrypted backups.
- Foreign environments: some of our providers handle data in the United States and other countries (section 8); we check the privacy rules there and take measures based on them.
11. Cookies and browser storage
The portal uses only two cookies, both necessary for it to work:
| Cookie | Purpose | Lifetime |
|---|---|---|
| Sign-in cookie | Keeps you signed in | 8 hours |
| Language cookie | Remembers your language choice | 1 year |
The portal also keeps a few items in your browser's storage: what you typed in a form when you switch language (never passwords or files), your choices while you set up an order, and the recent portal pages and errors in a tab, which are sent to us only with a bug report you submit. Our website keeps one item in local storage, to remember whether you turned the sound on.
Cloudflare may set a strictly necessary security cookie (such as __cf_bm) if it needs to check for automated traffic.
12. Your rights and how to make a request
Under the APPI you may ask us to notify you of the purposes of use of personal information we hold about you, to disclose it (including records of its provision to third parties), to correct, add to or delete it, or to stop using it or stop providing it to third parties. Under the GDPR you also have rights of access, rectification, erasure, restriction, portability and objection, and you may complain to your data protection authority.
To make a request, email [email protected] from your account's email address (or, if you have no account, the address the request concerns) and say what you want. If we need to confirm your identity further, we will ask. We respond without delay, electronically unless you ask otherwise. There is no fee. If your request concerns Customer Content that your organization controls, we will refer it to that organization or act on its instructions.
13. If something goes wrong
If personal information is leaked, lost or damaged in a way the APPI requires us to report, we report it to the PPC and notify the people affected. If it concerns Customer Content, we also tell the customer without undue delay.
14. Changes to this policy
We may update this policy. We post the new version here with its effective date, and email account holders about material changes before they take effect.
15. Contact and complaints
Questions, requests and complaints about personal information: [email protected]. Postal address: provided without delay on request (email [email protected]).