Privacy Policy
Clankie for iPhone and iPad is the native client for your own Mac-hosted agent. No agent runs in the cloud. Your Mac holds the conversations, terminal sessions, paired devices, and the grants each device has. The public gateway at api.clankie.bot is a relay that carries traffic between the phone and your Mac.
The app stores two records in the iOS Keychain. Both are marked device-only, so neither syncs to iCloud Keychain nor migrates to another device:
Messages, terminal output, and fleet state live on your Mac. The phone displays them and keeps no copy anywhere else. Three display preferences — menu density, skin, and the commons viewport — sit in ordinary app storage.
You scan a one-time pairing code shown on your Mac. The app then sends that code, a fixed device label (Clankie mobile), and the platform (ios) to your Mac through the gateway, so the Mac can list and revoke the device with clankie devices. It sends nothing else: no advertising identifier, no model or OS version, no contacts, and no location.
The gateway relays traffic between the phone and your Mac. It stores no message content, terminal bytes, or authorization headers, and writes none of them to a log. Its own log lines carry an opaque host id, a request id, the HTTP status, the response byte count, a duration, and connect and disconnect events.
The web server in front of it keeps a standard access log: client IP address, user agent, request line, TLS parameters, status, size, and duration. Both logs stay on that one machine and rotate by size. Nothing is shipped to an analytics or logging service.
TLS terminates on the gateway, which runs on AWS, before your Mac's outbound connection. The gateway neither records nor interprets what it carries, but traffic is not yet end-to-end encrypted between the phone and the Mac.
Notifications are optional. If you allow them, the app sends its Apple push token, its registration key, and your Mac's opaque host id to the gateway, which stores them so it can address a notification to your device. The token never reaches your Mac.
A notification carries no message content. Your Mac asks the gateway to wake a device for a conversation; the gateway sends a fixed alert reading New message along with the host and conversation ids, and the app then fetches the thread from your Mac over its normal authenticated connection. Apple sees the push token, the app's topic, those two ids, and the timing.
Turning notifications off in the app clears delivery: the push token and device id are erased. The gateway keeps the registration id, a hash of the registration key, and the counter, so that a stale request cannot switch delivery back on.
The camera is used only to scan the pairing QR code, and only while that scanner is open. Frames are not stored, written to disk, or sent anywhere; the app reads the decoded text and discards everything else.
The app can open your photo library so you can pick an image for a conversation. Sending image attachments is not finished in this release, so a picked image is resized inside the app's own sandbox and goes no further.
An email address is used only for your Mac's sign-in codes and as the account identity for remote access. You type it into Clankie on your Mac; the phone app never asks for, stores, or sends an email address. One-time codes come from Amazon Cognito through Amazon SES from a clankie.bot address. The gateway keeps only the pseudonymous account identifier from a verified sign-in, never the address itself. Disabling the account revokes remote access and ends the mail.
The app has no tracking, no advertising, and no analytics, attribution, or crash-reporting SDKs, and it sends nothing to any host except api.clankie.bot and your own Mac. The only third parties involved are the AWS services named above — Cognito and SES for sign-in codes, and the machine the gateway runs on — and Apple, for notification delivery. The app's iOS privacy manifest declares no tracking. It declares the two identifiers the notification registration involves — a device identifier and a user identifier — as collected for app functionality only, and nothing else.
The landing page at clankie.bot sends a first-party analytics beacon to jcvolpe.me for page views, engagement, and outbound clicks. Each event carries a random visitor id in localStorage, a session id in sessionStorage, the path, the referrer, any utm_ parameters, screen and window size, pixel ratio, browser language, and time zone. There are no cookies and no third parties. This page and the support page send nothing.
clankie devices revoke; it loses access immediately.Clankie is not directed at children under 13.
When this policy changes, the effective date above changes with it.
Open an issue at github.com/Volpestyle/clankie/issues.