Share a profile intentionally, then keep control of access.
Profile Share uses controlled links and a static QR so someone can share the intended profile view without exposing private account details or creating a public directory.
An active static QR uses fictional data only.A revoked or expired code resolves to a privacy-safe unavailable state.
Active, revoked, and expired
An active share can resolve to the intended profile. Revocation stops future resolution through that share. Expiration ends time-limited access without requiring the owner to remember to remove it later.
Blocking still takes priority. A blocked viewer should not recover access through a copied link or QR.
Active, revoked, and expired
State
What it means
Available next step
Active
The controlled code resolves to the intended shared profile view.
View only the shared context or leave the page.
Revoked
The owner ended access for that code.
The old QR remains static but no longer restores access.
Expired
Time-limited access ended.
A new share requires a new intentional action by the owner.
Blocked
A relationship boundary prevents access.
The resolver does not disclose private block details.
Unavailable
The code cannot resolve to a view.
Use Support only for an account or technical issue.
The resolver is deliberately private
The public resolver path uses a code, stays noindex, remains outside the sitemap, and is not linked from navigation. Search engines should not treat shared codes as discoverable profile pages.
A static QR can be shown or printed, but the access behind it remains revocable. Revoking the share does not physically change an already printed QR; it changes what that code can resolve.
