Privacy Policy

We collect the information needed to run a public Payky page and its Pubky-based editing flow. That can include your Pubky identifier, public profile metadata returned by Pubky services, and the payment methods you choose to publish on your public page.

If you connect with Pubky Ring, the browser stores a small session snapshot in local storage so your editing session can survive refreshes. The authenticated secret itself is handled separately by the Pubky SDK through an HTTP-only cookie on this origin.

If you use invoice-style links, the shared URL can contain an amount, currency, and note. Those values are visible to anyone who has the link and may also appear in browser history, shared links, and hosting or relay logs as part of the URL.

We also receive standard request metadata such as IP address, browser information, and timing data through our hosting providers and infrastructure partners.

We use information to provide the service you request, including to:

• authenticate you with Pubky Ring and restore your editing session;
• read, publish, and update payment methods on your Pubky homeserver;
• render public pay pages and invoice hints;
• measure site traffic and diagnose outages, abuse, and product issues; and
• respond if you contact us.

Payky depends on third-party and network services to work. Depending on what you do in the app, data may be processed by:

• Vercel for hosting and cookie-free Web Analytics;
• Pubky infrastructure such as the configured HTTP relay, Nexus, and PKARR relays;
• CoinGecko for BTC price conversion data; and
• the payment services or wallets you choose to open from a public pay page.

We do not sell personal information or share it for cross-context behavioral advertising. Public payment-page content is shared because publishing it is the core function of the product.

Payky uses Vercel Web Analytics to measure aggregate page traffic. Vercel describes this product as cookie-free and based on anonymized traffic data. Payky also strips invoice query parameters such asamount,currency, andnote before those URL values are sent to Vercel Analytics.

Payky also uses essential browser storage for session restore. If you block local storage or essential cookies, editor features may stop working correctly.

We keep data for as long as needed to operate the service, comply with legal obligations, resolve disputes, and protect the service. Public payment data remains public until you remove or overwrite it from the underlying Pubky storage location. Session snapshots stored in the browser are short-lived and are cleared when they are invalid, expired, or no longer safe to use.

You can remove or change the payment methods you publish, disconnect your active session, or stop using the service at any time. If you want to request access to or deletion of information we directly control, contact us through ben@synonym.to.

Some information shown through Payky is stored on decentralized or third-party systems, so deletion may need to happen through those underlying services instead of through Payky itself.

Payky does not currently respond differently to browser "Do Not Track" signals. If that changes, this policy will be updated.

Payky is not directed to children, and we do not knowingly collect personal information from children. If you believe a child has provided information to Payky, contact us so we can review the situation.

We may update this Privacy Policy as the product changes. When we do, we will post the updated version here and revise the effective date above.