Buyer Guides · 7 MIN

Working with an overseas software development partner as a Japanese company: APPI, copyright and documentation

How a Japanese company can work with an overseas software development partner: APPI cross-border rules, breach reporting, copyright assignment and documentation habits.

By NactorePublished 11 Nov 2026All articles

A Japanese company can work well with an overseas software development partner, but four Japan-specific points decide whether the engagement holds up. They are the cross-border rule in Article 28 of the Act on the Protection of Personal Information (APPI), the breach reporting timeline the Personal Information Protection Commission (PPC) expects, a Copyright Act rule that keeps some rights with the developer unless the contract names them, and the documentation habits Japanese teams rely on. This guide covers all four, with sources your legal team can check.

Key takeaways
  • APPI Article 28 restricts giving personal data to a third party in a foreign country unless the person has consented or the recipient has a system that meets PPC standards.
  • When relying on the recipient's system, the Japanese company must check it regularly and give information to individuals on request.
  • PPC guidelines expect a preliminary breach report within about three to five days and a final report within 30 days, or 60 days for attacks.
  • Under Article 61(2) of the Copyright Act, adaptation rights stay with the developer unless the assignment names them, and moral rights cannot be transferred at all.
  • Japan is 3.5 hours ahead of India with no daylight saving, which gives an afternoon overlap of about 4.5 hours.
  • Nactore is a technology and growth company based in India that works in written, documented steps, which fits how Japanese teams review and approve work.

Can personal data go to a development team abroad?

Yes, with a legal basis. Article 28 of the APPI governs giving personal data to a third party in a foreign country. The current English translation is linked from the PPC's laws and policies page. There are two main routes.

  1. Consent. The individual agrees in advance, after you give them information about the foreign country's data protection system and the measures the recipient takes.
  2. An equivalent system. The recipient has set up a system that meets PPC standards for handling data the way a Japanese business must, usually shown through a contract. You must then take steps to keep that system working and answer individuals who ask about it. Baker McKenzie's summary notes that you must regularly check both the recipient's measures and whether local laws could get in the way.

Some countries are treated as equivalent to Japan, which removes the Article 28 step. The PPC made that designation in January 2019 for the EEA countries, a list that then included the United Kingdom, as an Anderson Mori & Tomotsune bulletin explains. India is not on it. Do not assume the domestic exception for entrusting work to a contractor settles the question for an overseas team. Ask counsel which Article 28 route you rely on, and write it down.

The simplest answer is often to avoid the transfer. Build and test on masked or synthetic data, keep production in a Japan cloud region, and give engineers logged, named access only when needed.

What breach timeline should the contract support?

Since the 2022 amendments, a business must report certain incidents to the PPC. According to an IAPP analysis by Mori Hamada & Matsumoto lawyers, the triggers include sensitive data, possible financial harm, improper purpose and incidents affecting more than 1,000 people. For a company, the guidelines generally expect a preliminary report within three to five days of becoming aware, and a final report within 30 days, or 60 days where the breach was likely committed for an improper purpose such as a cyberattack.

Under the APPI, a contractor that informs the business that entrusted it with the data is excused from reporting to the PPC itself, so the report falls to you. That makes the contract's notice clause your early warning system. Set it in hours, not days, and name the person on each side who receives the call.

This is where many foreign-drafted contracts fall short. Article 61(2) of the Copyright Act says that if a transfer contract makes no particular reference to the rights in Articles 27 and 28 (translation, adaptation and rights in derivative works), those rights are presumed to stay with the transferor. A clause that simply says "all copyrights" may not be enough. Article 59 adds that an author's moral rights are inalienable.

So a Japanese-style assignment does three things. It assigns all copyrights "including the rights under Articles 27 and 28" by name. It includes the developer's agreement not to exercise moral rights against you. And it licenses any pre-existing tools the vendor brings. Our post on IP and data terms lists the related clauses.

Should the contract be ukeoi or jun-inin?

Japanese system development contracts usually take one of two forms, and the Information-technology Promotion Agency's model contract, second edition, addresses both, with a separate agile version built on quasi-mandate.

PointUkeoi (contract for work)Jun-inin (quasi-mandate)
What you pay forCompletion of a defined deliverablePerformance of the agreed work
Best fitScope fixed and known in advanceProduct that will change as you learn
AcceptanceInspection against the specificationSprint reviews and agreed reports
ChangesChange request and re-pricingReprioritize the backlog

Neither is better in general. Pick the one that matches how certain your scope is, and make sure an overseas partner understands which one it is signing.

What do Japanese teams expect in communication?

Mostly, writing. Agreement in a meeting counts only once it is in the minutes. A partner that works well with Japanese teams usually does the following.

  • Minutes after every meeting. Decisions, owners and dates, sent the same day, so nothing depends on memory.
  • Documents before code. A requirements definition and a design document reviewed and approved before the build starts.
  • A shared issue list. Open questions tracked in one place with status, rather than scattered across chat.
  • Early bad news. A risk to a date raised the day it appears, with options, never at the deadline.
  • A shared glossary. Japanese and English terms agreed once, so specifications do not drift in translation.

For security reviews, a written vendor security questionnaire fits this style well.

Pro tip

Ask a prospective partner to send minutes after your first call. Their quality, speed and accuracy predict the rest of the engagement better than any proposal.

How much working time overlaps with India?

Japan Standard Time is UTC+9 with no daylight saving, and India is UTC+5:30, so Japan is 3.5 hours ahead. An India team working 10:00 to 19:00 IST is online from 13:30 to 22:30 in Tokyo, so a 9:00 to 18:00 Tokyo office shares about 4.5 hours each afternoon. Exchange holiday calendars at the start, because Golden Week and Indian festivals fall at different times. More patterns are in working across time zones.

Frequently asked questions

Can a Japanese company use developers in India for systems with personal data?

Yes, if it has an Article 28 route, either informed consent or a recipient system that meets PPC standards with regular checks. Many projects avoid the question by using masked data in development.

Is a general "all copyrights are assigned" clause enough in Japan?

It may not be. Article 61(2) presumes the Article 27 and 28 rights stay with the developer unless the contract names them, so name them.

Should documents be in Japanese?

Contracts can be bilingual with a governing language clause. Working documents should be in whatever language your reviewers approve in, with a shared glossary.

Is this legal advice?

No. It is a plain-language guide with sources. Confirm your setup with Japanese counsel.

Write it down, then build

Japanese buyers reward partners who make decisions visible: the Article 28 route on paper, the Article 27 and 28 rights named in the assignment, and minutes after every call. Nactore builds and ships software, then helps it rank and grow, as one partner measured on your growth.

Planning a build with a team outside Japan? Book a free 30-minute call.

Want to apply this to your business?

Book a free 30-minute call. We will tell you what we would do first.