sakyti Back to sakyti.com

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.

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)

3.2 Account and business contact data (portal)

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.

4. Purposes of use

We use personal information to:

  1. create and manage accounts and workspaces, and sign you in;
  2. provide the Service: check files, translate, answer your questions and comments, and deliver results;
  3. send service emails;
  4. answer inquiries and bug reports, and give support;
  5. keep the Service secure, prevent misuse, and investigate problems;
  6. 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);
  7. 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;
  8. tell account holders about changes to the Service, these policies or our Terms; and
  9. 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.

Purpose (section 4) Legal basis
1–3: accounts, providing the Service, service emailsIf 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 reportsOur legitimate interest in answering requests and fixing problems (Art. 6(1)(f))
5: security and misuse prevention, server logsOur legitimate interest in keeping the Service and its users safe (Art. 6(1)(f))
6: billing and accountingPerformance 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 ServiceOur legitimate interest in running and improving the Service (Art. 6(1)(f))
8: notices of changesOur legitimate interest in keeping customers informed (Art. 6(1)(f)), or a legal obligation where one applies (Art. 6(1)(c))
9: complying with lawLegal 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:

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:

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

10. Security measures (安全管理措置)

11. Cookies and browser storage

The portal uses only two cookies, both necessary for it to work:

Cookie Purpose Lifetime
Sign-in cookieKeeps you signed in8 hours
Language cookieRemembers your language choice1 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]).