Public and private links
Public target links and QR codes are intended for respondents. They do not grant workspace administration access. Private feedback is separate from public widgets.
Private follow-up links, visitor passes, guest chat sessions, integration secrets and business cookies need protection. A private customer link can authorize specific follow-up actions.
Collect and export carefully
Use optional fields unless the information is necessary. Review visitor fields and notices before sharing an entrance QR. Account profession and phone are optional and are not public widget data.
Avoid unnecessary personal information in notes. Downloaded CSV files no longer have the app's access controls, so store and share them securely under your organization's policies.
Digital business cards are public contact profiles: publish only approved fields. A contact download can be retained outside Lipback. Campaign contact capture, review publication and voluntary card contact exchanges have separate purposes and consent choices.
Review consent
Public publication requires customer consent and moderation. Apply content rules to positive and negative reviews alike. Customers can withdraw public permission using their private follow-up link.
Operational and legal requirements
The operator must configure secure hosting, trusted origins, authentication, persistence, backups, credentials and retention operations. Notifications and payments need their own provider configuration.
The legal center provides the Privacy Policy, Terms of Service and Cookie Notice, with Gasobu Technologies operator details. Organizations must still review their own collection notices and legal obligations; the presence of a policy page does not establish regulatory certification.
Card and campaign privacy
A campaign source or channel identifies distribution, not a verified person. Do not put email addresses, names or private data into share-link source labels.
Card analytics counts recorded profile views, QR requests, downloads and contact actions. A vCard download does not confirm that a visitor saved the contact; unique visitors are not estimated. Organizations can set card event and activity retention, but the retention worker must run to remove eligible records.
Guide reviewed 22 October 2026. Available actions depend on your workspace permissions and enabled modules.
