What Privacy Links are
Privacy Links are shareable Parly payment pages. Use them when you want someone to pay you without exposing your private Parly balance, full wallet history, or wider activity graph. Parly supports two link types:- Profile links for open-ended payments, tips, creator payments, service deposits, and recurring public payment pages.
- Invoice links for a specific payment request with an amount, asset, expiry, and recipient-facing details.
What payers can choose
Depending on the link settings and route availability, a payer can use:- Deposit from wallet for a connected-wallet payment.
- One-time deposit address for a generated payment address that can be paid from a supported wallet or exchange.
What stays private
Privacy Links are public pages, so the profile or invoice details you publish are visible to anyone with the link. Your private Parly balance, private ledger, unrelated payments, recovery identity, and private notes are not shown on the public link. Receipts and Verify disclose only the payment or invoice settlement they are meant to prove.Link owner controls
From the Privacy Links tab in the App, a link owner can:- reserve and publish a Parly username
- create or update a profile link
- create invoice links
- review link activity
- download receipts where available
- connect notification channels where supported
- manage receipt and display preferences
Reports and restricted names
Parly may restrict names, slugs, images, or public content that is reserved, misleading, impersonating, abusive, illegal, or unsafe. If a link is restricted, the owner may need to rename, edit, pause, or republish the link. Settled receipts, payer history, and refund paths should remain scoped to the payment records they belong to.Good practices
- Publish only information you are comfortable showing publicly.
- Use a refund wallet you control.
- Do not ask payers to send funds outside the current payment instructions shown by Parly.
- Keep receipt or verification links for reconciliation.
- If a payment fails, use the shown status and refund path instead of resending blindly.

