Privacy policy
Last updated 14 October 2026
The short version
Strixeo watches a wildlife feeder and tells you what turned up. To do that it keeps the photographs it takes and a few lines about each visit, for 30 days, and then deletes them.
There is no account. We never ask for your name, your email address, or your location, and nothing we store is derived from them. So the database holds nothing that names you.
It is not quite the same as saying you could never be identified, and we would rather be exact than reassuring. Two things you control could carry your identity into it: a photograph, if a person is in frame or the place is recognisable, and the name you type for a feeder, which we store exactly as you type it. Neither is something we can strip out without throwing away the thing itself.
What the app keeps on your phone
The feeder phone stores, in the app's own private storage:
- the photographs it captures, and the temperature map of each one;
- a record of each sighting — species, confidence, time, how long the animal stayed;
- its own event log, for diagnosing faults.
Species identification happens on the phone, offline. No photograph is sent anywhere to be recognised — the model runs on the feeder phone and the answer never leaves it. The photograph itself is a separate matter: it is sent to our server, so the alert can show you the animal while you are away from the feeder. That is described below, and it is deleted after 30 days.
None of what the phone keeps is readable by other apps, and uninstalling the app removes all of it.
The app does not read your photo gallery, your contacts, your messages, or your location.
What the app sends to our server
So an alert can reach your pocket when you are away from the feeder, the feeder phone sends
each sighting to our gateway at api.strixeo.com:
| What | Why |
|---|---|
| The photograph | So the alert can show you the animal |
| Species, confidence, description | So the alert can name it |
| When it happened, and your clock's offset from UTC | So the alert reads in your local time |
| The feeder's four-character code, and the name you gave it | So you know which feeder it was |
| A visit id, how long the visit lasted, peak and mean temperature | So one visit makes one alert, and a photograph leads back to its data |
| The sound label, if a sound triggered the capture | So you can tell a real trigger from a false one |
Two further things are stored about the devices themselves:
- A pairing code — the short code you type to connect a pocket phone to a feeder. It identifies the pair and nothing else, and is not derived from anything about you.
- A Firebase Cloud Messaging token — the address Google uses to deliver a push notification to one installation of one app. It changes when you reinstall.
We also keep a record of feeder faults — camera lost, feeder gone quiet — so the app can tell you something is wrong.
This website
Reading these pages contacts nobody but us. No analytics, no cookies, no
scripts of any kind, no embedded video, no social buttons. The typeface is served from
strixeo.com along with everything else, so your browser makes no request to any
other company while you are here.
Until 23 October 2026 the typeface came from Google’s font service, which meant Google received your IP address and the address of the page you were reading. It does not any more, and saying so here is the point of saying it at all.
One thing the web server does record, because every web server does: an access log line per request, holding your IP address, the page, the time and your browser’s description of itself. It is how a broken link or a flood of requests is noticed at all. It is never joined to a sighting, a feeder or anything else in this policy, and nothing reads it but us.
They are capped at a rolling window of roughly the last 13,000 requests, after which the oldest are discarded automatically. When this section was first written on 23 October 2026 they were not capped at all and would have lasted as long as the server did; that was said here, and then fixed the same day.
The same cap was put on the two other things that write logs on that machine, both of which are about the app rather than this site: the gateway, whose lines carry feeder codes and sighting references, and the relay that carries a live view, whose lines name which two phones were connected. Neither is read by anything but us, and both now roll away on their own instead of accumulating.
The name you give a feeder is free text that you choose, and we store it as typed. If you put your home address in it, we will be storing your home address — so please don't.
How long we keep it
Sightings and their photographs: thirty days. A sweep runs on the server and deletes anything older, photographs included. It is automatic; you do not have to ask.
The other three are not sightings and are not on that clock, so here they are separately:
- The pairing record and its push token — which feeder sends to which phone, and the address Google delivers to — are kept for as long as the pairing exists. There is no automatic expiry on them. When you reinstall and your phone registers a new token, the row holding the old one is deleted as the new phone claims it. Otherwise they go when you ask us, below.
- Fault records — camera lost, feeder gone quiet — are not deleted at all, and that is deliberate rather than an oversight. A fault is two short strings about a device, and the pattern across months — this feeder loses its camera whenever it rains — is the only thing that will ever explain the faults that are not a loose cable. They are deleted on request with everything else.
Deleting it sooner
There is no account to close, so there is nothing to cancel. If you want what we hold removed before the thirty days are up, write to support@strixeo.com with your feeder's four-character code and we will delete it. While Strixeo is in testing this is done by hand, so allow a few days; you will get a reply confirming it is gone.
Deleting the app from the feeder phone removes everything stored on that phone immediately.
Live video
When you tap to look at a feeder live, the video travels directly between your two phones wherever the network allows it. When it does not — which is most mobile networks — it is relayed through Cloudflare's TURN service to get past the carrier's firewall.
The relay passes the stream through. It is not recorded, by us or by Cloudflare, and we store it at neither end. Cloudflare's handling of traffic crossing its network is governed by their own privacy terms.
Who else sees any of this
- Google Firebase Cloud Messaging delivers the push notification, so it necessarily handles the notification and the token it is addressed to.
- Cloudflare, for live video only, as above.
- Hetzner, in Germany, host the server the data sits on.
We do not sell anything to anybody, and we share nothing for advertising. There is no advertising in the app.
Children
Strixeo is not directed at children and collects nothing that would identify one.
Changes
If this policy changes in a way that affects what we collect, the app will say so before the change takes effect, and the date at the top of this page will change.
Contact
support@strixeo.com — a real person reads it.