on your mac, only.
what lucky knows, and where it stays.
lucky is a mac app that reads the messages your mac already has and drafts your next text. there is no lucky account and no lucky server that receives your messages. this page says exactly what the app keeps, what can leave your mac, and who it goes to when it does.
01the short version
- your messages stay on your mac. lucky reads imessage from this mac's messages database and whatsapp as a linked device of your phone. the history, your contacts, the profiles and drafts it builds are all stored in a folder on the machine.
- we don't run a server that sees your data. lucky has no accounts, no sign-in, no analytics, no crash reporting, no ads, and we do not sell or share anything.
- what leaves is what you set up. a model provider you give your own key to receives the lines of a thread it needs to write a draft. a calendar you connect receives the events you add. a phone you pair receives your inbox, end-to-end encrypted. each is optional and each is off until you turn it on.
02what lucky stores on your mac
everything below lives in ~/Library/Application Support/com.lucky.desktop and the macos keychain. deleting that folder, and lucky's keychain item, removes it all.
| what | where it comes from | why |
|---|---|---|
| messages | this mac's messages database (read-only) and whatsapp, as a linked device | to show your inbox and give a model the thread it needs for a draft |
| names and photos | your contacts, with the contacts permission; whatsapp's participant names | to label chats that imessage only knows by a number or email |
| style profiles, drafts, tips, moments, catch-ups | written by the model you connected, from your own chats | so the reply, the reminder and the heads-up are ready when you open a chat |
| profiles and public posts | x and linkedin, when you paste a url or let lucky look for someone's account | the sphere, intros and network search |
| settings and api keys | you | keys go in the keychain in a signed build, otherwise in the settings file |
| calendar sign-in | google, if you connect it | the token that lets lucky add the events you confirm |
| pairing keys | made on the mac when you pair a phone | the signing and encryption keys that make the phone link end-to-end |
lucky copies its database beside itself before any upgrade of its own schema, so a backup of the same data may sit in the same folder.
03what can leave your mac, and to whom
nothing on this list is on by default. each needs a key, a sign-in or a pairing code that you provide, and each goes straight from your mac to that service. lucky does not sit in between and never receives a copy.
the model provider you choose
drafts, tips, intros, moments, catch-ups and network search are written by a model at openai or xai, using the api key you enter. to do that, lucky sends the provider the recent lines of the thread in question, the names of the people in it, and, for intros and search, the profiles it has built. lucky uses each provider's api, whose terms say requests are not used to train their models; beyond that, what a provider does with a request is governed by its own terms and privacy policy, which you agreed to when you got the key. lucky uses the api, not the consumer products, and sends nothing when no key is set: without one, lucky is still the inbox.
x and linkedin, for profiles
when you paste someone's x or linkedin url, or let lucky find a new contact's account, lucky looks that person up: public posts on x by handle, career data on linkedin through linkdapi (with your key), and web searches run through xai with the name and the clues a chat gives, such as a school or a city. profile photos are fetched from x and linkedin directly. what comes back is saved on your mac. lucky only ever looks up people you text, and only once you have turned profiles on.
google calendar
if you connect a calendar, lucky signs in to google with the calendar.events scope through an oauth client you create, and only ever creates the events you confirm from a chat. the sign-in token stays on your mac. you can revoke lucky's access at any time from your google account's connected apps.
whatsapp and imessage
whatsapp sees lucky as one of your phone's linked devices, like whatsapp for mac, and your messages travel to and from whatsapp's servers exactly as they would from the official app. imessage goes through messages.app on your mac, which is apple's service. opening a whatsapp chat in lucky sends a read receipt, as whatsapp's own apps do; opening an imessage chat does not.
your phone, through the relay
lucky on your phone shows this mac's inbox, drafts and tips, and sends through the mac. every frame between the two is end-to-end encrypted with keys that exist only on the mac and the phone. the relay in between forwards sealed frames and cannot open them. it does see what any server sees: the ip addresses and connection times of the two ends, the public signing keys they identify with, and the size and timing of frames, which it uses for rate limits and to tell a phone when its mac is back. the relay keeps no history of frames.
fonts on this website
this site loads its typefaces from google fonts, so google's servers see the request for the font files, as with any site that does. the site itself has no cookies, no analytics and no forms.
04permissions on the mac
lucky asks for each macos permission on its own setup step, with the reason beside the button. it works, reduced, without any of them.
- full disk access, to read the messages database. lucky opens it read-only and never writes to it.
- automation of messages, to send an imessage. a send happens only when you press enter.
- accessibility, optional, for tapbacks, quoted replies and edits on imessage.
- contacts, to put names and faces on chats. nothing from contacts leaves the mac.
- notifications, for banners, sounds and the dock badge.
05what we don't do
- no accounts, no sign-up, nothing you have to tell us about yourself.
- no analytics, usage tracking, crash reporting or telemetry in the app or on this site.
- no advertising, and no selling, renting or sharing of your data with anyone.
- nothing is ever sent on your behalf automatically. every send is your enter key.
06your control
- to remove everything, quit lucky, delete
~/Library/Application Support/com.lucky.desktop, and delete thecom.lucky.desktopitem in keychain access. - to stop a provider, clear its key in settings. nothing is sent to it from then on.
- to unlink whatsapp, remove the linked device from whatsapp on your phone, or from settings → whatsapp.
- to disconnect a calendar, revoke lucky in your google account's connected apps, or from settings.
- to unpair a phone, remove it from settings → phone on the mac, or delete the app on the phone.
- to take back a permission, turn it off in system settings → privacy & security.
07other people in your chats
your messages include what other people wrote to you. lucky treats their words the same way it treats yours: kept on your mac, sent to a model only when you have connected one and only as part of a thread it is drafting for. looking someone up on x or linkedin uses only what is public. you are responsible for using lucky in a way that respects the people you talk to and the law where you live.
08children
lucky is not for anyone under 13, and imessage and whatsapp each set their own minimum age. we knowingly collect nothing from children, and since we collect nothing at all, there is nothing to ask us to delete.
09changes
if this page changes in a way that matters, the date at the top will change with it and the app's release notes will say so. the current page is always the one that applies.
10contact
questions about any of this: privacy@example.com.
krishiv