Privacy Policy

Magpie is operated by an independent developer ("Magpie," "I," "me"). Location: New Jersey, USA. For questions or concerns, please use the Contact form.

Magpie is designed around a simple principle: your ideas should live in tools you own and control. Magpie exists to help you add to and work with that data, not to lock it in.

Account Information

I collect the minimum information needed to operate Magpie, such as authentication identifiers used to connect your accounts (for example, GitHub OAuth).

GitHub Integration Data

When you connect a GitHub account, Magpie receives permission to access the repositories you explicitly choose. This may include: Repository metadata (such as repository name, file paths, and commit history). Content you choose to read, create, or update using Magpie.

Magpie may create commits in your repositories only in response to actions you take (for example, saving or updating a note). All commits are authored as the authenticated GitHub user and follow standard GitHub version history.

Phone Number & SMS Data

If you choose to link your phone number for SMS note capture, I collect your phone number. It is stored in encrypted and hashed form — never as plain text — to route incoming messages to your account. When you send a text message, the message body and metadata (such as message ID and timestamp) are temporarily logged for deduplication, rate limiting, and operational reliability. Your consent to receive SMS confirmation messages and the timestamp of that consent are also recorded.

Content You Provide

Magpie does not maintain a separate copy of your notes or files as a primary data store. Your content lives in your GitHub repository, which you own and control. Magpie accesses and modifies this content only to carry out actions you request.

Usage & Technical Data

Like most online services, Magpie's infrastructure providers may collect limited technical data (such as IP address, timestamps, and request metadata) to operate, secure, and maintain the service.

I use information only to: Provide and operate Magpie (authentication and syncing with GitHub). Process and save notes you send via SMS. Send SMS confirmation replies when you use the SMS feature. Maintain reliability and security. Prevent abuse through rate limiting and deduplication. Communicate essential service updates.

Magpie does not use your content for advertising, profiling, or model training.

Service Providers

Magpie relies on a small number of service providers to operate: GitHub (repository hosting and OAuth authentication). Supabase (authentication and basic account data). Vercel (hosting and infrastructure). Twilio (SMS message routing — used only if you link your phone number for the SMS feature). Twilio processes your phone number and message content as a transport provider. I enable Twilio message redaction to minimize what Twilio stores.

I do not sell personal information and do not share it for cross-context behavioral advertising.

I may also disclose information if required to comply with the law or to protect the rights, safety, and security of users or the service.

Magpie requests GitHub OAuth access only to the repositories you choose to connect.

You can revoke Magpie's access at any time through your GitHub account settings. Revoking access does not affect content already stored in your repositories.

Magpie offers an optional SMS feature that lets you text notes to a Magpie phone number operated via Twilio. This feature is only available after you explicitly link your phone number and consent to receive messages. Linking is optional and can be undone at any time from your account settings.

Consent & Opt-Out

By linking your phone number, you agree to receive SMS confirmation messages from Magpie. Message and data rates may apply. To opt out at any time, reply STOP to any Magpie message. To re-enable the feature, visit your account settings to re-consent. Reply HELP to any Magpie message for support information.

What Magpie Sends in Replies

SMS is not an encrypted medium. To protect your privacy, Magpie reply messages contain only a short confirmation and a link — never the content of your note. Note content travels to and from GitHub over encrypted connections, not over SMS.

Rate Limits

To prevent abuse, Magpie limits incoming SMS messages per phone number. If you exceed the limit, messages will be rejected temporarily.

Content stored in GitHub remains in your repositories unless you delete it. Magpie does not retain a separate long-term copy of your repository content.

Basic account data is retained until you delete your account. If you link a phone number for SMS, your phone number is retained until you unlink it or delete your account. SMS message logs (used for deduplication and rate limiting) are retained for a limited period for operational purposes.

Infrastructure providers (such as Supabase and Vercel) may retain technical logs according to their standard retention practices for security and reliability purposes.

You can: Access, correct, or delete your account data by contacting me through the Contact form. Export, modify, or remove your content directly from GitHub at any time. Stop using Magpie without losing access to your data.

Because your content lives in GitHub, you do not need to rely on Magpie to retain or retrieve it.

If you are a resident of certain U.S. states (CA, CO, CT, VA, UT), you may have rights to: Access and receive a copy of personal information. Correct inaccurate information. Delete personal information. Opt out of targeted advertising, sale, or sharing (Magpie does not sell or share personal information).

To exercise these rights, contact me through the Contact form. I will respond within the timeframe required by law.

Magpie is not directed to children under 13, and I do not knowingly collect personal information from children.

I use reasonable administrative, technical, and physical safeguards to protect personal information. However, no system is 100% secure.

Magpie is based in the United States. If you access Magpie from outside the U.S., your information may be processed in the U.S. or other locations where service providers operate.

I may update this Privacy Policy from time to time. Updates will be posted here with a revised "Last updated" date.