PRIVACY POLICY

Privacy Policy

This policy sets out how personal information is handled in Airffic World OS (the “Service”). Because we hold drone flight positions and building inspection data, information that cannot be taken back once mishandled, we state clearly what we collect and what we do not.

This is an English translation for convenience. If there is any conflict, the Japanese version prevails.

1. Information we collect

The Service collects the following information. We do not collect anything not listed here.

Account information

Email address and password (stored as a hash; we never keep the plain text). If you sign in with a Google account, we receive the email address, name and profile image provided by Google.

Aircraft information

The name of each registered aircraft, its aircraft ID (including Remote ID), and the date and time of registration. When entered in Airffic Flight: the aircraft registration mark, model, and pilot certificate number (optional).

Flight plans and flight logs (Airffic Flight)

The centre point, radius, maximum altitude, time window and purpose you enter as a flight plan. The position of the pilot's device during a flight (latitude, longitude, altitude, time) and the flight log built from it. Position is recorded only between the moment you press "Start flight" and "End flight", and only if you grant the device's location permission. While you are not signed in it stays on your device; when you sign in it is copied to our database as your own record.

Flight position data (telemetry)

Aircraft ID, latitude, longitude, altitude and timestamp.Of everything the Service handles, this requires the most careful treatment.A flight path can reveal where and when an operator works. We use it for flight operations management and for nothing else.

Inspection data

Property name, inspection ID, number of images, and the record of the inspection. A property name is treated as information that can identify the location of a building.

Organisation and billing information

Company name, plan in use, and monthly usage counts.We never hold credit card numbers.Payments are processed by Stripe, Inc.; the only thing we keep is the customer identifier issued by Stripe.

API keys

The key needed to use the pilot API. It is issued per user and visible only to that user.

Anonymous usage events

To find where people get stuck and fix the Service, we record: the path of the page you open (without the query part of the URL), the page you were on just before within the Service, the domain name of the referring site when you arrive from outside, the display language, whether you are signed in, the kind and time of actions such as "registered an aircraft" or "saved a flight plan", and a random identifier created on your device. When we compare two versions of a screen to improve it, we also record which version was shown.

This identifier is not linked to your account. We do not record location, registration marks, email addresses or anything you type. No cookies are used and nothing is sent to outside analytics providers (it is stored only in our own database). If your browser asks not to be tracked (Global Privacy Control or Do Not Track), nothing is recorded.

The other Airffic World sites (aircraft, port, pilot, market, operation, simulator, tobira, radiotelephony and study .airfficworld.com) record only the page-view part of this in the same way: the path of the page you open, the page just before it on that site, the referring domain, the display language and a random identifier made separately on each site. The identifiers of different sites are not linked to each other.

2. Information we do not collect

To avoid any misunderstanding, here is what we do not collect.

  • We use no third-party analytics tools at all.No Google Analytics and no other behavioural tracking tools run by outside providers. Usage is kept only by us, as the anonymous events described in section 1.
  • No advertising, and no tracking for advertising purposes.
  • Credit card numbers, security codes or bank account details.
  • The video footage captured by drones itself (we store only the inspection record).

3. Purposes of use

  • Providing the Service, verifying identity, and responding to enquiries from users
  • Managing flight operations, identifying aircraft, and preserving flight records
  • Producing, storing and delivering inspection results to users
  • Billing and invoicing based on usage
  • Detecting and preventing misuse
  • Improving the Service (limited to statistics that do not identify individuals)

If we ever need to use information beyond these purposes, we will ask for your consent again.

4. Third parties and external services

Except where required by law, we do not provide personal information to third parties without your consent. To operate the Service, however, we entrust the handling of information to the following providers.

  • Supabase — database and authentication infrastructure. Stores account information, aircraft information, flight position data and inspection data.
  • Stripe, Inc. — payment processing. Card details are collected directly by Stripe and never pass through us.
  • Mapbox, Inc. — map display. When map tiles are fetched, information about the displayed location is sent to Mapbox.
  • Google LLC — authentication when you sign in with a Google account.

These providers may operate servers outside Japan. Each handles information in accordance with its own privacy policy.

Sharing with people you choose.Records in the apps can be viewed by another person only when you choose that person (by email address) and the scope (which records in which app) in Sharing settings. By default nothing is shared with anyone. You can revoke sharing at any time, and the other person loses access the moment you do.

Airffic Circle and Airffic Chat.Your card (@handle, name, one line, tags, an area as text, a photo) is stored only if you create it, and can be looked up by @handle by any signed-in user. Posts and channel messages in a space are visible to that space’s members only; a direct message is visible to the two people in it (enforced by row-level security in the database). Attached photos are stored at unguessable paths and are visible to anyone who has the URL. There are no read receipts, typing indicators or notifications. You can delete your posts, messages and card at any time; deleting a space you created also deletes its posts and channels. The other person’s email address is used only to identify the recipient; we never tell you whether that person has an account. The recipient sees your display name, not your email address.

5. Retention and deletion

  • You can delete your account at any time from Settings → Delete account. Doing so immediately removes your account information, all app records, posts and photos, and cancels any paid plan. If you ask us to close the account by contacting us instead, it is deleted within 30 days of the request.
  • Aircraft information and API keys are deleted at the same time as the account.
  • Anonymous usage events are deleted automatically, every day, once they are more than 13 months old.
  • Flight position data and inspection data are kept for as long as the Civil Aeronautics Act or other laws require the records to be retained, or until you ask for them to be deleted.
  • Billing records are kept for the period required by law (in principle seven years).

6. Security

All communication is encrypted with TLS. Row Level Security is enabled on the database, sousers cannot read any data other than their own.Keys with administrative privileges are held as server environment variables and are never committed to the repository.

7. Requests for access, correction and deletion

You may request disclosure, correction, addition, deletion, suspension of use, or suspension of provision to third parties of your personal information. After verifying your identity, we will respond without delay, except where the law provides otherwise.

Please send requests to the contact address at the end of this page.

8. Third parties captured in footage

Drone photography can unintentionally capture third parties or their property. The Service does not store the footage itself, but when you take photographs we require, as your responsibility,that you obtain permission from the manager of the subject and respect the privacy of third parties.

9. Changes to this policy

This policy may be revised in response to changes in the law or in the Service. Material changes will be posted on this page and, where appropriate, notified to users.

Last revised: 2026年10月20日

10. Operator and contact

The operator of the Service and the contact point for matters concerning personal information are as follows.

Operator KIYOMINE(個人事業主)

Responsible person 清峰 強志(Tsuyoshi Kiyomine)

Address Yamato Bldg. 405, 1-6-16 Kanda-Izumicho, Chiyoda-ku, Tokyo 101-0024, Japan

Contactinfo@kiyomine.com

The legal notice under Japan’s Specified Commercial Transactions Act is the legally required Japanese-language notice with the operator details and prices.