Privacy
Blink keeps your data on your Mac and on a server in your own account. Pexilim, the company that makes Blink, doesn't store it and can't read it.
Last updated 24 October 2026
The short version
- Your clipboard, chat history and post images stay on your Mac.
- Everything else Blink keeps is on your own Supabase server, in your account.
- AI requests go from your server to the AI provider you pick, with your key.
- Pexilim runs no database for the Blink app. For the app, the only thing we run is a tiny sign-in helper used once during setup, and it stores nothing.
- If you join the waitlist on this website, we keep your email to tell you when Blink is ready. Details below.
- No analytics, no tracking and no cookies in the app. This website counts anonymous visits and page speed, without cookies (below).
Who holds what
| Your Mac | Clipboard history (your last 50 copies), chat history and post images. The clipboard is never sent to your server or to any AI. Items that password managers mark as concealed are never recorded. You can pause or clear the clipboard at any time. |
|---|---|
| Your server | Notes, tasks, reminders, habits, spaces, money entries and accounts, content ideas, drafts and post stats, mail summaries and your sender rules, and a log of the actions you approved (kept 180 days). Your AI keys and mail app passwords are stored there as secrets; Blink never shows them again. The server is a Supabase project in your account, run under your agreement with Supabase. |
| Your mail provider | Your server checks your mailbox and stores only short summaries, not full messages. Reply drafts are saved to your mailbox's Drafts folder. Mail is sent only after you approve it with Touch ID. |
| Your AI provider | When a task needs AI, your server sends what that task needs to the provider you chose (Anthropic for Claude, Groq, or OpenRouter), using your own key. If you turn them on, post images use Cloudflare and reading your own public Instagram page uses Apify, also with your keys. Each provider handles that data under your account's terms with them. |
| Google (optional) | If you connect Google Calendar, your server creates the meetings you approve with /meet. See Google Calendar below. |
| Pexilim | Only the sign-in helper, described below. No copy of your data, no admin access, no telemetry. Separately, the waitlist, if you join it. |
Google Calendar
If you connect Google in Blink › Settings › Connections, Blink asks Google for: access to your calendar events (calendar.events, which Google shows as “view and edit events on all your calendars”; Blink only creates the meetings you approve), and your Google sign-in identity and email address (openid, email) so Settings can show which account is connected. Blink uses it for one thing: when you type /meet and approve with Touch ID, your server creates that meeting in your Google Calendar with a Google Meet link, and Google emails the guests you chose.
The access Google gives is stored encrypted in your own server's vault, never on your Mac and never with Pexilim. Your server also keeps the connected account's email and, for each meeting, its title, guests, time and Meet link in your action log (kept 180 days). Blink doesn't read your other events, mail or files through Google, doesn't sell or share Google data, doesn't use it for ads, and doesn't use it to train AI models. Blink's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You can remove Blink's access at any time at myaccount.google.com/permissions. To delete what your server keeps, remove the google_link row and its vault secret in your Supabase project, or delete the project.
The sign-in helper
When you choose “Sign in with Supabase” during setup, Supabase needs a secret that a Mac app can't keep safely. So Pexilim runs one small helper. It receives the one-time sign-in code from Supabase, adds our secret, and returns a short-lived access token to Blink on your Mac. It never asks for a long-lived token.
The helper's code doesn't store or log the code or the token. Blink keeps the token in memory only while it sets up your server, then drops it. Like any hosted service, the platform the helper runs on may record basic request details such as the time and the result. If you choose “I already have a server” instead, the helper isn't used at all.
This website
www.blinkk.app is a set of static pages. It sets no cookies. To see which pages people read and how fast they load, it uses Vercel Web Analytics and Speed Insights from our host, Vercel: they count page views, the country, the browser and device type, and loading times, without cookies and without identifying you or following you to other sites. The only other thing it sends anywhere is the waitlist form, when you submit it. Everything it uses, the font, the animation library and the film, is served from this site itself, so no company other than our host sees your visit. Like any web server, our host receives your IP address to send you the pages.
Waitlist
Blink isn't public yet. If you join the waitlist on this website:
- What we keep: your email address, when you joined, that you agreed to be emailed, and when you confirmed.
- Confirming: we send one email asking you to confirm. Until you click its button, you're not on the list, and an unconfirmed address is deleted after 30 days.
- Why: to email you when Blink is ready to download and about its launch. Nothing else.
- Where: on Pexilim's own Supabase server in Frankfurt, Germany. This website runs on Vercel, which passes the form to that server, and our emails are delivered by Resend, which sees your address and the email to send it. Both act on our behalf only.
- How long: until launch plus 12 months, or until you ask us to remove it, whichever comes first.
- Leaving: use the "Leave the waitlist" link in any email we send (one click on our site deletes your address), or write to hello@blinkk.app, and we delete your address.
- Optional questions: after you confirm, and once by email a few days later, we may ask five quick questions: what slips through your day, what you use now, which feature you'd use first, what you'd pay, and whether you'd like to test Blink early, plus an optional note. Every answer is optional. If you say yes to testing, we send you one thank-you, then write to you personally about it. Answers are kept with your address, read only by us to decide what to build, and deleted with it.
- No sharing, no tracking: we don't sell or share your email, and our emails and this form carry no tracking.
The form sends your email straight to that server. A hidden field catches spam bots; people never see it.
If you email us
If you write to hello@blinkk.app, we use your address and message only to reply. Ask us and we'll delete the conversation.
Your control
Because your data is on your own server, you decide what happens to it. You can export it, back it up or delete it from your Supabase account; deleting the project removes all of it. Clear the clipboard in Blink's settings. Pexilim has nothing to hand over or delete, because we don't hold it.
iPhone
Blink is Mac only today. When the iPhone app ships, it will need a notification relay, and we'll update this page before it does.
Changes
If we change how Blink handles data, we'll update this page and the date at the top.
Contact
Questions about privacy: hello@blinkk.app.