Privacy

Stillwire is an Android app run by Per Overgaard. This page says what the app stores, and who else receives it.

Google sign-in

You sign in with a Google account. Firebase Authentication checks that sign-in. Stillwire stores the email and name from the account on your owner record. A new Google account can use the app only after it is invited.

Your drafts

Drafts are yours. They are stored for your account. Another owner cannot read them. Stillwire does not publish a draft. You choose the text, the channels, and the time, and you confirm before a send.

A bot you connect can add drafts. The drop-in token is shown to you once. Stillwire keeps a hash of that token, not the token itself.

Firebase

Stillwire uses Firebase for Google sign-in, for your drafts and settings, and for photos you attach. Cloud Functions in europe-north1 receive drop-in drafts, talk to Buffer when you send, and run rewrite. Your Buffer API key is encrypted on the server. The app cannot read it.

Buffer

When you connect Buffer, you paste a personal API key. Stillwire uses it to list your channels. When you confirm a send, Stillwire sends the post to Buffer for the LinkedIn and X channels you picked. Buffer then holds that post. The key stays on the server.

Rewrite

If you use Rewrite in my tone, the draft and your voice notes are sent to xAI so Grok can suggest a LinkedIn post and an X post. You see the suggestion before it replaces the draft. The xAI key stays on the server.

This website

This site is static. It does not create an account. Request an invite opens your email app to peroverg@gmail.com. The site does not record that message.

Contact

Questions, or a request to delete your account and drafts: peroverg@gmail.com.

11 October 2026.