A practical privacy checklist for your Presbot assistant

Privacy begins with thoughtful choices

A useful assistant does not need to collect every possible detail.

Privacy improves when your questions, access, and follow-up process are designed around a clear purpose.

This guide is a practical review, not legal advice. Your business may need guidance that reflects its location, industry, and obligations.

Know why each detail is collected

Review every lead capture question and write down how the answer is used.

If a detail has no clear purpose, remove the question.

Review how to set up lead capture.

Avoid sensitive information

Do not ask visitors to submit passwords, security codes, payment card details, government identifiers, or other sensitive information through a general website conversation.

Direct people to an appropriate secure process when sensitive information is required.

Set clear expectations

Visitors should understand when information is being saved for follow-up.

Use plain language about what will happen and how the team will respond.

Keep your website privacy notice current

Your privacy notice should reflect the way your business collects and uses visitor information.

Make it easy to find from the website and keep it aligned with the actual lead process.

Limit access

Only people who need visitor information for their work should have access to it.

Review team access when responsibilities change or someone leaves the organization.

Use strong account security

Use a unique password, protect access to the email account connected to Presbot, and avoid sharing one login among several people.

Review how to protect access to your Presbot account.

Handle leads carefully

Do not copy personal information into public notes, unsecured documents, or unrelated systems.

Share only what a colleague needs to complete the follow-up.

Choose a retention approach

Decide how long visitor information is useful for your business and what happens when it is no longer needed.

Your approach should fit your business obligations and the promises made to visitors.

Review third-party processes

If your team transfers lead information to email, a spreadsheet, or another system, review the privacy and access practices of that workflow too.

Protecting information in Presbot is only one part of the full process.

Test the public experience

Complete a lead request as a visitor.

Check whether the purpose is clear, unnecessary information is avoided, and the privacy page is easy to find.

Review after business changes

Update your privacy process when you add new lead questions, change follow-up tools, expand to new regions, or change who handles visitor information.

Privacy checklist

• Every collected detail has a purpose
• Sensitive information is not requested
• Visitors understand the follow-up process
• The website privacy notice is current
• Access is limited to the right people
• Account security is reviewed
• Leads are shared carefully
• A retention approach exists
• Connected tools are considered
• The public experience was tested

Next steps

Review how Presbot handles privacy and visitor data and how to review and manage captured leads.