Privacy notice
Add to Semble is a small, open-source iOS app. It has no server, no analytics and no accounts. The developer collects no data about you.
On your device
The app stores your AT Protocol tokens, and the DPoP key that protects them, in the iOS Keychain. Only the app and its share extension can read them. They stay on this device: they are not included in backups and do not move to a new phone. The tokens go only to your own PDS and its authorisation server.
Signing out asks your authorisation server to revoke the tokens, then deletes them from the device. If the device is offline at the time, the tokens are still deleted but the server is not told.
Deleting the app does not delete them straight away. iOS keeps Keychain items after an app is removed, where no other app can read them. If you install the app again, it deletes them the first time it opens. To be sure they are revoked and gone, sign out before you delete the app.
If a link is saved while your device has no connection, the app keeps it — the link and its preview, your note, the collections you chose and any new collection's name — in its private on-device storage until it can be sent to your PDS, then deletes it. The app keeps the list of your collections, and of the shared collections you added links to, the same way. Thus the app still works offline. The app replaces each list when it gets the list again. Signing out does not remove these. Deleting the app does.
Who the app contacts
The app connects to these services and to no others.
- Your PDS and its authorisation server, to sign in, to write the records you save, and to revoke your tokens when you sign out. Your account decides which servers these are.
-
plc.directoryandpublic.api.bsky.app, to turn your handle into the address of your PDS. The app also usesplc.directoryto find the PDS of a person who owns a shared collection. (An account with adid:webidentity is looked up on the site that identity names instead ofplc.directory.) If that fails, the app asks the website your handle is named after instead (foralice.example.com, that isalice.example.com). These look-ups are public. They use no credentials. -
api.semble.so, for the link preview and for shared collections. These requests use no credentials.
For the preview, the app asks Semble's publicnetwork.cosmik.card.getUrlMetadataendpoint for a title, a description and an image. It sends only the link. Semble then fetches the page itself.
For shared collections, the app asks Semble for the open collections of other people that you added links to. It sends your account identifier (your DID). When you search your collections, the app also sends the search text to Semble, to find open collections from other people.
A link with a query string (?…), a fragment (#…) or a username in it might carry something private, such as a sign-in code. For those links the app sends nothing until you tap Load preview. - The PDS of the owner of a shared collection, when you choose that collection. The app reads the public record of the collection, because the link to it must refer to that record. This request uses no credentials. It tells that server which collection you chose.
- The site that hosts the preview image, to show its thumbnail. The linked page chooses this site, so it can be any site. Your device fetches the image directly, over https only, so that site sees your IP address, as it would if you opened the page.
What you publish
The app writes your link, your note and your collections as records in
your AT Protocol repository. Those records are public. Semble's own apps
publish the same records. The app writes only to the
network.cosmik.* collections that the
network.cosmik.authFull permission set allows.
What the app does not collect
- No analytics, no crash reports and no telemetry.
- No advertising identifiers.
- The app sends nothing to the developer.
Questions
Read the source code to check all of the above. Open an issue if something is unclear.