Cue in your logs
Cue is picture-day photography software. It matches every photo to the person in it, by time.
Requests that name Cue come from its apps and services, working for a studio that uses Cue, or from our own tools. Cue is not a crawler, and calls only the services listed below.
The User-Agent header
Each request names the part of Cue that sent it, usually with its version. The apps add their operating system, and the computer app adds its processor type.
<name>/<version> (<platform>; +https://cue.photo/user-agent; api@cue.photo)
For example:
Cue-iOS/0.3.0 (iOS 26.0; +https://cue.photo/user-agent; api@cue.photo)Cue-Desktop/0.3.1 (macOS 26.0; aarch64; +https://cue.photo/user-agent; api@cue.photo)cue-backend/0.1.0 (+https://cue.photo/user-agent; api@cue.photo)cue-tools (+https://cue.photo/user-agent; api@cue.photo)
That is all it carries. It never names a person, an account or a studio, and never carries a device ID, a device model or a hostname.
Who sends what
Cue-iOS- The iPhone and iPad app. Calls the studio's photography provider and Cue's server at
api.cue.photo. Cue-Desktop- The computer app. Calls the studio's photography provider and uploads photos to it, calls
api.cue.photo, and checksdownloads.cue.photofor updates. cue-backend- Cue's server at
api.cue.photo. Calls the subprocessors Cue uses for sign-in, billing and email. cue-console- The account site at
app.cue.photo. Calls only Cue's own server. cue-clicue-toolscue-poc- Our own tools for building, testing and releasing Cue, run by our team. They also reach the hosts our build tools, releases and API documentation come from.
Contact
If a request from Cue is causing you trouble, write to us.
api@cue.photoIt helps to include the time and the header you saw.