Four calls carry the storage backend of an index between the phone and the account. They move credentials, sealed on the account's side; they never move a photo, and nothing at Opensolr ever connects to the storage.
photos_storage_getphotos_storage_savephotos_storage_qualityphotos_storage_deleteAll four go to https://opensolr.com/solr_manager/api/ as a form with email, api_key and core_name, like photos_sync_info. Only the owner of the index is answered; anyone else gets NOT_OWNER_ERROR.
- One row per index: the kind, the name, the quality, and the fields sealed with a key kept on the server outside the web and the database. When that key is missing the account answers not ready and refuses to save.
- The row goes when the index is deleted.
- Nothing about the files: no list, no count, no checksum. Those live in your storage. See what is written into your storage.
Not through Opensolr: with the credentials above, straight to the bucket or the folder. S3 over HTTPS with signed requests, WebDAV over HTTPS. Files, 720 px copies and the manifest; nothing else. See backup.