AniAll
Privacy Policy
xperiy LLC (“we”, “us”) handles information in AniAll (the “service”) as described below.
The most important point first. What the service makes public is animal profiles and viewers (anonymous characters) — never your own name, e-mail address or the details of the service you signed in with. On the other hand, the photographs and videos you post can be read on the open web by people who do not use the app.
This English text is provided for convenience. The Japanese version is the controlling text.
1. Who we are and how to reach us
| Item | Detail |
|---|---|
| Controller | xperiy LLC (合同会社 xperiy) |
| Registered address | Ginza Otake Bizidence 2F, 1-22-11 Ginza, Chuo-ku, Tokyo 104-0061, Japan |
| Telephone | +81 70-8570-2173 |
| Privacy contact | info@xperiy.com |
Write to the address above, or use our contact form, for questions about this policy or to exercise your rights.
2. What we collect
| Category | What it is | How we get it |
|---|---|---|
| Sign-in details | The identifier issued by the authentication provider when you sign in with Apple or Google. This may include an e-mail address. | From the authentication provider at sign-in |
| Internal identifier | An identifier we issue for your account. We also issue a technical identifier to people who use the service without signing in, purely so that usage limits can be applied. It does not directly reveal your name or any other contact detail. | Issued automatically by the service |
| Animal profile and viewer details | Name, handle, species, breed, sex, country, date of birth, icon, bio, colour choice. | Entered by you |
| Posts | Photographs, videos, captions, tags, place name, visibility setting. | Entered by you |
| Interactions | Likes, reposts, comments, follows, blocks, saved posts. | Your actions |
| Device details | Push notification token, device type, language setting, app version. | Sent automatically by the app |
| Usage signals | The records used to order your feed (section 7). | Sent automatically by the app |
| Reports and enquiries | The target of a report, the reason and any free text. For the contact form: your name, e-mail address, handle, topic and message. | Entered by you |
| Quality and crash measurement | Statistics about how the app is used (screens shown, how long operations take, how long a video took to start, how many bytes were prefetched, how often playback stalled), your device model, OS version and language, the app version, an approximate region (the country or region inferred from your connection), and an identifier issued per device for measurement. This does not include your name, e-mail address, account identifier or post identifiers. | Sent automatically by the app (Firebase Analytics / Crashlytics) |
The e-mail address obtained when you sign in is held in Firebase Authentication, our authentication platform, and is not stored in the application database we run. The display name and profile picture you hold with Apple or Google are neither stored by us nor shown anywhere in the service, and other users cannot search for you.
IP addresses are used transiently at the delivery network (Cloudflare) to block excessive numbers of requests. They are not stored in the service's database. How long the logs produced by our processors' platforms are kept is governed by each processor's own defaults.
What you write in the contact form is sent to us by e-mail and is not stored in the service's database. The e-mail itself is, however, kept in the Google Workspace mailbox we use. Reports are likewise sent to that same mailbox so that we can investigate them.
We use Google's Firebase Analytics and Crashlytics for quality and crash measurement. These run on a separate platform from the database we operate, and the measurement identifier is separate from your account identifier. We do not use measurement records to identify individual users. Section 15 explains how to turn measurement off.
3. Why we use it
- To provide, display and deliver the service
- To authenticate you and check your permissions
- To prevent impersonation, automated bulk activity and other abuse
- To act on reports and keep the service safe
- To order posts in the feed and in Explore (section 7)
- To send push notifications and in-app notifications
- To reply to your enquiries
- To investigate faults and defects, and to improve the service (including measuring usage and performance — see section 15)
- To introduce, promote and advertise the service
- To comply with the law and respond to lawful requests
4. Legal bases (for users in the EEA and the UK)
Where the GDPR or the UK GDPR applies, we rely on the following legal bases.
| Processing | Legal basis |
|---|---|
| Creating your account, authentication, providing the service | Performance of a contract (Art. 6(1)(b)) |
| Preventing abuse, acting on reports, keeping the service safe | Legitimate interests (Art. 6(1)(f)) |
| Ordering posts (recommendations) | Legitimate interests (Art. 6(1)(f)) |
| Sending notifications (interactions and operator announcements) | Performance of a contract and legitimate interests (Art. 6(1)(b) / (f)). The device notification permission is a technical precondition; you can switch notifications off per kind in your device settings and in the app's notification settings |
| Quality and crash measurement (section 15) | Legitimate interests (Art. 6(1)(f)). It excludes your name, e-mail address and account identifier, and is limited to statistics and fault investigation. You can turn it off as described in section 15 |
| Keeping records required by law and answering lawful requests | Legal obligation (Art. 6(1)(c)) |
Where we rely on legitimate interests, we have weighed that interest against your rights and interests before proceeding. If you want to object, write to the contact in section 12 (GDPR Art. 21).
There is currently no kind of notification whose purpose is advertising or promotion. Every push notification, including operator announcements, can be switched off per kind; switching one off still leaves the entry in the app's Activity list. Notifications about a report we received, an enforcement action and the outcome of a review cannot be switched off, because we have to tell you about them. Of these, notifications about an enforcement action are also sent as a push notification in addition to being shown in the app (the reason for the action and how long it lasts are never included in the push notification — we show those only inside the app). Notifications about a report we received and about the outcome of a review are shown only in the app and send no push notification.
5. What is public and what is not
The service draws a deliberate line between what is published and what is not.
| Public (readable by anyone, including people who are not signed in) | Not public |
|---|---|
| Animal profile and viewer details, handles, follower / following / post counts, and whether the profile is suspended | Your name, your e-mail address, and the display name and profile picture held by the service you signed in with (we do not store these) |
| Published posts: photographs, videos, captions, tags, place name, publication time | Your saved posts, notifications, app settings and device registrations |
| Likes, reposts, comments, follow relationships | The usage signals behind recommendations and the interests inferred from them (section 7) |
| Announcements from us | The content of reports, who reported, and our record of the action taken |
The public record of an animal profile or viewer technically contains an internal identifier for the account that created it. That identifier does not reveal your name or e-mail address, but it does mean a third party may be able to infer that several animal profiles are managed by the same person.
A post set to private is not shown in the service or on the share pages. As described in the next section and in section 14, however, that does not prevent someone reaching the underlying photograph or video file.
6. Location data and information embedded in photographs
- 1.When you add a place to a post, the only thing stored is the name of that place. We never receive or store its latitude and longitude, its address, or any venue identifier. Your current location is used solely to list nearby candidates, and that query is made to Apple's map service at that moment; its contents are never sent to us.
- 2.The name of the place is published as part of the post, in the same way as the caption. As described in section 5, it can therefore be read on the web by people who do not have an account. You can still choose a place by typing its name if you do not allow access to your location.
- 3.Photographs are re-encoded twice: once when the app exports them from your device, and again when our server receives them. That removes embedded information such as the capture location (GPS) and the camera details. The original file is never published as it is.
- 4.A photograph for which that processing does not complete successfully is not published.
- 5.For videos, the app strips information not suitable for sharing when exporting from your device, and our server validates the file's structure. Because the server does not re-encode videos, we do not guarantee that every piece of embedded information has been removed. If you do not want a video to carry location data, please check your camera settings.
7. Recommendations and usage signals
To decide the order of your feed we keep the following records.
| Record | What it is | How long we keep it |
|---|---|---|
| Confirmed actions | Likes, saves, reposts, follows, comments, reports, blocks, and the undoing of any of these. | Held as inferred interests (below) |
| Display and dwell | That a post appeared on screen, the cumulative time it was visible, and whether a video played to the end. | Held as inferred interests (below) |
| Inferred interests | How strongly you appear to be interested in each species, and whether you tend to prefer photographs or video. | Kept while you use your account, with the strength of each interest decaying over time (a 30-day half-life). That does not mean the record itself is deleted after 30 days. Entries whose influence has become small enough are dropped from the record, and the whole record is erased when you delete your account |
| Already-seen record | Post identifiers and the time they were shown, so the same post is not shown repeatedly. | 7 days (up to 500 entries) |
- 1.The inferred-interest record is stored where no user — including you — can read it. It is never shown to other users.
- 2.What the app sends contains no species and no post content: only the post identifier and the kind of action. All inference happens on our servers.
- 3.We do not keep the individual actions or impressions themselves. What we receive is folded into the summarised figures above and then discarded — except the already-seen record, which we keep for the period shown above so that the same post is not shown repeatedly.
- 4.For confirmed actions such as likes, our server checks that the underlying record actually exists before it affects the inference. A claim from the app alone has no effect.
- 5.This processing decides the order of posts. It is not automated decision-making that produces legal effects concerning you or otherwise significantly affects you.
- 6.There is currently no setting to switch off the collection of these usage signals. The records are erased when you delete your account.
8. Sharing and processors
We do not sell the information we collect, and we do not provide or share it with third parties for advertising. We engage the following processors in order to run the service.
| Processor | Role | Information handled |
|---|---|---|
| Google LLC (Firebase / Google Cloud) | Authentication, database, server execution, app attestation, push relay, logging | Sign-in details, internal identifiers, profiles, posts, interactions, device details, usage signals |
| Google LLC (Firebase Analytics / Crashlytics) | Measuring how the app is used and investigating crashes | The quality and crash measurement records (the last row of the table in section 2) |
| Cloudflare, Inc. | Storage and delivery of photographs and videos, web page delivery, the search index, rate limiting | Photograph and video files, parts of public profiles and public posts, the requesting IP address (transiently) |
| Google LLC (Google Workspace) | Sending reports and contact-form enquiries to us by e-mail | The content of reports and enquiries |
| Apple Inc. | App distribution, push delivery, payment for any future paid service | Push notification destination, payment details (we never receive card details) |
We put the necessary agreements in place with our processors and limit their handling to the purposes set out in this policy. If we change this set of processors we will update this policy.
In addition, we may disclose information to the extent necessary where the law requires it, where there is an urgent need to protect someone's life, body or property, or in connection with a transfer of the business.
9. International transfers
- 1.The database and server processing run principally on infrastructure in Japan (Tokyo). Photographs and videos are stored on infrastructure in the Asia-Pacific region.
- 2.All of the processors named above are based outside Japan, and information may be handled outside Japan for support, auditing and similar purposes. Data protection regimes in those countries may differ from Japan's.
- 3.Where we transfer the personal data of users in the EEA or the UK outside those territories, we use whichever lawful transfer mechanism fits the destination and the processing — an adequacy decision, standard contractual clauses, or another lawful means.
- 4.Where we entrust the handling of personal data to a third party located outside Japan, we select processors that have put in place arrangements conforming to the standards set by Japanese data protection law.
- 5.Write to the contact in section 12 if you would like information about the data protection regime of the destination country or about the measures our processors take.
10. How long we keep things, and what survives account deletion
We do not keep information for longer than is needed for the purposes above.
Even if you do not delete your account, the following are removed with time.
| Category | How long we keep it |
|---|---|
| A post you deleted yourself | 30 days from when you deleted it. The photo and video data are erased promptly; the caption, tags, comments and likes are removed once the 30 days have passed. The window exists so that an accidental deletion can be looked into. If the post falls within the preservation described in section 11, that section's period applies instead. |
| Entries in Activity in the app | 90 days from when that event last happened. Only the most recent entries are shown on screen. |
| Media preserved as the basis for an action | As set out in section 11 (180 days as standard). |
When you delete your account, this is what happens.
| Category | After deletion |
|---|---|
| Your account, animal profiles and viewer | Deleted, including the record held by the authentication provider. |
| Your own posts (photographs, videos, captions, tags, place names) | Deleted, and the photograph and video files are erased. |
| Handle reservations, saved posts, notifications, settings, device registrations, recommendation records | Deleted. |
| Likes and reposts you left on other people's posts, and the text of your comments | Retained. The display name, handle and icon are removed; all that remains is the animal profile's internal identifier. That reduces the link to the closed account, but depending on what a comment itself says the link cannot always be removed entirely. We keep these so the counts shown on the service stay consistent. |
| The animal's display name and the thumbnail reference recorded in other users' notifications | Retained, because we do not rewrite every user's notification history. The photograph files are erased, so no image is shown. |
| Follow relationships recorded for other users | Retained (the animal profile's internal identifier only). |
| The content of reports, the identifier of the reporting account, and our record of the action taken | Retained for as long as we need them, in order to prevent abuse, recognise repeated breaches, respond to challenges against our decisions, and keep the service safe. We review that need periodically against the kind of record, the seriousness of the breach, the likelihood of recurrence, whether an investigation or dispute is still live, and our legal obligations, and we delete or anonymise what we no longer need. Users cannot read them. |
As set out above, some records survive deletion. They do not reveal your name, e-mail address or any other contact detail, but reports and enforcement records do contain internal identifiers. If this concerns you, write to the contact in section 12.
Deletion is processed in stages. When you delete your account from the app, completing the process can take up to about a day.
11. Media preserved as the basis for enforcement
- 1.When we hide or remove a post, we copy the photograph or video to a separate area that cannot be reached from outside, so that the decision can be reviewed afterwards, and we keep it for 180 days as a rule.
- 2.We may keep it for longer than 180 days where an investigation is ongoing, where someone has disputed the decision, or where the law requires it to be preserved.
- 3.Despite the above, if you delete the post yourself or delete your account, the copy is deleted even while preserved. Our enforcement never takes precedence over your own request to erase.
- 4.However, in the cases below we may keep the post and the records attached to it (caption, tags, comments, the content of reports) for a defined period after you have deleted it. The grounds are limited to these three.
- 5.(a) An investigation under way — where, at the time of deletion, a serious report about that post (a report about cruelty to an animal, or reports from several people) was outstanding or under review. Unless we specify otherwise, we keep it for 30 days and it is then deleted automatically.
- 6.(b) Answering a legal claim — where it is necessary in order to deal with a legal claim, a dispute or an enquiry from an authority, whether ours or a third party's.
- 7.(c) A statutory retention duty — where applicable law requires us to keep it.
- 8.For any such retention we record the ground, the end date and a review date, and we reconsider whether it is still needed on the review date and when the end date arrives. We delete it promptly once it is no longer needed. There is a maximum period; we do not keep anything indefinitely. While it is kept, access is limited to the staff described in the next paragraph.
- 9.The retention described in the paragraphs above is carried out only so far as the law allows. To ask whether one of your posts is subject to it, or to object to it, write to the contact in section 12.
- 10.Preserved media is stored in an area that ordinary users and outside third parties cannot reach. Only members of our team who have been granted access for investigation and safety purposes can view it, and they do so through a temporary URL valid for five minutes.
12. Your rights
You can make the following requests about your own information. Write to info@xperiy.com or use our contact form. We will act on them so far as we can verify that the request is yours.
- To be told the purposes for which we hold your personal information, and to be given access to it
- To have inaccurate information corrected, completed or deleted
- To have processing stopped, information erased, or disclosure to third parties stopped
- To ask us to restrict the processing of your personal data (GDPR Art. 18)
- To receive the information you provided in a machine-readable form (portability)
- To object to processing based on our legitimate interests
- To withdraw consent where processing is based on consent
- 1.Much of this you can do yourself in the app. Deleting posts, editing profiles, changing notification settings, unblocking and deleting your account are all available at any time.
- 2.If you live in the EEA or the UK you also have the right to lodge a complaint with your national supervisory authority.
- 3.For residents of California: we do not sell personal information and we do not share it for advertising. Requests to know, delete or correct are handled through the contacts above, and we will not treat you less favourably for exercising those rights.
- 4.The recommendation records described in section 7 sit in an area that no user — including you — can read from the app. If you ask for access to them, we will look them up and tell you what they contain.
- 5.How far each of these rights reaches depends on the kind of personal data, the purpose of the processing and the legal basis for it.
- 6.Because of how the service is built, there are requests we cannot fully meet — the items listed as retained in section 10, and the preservation described in section 11. Where that is the case we will tell you why.
13. Children
- 1.The service is not intended for anyone under 18, and we do not knowingly collect information from anyone under 18 (clause 5 of the Terms of Service).
- 2.When you sign in we ask you to confirm that you are aged 18 or over. That is your own statement; we do not ask for documents proving your age.
- 3.Where the law of the country or region in which you live sets a higher age for using a service like this, or for consenting to the handling of personal data, that higher age applies.
- 4.If we learn that we hold information about someone under 18, we will delete that information and the account promptly. Write to the contact in section 12 if you believe this has happened.
14. Security, and its limits
We take the following measures against loss, destruction and unauthorised disclosure.
- Encryption in transit
- Database rules that confine each user's reads and writes to what they are permitted
- Attestation that requests come from a genuine copy of the app
- Signing of server-to-server requests, and rejection of replayed requests
- Restricting access to the moderation console behind multi-factor authentication, with an audit record of every action
- A practice of never writing user identifiers, post text or e-mail addresses to our application logs
These are the limits of the current design. We state them plainly.
The URLs from which photographs and videos are delivered carry no authentication and no signature. They are hard to guess, but anyone who learns such a URL can retrieve the file regardless of the post's visibility setting.
- 1.When a post is deleted we normally erase the photograph and video files and invalidate the copies held in the delivery network within 15 minutes. Until that completes, and if it fails, the data may remain reachable for a period after deletion. We retry a failed invalidation repeatedly, but until it succeeds the file may stay reachable for up to one year.
- 2.We do not create backups of user content and we have no means of restoring information lost through a fault, a mistake or a defect.
- 3.The service does not automatically assess the content of the photographs and videos posted to it. Inappropriate posts are dealt with through reports and our review of them.
16. Changes to this policy
- 1.We may revise this policy. When we do, we publish the revised text on this page.
- 2.Where we materially change what we collect, why we use it, or who processes it, we publish the new text and the date it takes effect, on this page or within the app, a reasonable time before it takes effect. Where the law requires consent, we will ask you again.
Effective from 27 October 2026. Amended 8 November 2026.