This is a reference translation. The Japanese version is the authoritative one; if they differ, the Japanese version prevails. 日本語版(正本)

Privacy Policy

The operator of Flockr (the “App”) handles users’ information as follows.

1. Operator and contact

  • Operator: 8M Software
  • Contact: hello@8m-software.com (please include “Yaoyorozu” in the subject.)
  • Established: October 19, 2026

2. Information we receive

If you sign in with a Google account, we receive the following information from Google.

  • An ID that tells accounts apart (not stored as is: it is combined with a secret value and stored as a different ID)
  • Email address
  • Name
  • Profile photo URL

The permissions the App asks Google for are:

  • Sign-in information (openid, email, profile)
  • The Google Drive “drive.file” permission: it lets the App read and write only the files the App created. It cannot see the rest of your Google Drive.

If you do not sign in, the only thing the operator receives is the server’s access log (see 7).

3. Purposes of use

  • Keeping you signed in, and telling accounts apart
  • Showing your name and photo in the App’s account menu
  • Saving what you write to your Google Drive, and reading it from there

We do not use it for any other purpose.

4. What you write (Seeds, photos, videos, Tags, Flocks)

  • Your content (Seeds, photos, videos, Tags, Flocks) is sent directly from your browser to your own Google Drive. It does not pass through the operator’s server.
  • The operator does not view or use your content.
  • If you do not sign in, your content is stored only in your browser (IndexedDB) and is not shared with other devices.
  • If you do not sign in, your content may be lost, for example when the browser’s data is cleared. Because storage depends on how the OS and the browser work, the operator cannot guarantee it.

5. Information stored on the operator’s server

When you sign in, the following information is stored on the operator’s server, one file per sign-in.

  • The ID that tells accounts apart, email address, name, photo URL
  • Refresh token, access token (valid for about 1 hour), expiry time

It is kept as follows.

  • It is kept in a non-public location, fully encrypted (AES-256-GCM).
  • It becomes invalid 30 days after it was last used. Expired files are deleted by the clean-up that runs the next time anyone signs in, so the actual deletion may come later than 30 days.
  • When you sign out, the file of that session and the cookie are deleted. If you were already signed out because the session had expired, the file is deleted by the clean-up after its expiry.
  • Signing out does not revoke the permission you gave on Google’s side. To remove it, revoke it in your Google Account settings (see 9).

The operator does not use the refresh tokens kept on the server to read the contents of your Google Drive.

6. Information stored on your device

  • Cookie: only one, app_session (to keep you signed in). It holds a random session ID, is valid for 30 days, and is extended each time it is used. The introduction pages do not use cookies.
  • Storage in the browser (localStorage, IndexedDB, Cache Storage): the choice on the first screen, recent searches, display settings, what you write, and the App’s files for offline use.

7. Logs

  • Each time a sign-in starts, the sign-in process records the time and two marks sent by the browser (whether it was started by a tap on the screen, and whether it came from the same site). On an error, it records the time and the reason for the error. It does not record names, email addresses, IDs or IP addresses.
  • The server the operator uses (Xserver) keeps a standard access log (date and time, IP address, requested URL, browser type) for operation and security. It is kept for about 30 days; older logs are not kept.

8. Disclosure to third parties and external services

  • We do not sell or provide users’ information to third parties, except where required by law.
  • The only external service the App communicates with is Google (the sign-in screen, Google Drive, and fetching the profile photo). We use no analytics tools, ads or external scripts.
  • The App’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

9. Deletion and revoking access

  • When you sign out, your information stored on the server is deleted. However, if your sign-in has already expired, or if you cleared the cookie, the file remains and is deleted by the clean-up after its expiry.
  • Your Google Drive content is in your own Drive. You can delete it in Google Drive.
  • You can revoke the App’s access to your Google account at any time in your Google Account settings.
  • The information on the server is encrypted, and the operator has no way to look for a particular person’s file. To be sure it is deleted, sign out and revoke access as above. If anything is unclear, please contact us at the address above.

10. Changes

When we change this policy, we will announce it on this page.