Skip to main content
A Biolink is a public presentation of content managed in a workspace. Different interactions store data in different places and use different access rules.

​
Where information belongs

Workspace membership does not give general access to someone else’s personal inbox. A form response is not a direct message, and embedding another service does not automatically import its submissions into Contacts.

​
Publish intentionally

Review headers, contact cards, PDFs, gallery captions and manually entered stats before publishing. Do not upload sensitive information that visitors should not copy. Removing a block does not recall downloaded files or screenshots. Collect only the form fields you need. Configure custom terms and mailing-list opt-in appropriately. Email or phone collection alone does not establish subscription permission.

​
Connected providers

YouTube, TikTok and Calendly connections have their own authorization flows. Sign-in to Biqli and authorization of a content provider are separate choices. Use the intended account, review permissions and disconnect unused connections. Disconnecting stops the corresponding authenticated behavior; public source metadata or an external-link fallback may remain where supported. Review affected blocks and publish intended changes. An external provider can apply its own cookies, consent, sign-in and access rules.

​
Messages and reports

Biolink visitors authenticate before sending a private Biqli message. The recipient can see the sender identity presented by the messaging flow and their messages. Reporting can preserve selected messages, limited context and recordings independently of the original chat. Deleting a chat does not erase an already captured report. See Reporting and moderation for the current evidence rules.

​
Requests and recovery

Use workspace roles appropriate to each operator’s duties. If an action is unavailable, ask an owner to check permissions rather than sharing credentials. For data-access or deletion requests, use the contact route in the Privacy Policy. Describe the relevant account, page and interaction without sending unnecessary private content. Retention exceptions and provider-held copies can differ from simply hiding a page item.