SharePiPrivacy Policy
This translation is a draft. If it differs from the Japanese version, the Japanese version prevails.
Last updated: October 19, 2026
10dots (Kenji Koikeda) (the "Provider") sets out below how information is handled in the photo-sharing app "SharePi" (the "App").
Definitions
- Provider: the person who publishes the App on Google Play, shown as the "developer" on the Google Play store page: "10dots" (operated by Kenji Koikeda). The Provider only develops and distributes the App and does not operate any backend.
- Owner: the administrator of a group who contracts for their own cloud service (such as Google Cloud) and prepares and runs the backend and the storage for photos. The Owner is a third party separate from the Provider. The Owner is not the Provider's agent, employee or contractor, and the Provider neither manages nor supervises how the Owner operates.
- Member: a person who joins a group by invitation and uses the App.
1. How the App works (please read this first)
The App is not a service in which the Provider keeps your photos. Photos and group information are stored in a cloud service that the group's administrator (the "Owner") has contracted for themselves (for example, a Google Cloud project). The App is a tool for connecting to that storage (the "backend").
- The Provider does not receive, view or store photos, videos or rosters. They do not reach any server managed by the Provider.
- The backend is operated by the Owner of the group you join, not by the Provider. Management and deletion of photos and the conditions of their use are therefore the Owner's responsibility (sections 4 and 6).
2. Information obtained and stored
| Information | Handled by | Content and purpose |
|---|---|---|
| Google account identity (an ID token for authentication; by Google's design it also contains the email address and name) | Device → the connected backend | To sign in and to check permission to join groups. The ID token is issued by Google and verified by the backend. The backend does not store the email address or name; the roster holds only a keyed hash (a value that cannot be turned back into the original ID) made from the Google user ID |
| Session token | Connected backend → device | So that the ID token need not be sent every time. Valid for one day per backend, kept only on the device, and removed on sign-out and when the account is changed |
| Favorite folders and the photos and videos in them | Device → the Owner's backend | So that favorites can be restored after a reinstall or a new phone. Stored as your own file; not shown to other members, but the Owner can read it |
| Date and time of capture | Device → the Owner's cloud storage | To order photos and videos by when they were taken. Stored as metadata of each file |
| Share-link record | Device → the Owner's cloud storage | A list of the signed URLs of the photos and videos a share link points to. Deleted automatically about one day after it expires |
| Install referrer | Device ← Google Play | Read once, when the App was installed through a share link via Google Play, to open the preview of that link. Not sent to the Provider |
| Nickname | Device → the connected backend | To show who posted in the group |
| Photos and videos (and their reduced images and thumbnails) | Device → the Owner's cloud storage | What you choose and upload yourself, to share it in the group |
| Identifier of the poster | The Owner's backend | To show which member posted an item (stored as metadata of the photo) |
| Content of reports | The Owner's backend | So the Owner can review reports about inappropriate posts and users (section 9) |
| Paid-plan purchase status | Device ← Google Play | To determine the administrator's plan (member limit). The device only reads the purchase state held by Google Play; the Provider receives no purchase or payment information. Google Play processes the payment |
| Data on the device (group list, cache of reduced images, favorites, information on photos waiting to upload) | Device only | For the App to work. Not sent to the Provider or to the backend (favorite groups and events are kept only on the device) |
- Location, contacts and the advertising ID are not collected.
- The App contains no tools for usage analytics, advertising or crash reporting.
- The camera is used only to take photos and to read invitation QR codes. Photos and videos are chosen with Android's system picker.
3. Provision to third parties
- The Provider does not obtain this information and therefore does not provide it to third parties.
- The information in section 2 is sent to the backend operated by the Owner of the group you connect to. Members use the App knowing that their posts can be seen by the other members of the group they join (nickname, photos and videos they post).
- Signing in with a Google account uses Google's services. Google's handling of information follows Google's privacy policy.
- Even when a disclosure request is made under law, the Provider does not hold photos and the like, so what it can disclose is limited to the information it does hold (such as the content of inquiries).
4. The Owner's responsibility
The Owner who operates a backend is the controller of participants' information (nicknames, photos and videos, favorites, access records). The Owner manages the security settings of that cloud service, retention, deletion, and adding and removing participants. For how an Owner operates, please contact the Owner directly; the Provider cannot get involved. The Provider is not responsible for the upkeep, fees, security or other problems of the cloud service each Owner contracts for (see the disclaimer in the Terms of Use).
5. Storage location, period and safeguards
- Location: the cloud provider's region chosen by the Owner.
- Communication is encrypted with HTTPS. The backend returns only the information of groups you are allowed to join, and uses short-lived signed URLs to hand over photos.
- Retention: data is kept until the Owner deletes the group or the project. Deleted photos remain recoverable for a set period (30 days by default) through the cloud storage's soft-delete feature and are then permanently deleted.
- Data on the device is removed when you delete the App or change the account in the App. Caches on the device are deleted automatically: thumbnails after 30 days, the first frame of a video after 7 days, the medium-size image of a photo after 3 days (the newest 100 only), and video files after 7 days (at most 10). When you leave a group, that group's caches are removed immediately.
6. Requesting deletion and leaving a group
- To leave a group, use "Leave group" in the App. When you leave, your nickname and the hash linking your roster row to your Google account are erased from that group's roster, and your favorites file is deleted as well. Photos you posted earlier remain and are shown as "left member". If you also want your photos deleted, delete them yourself before you leave.
- If the Owner removes you from a group, or sharing is stopped because a plan ended, your roster row (nickname and so on) stays in the Owner's backend for moderation and for re-invitation or restoration.
- Photos, videos and rosters are deleted by the Owner of that backend. The Provider cannot access this data.
- For the details, see the Data Deletion Guide.
7. Children
The App is not intended for people under 13 (or the age set by the law of their place of residence).
8. Changes
If this policy changes, the change will be posted on this page and the last-updated date revised. Important changes will be announced in the App.
9. Reporting inappropriate posts
If there is a problem with a photo, a video or another user, use the App's report function. Reports go to the Owner of that group. The Provider cannot see the content of reports or the photos and videos posted.
10. Contact
Provider: 10dots (Kenji Koikeda)
Email: contact@studio10dots.com