What security questions should you ask an AEO vendor?
Ask an AEO vendor about data access, storage, deletion, security reports and contract terms. Use these questions to review the evidence before you sign.
Put the answers in writing
What this guide shows
A clear record helps your team judge the risks before data changes hands.
Know who can see or change your data.
Check what a report covers before relying on it.
Agree on data return and deletion before work starts.

Short answer
The Answer
Ask an AEO vendor who can see your data, how it is stored and deleted, what they will sign, and which security reports they can show you. Ask for the documents in writing. A vendor claim is not proof until you see the report and its date. Our founder handles AEO agency buying questions like this one, and his own real estate team closed over $100,000 in commission in July 2026 and credits AI search for it.
AEO means making your business easier for AI answer tools to find, trust and name. The right review depends on the data and access you plan to share.We did it for our own business. Let’s find out how to do it for yours. Book a 30-minute call to find out how we can help yours
Who can see your data, and why?
Ask for a list of the people and roles who can reach your data. Include staff, contractors and any outside firms that take part in the work. Ask what each role needs to see and what each person can change. A name on a sales call is not the same as a list of people with access.
Give the vendor only the access needed for the agreed work. Ask if each person gets a named account and whether access can be removed without breaking the work. Find out who approves new users, who checks the list and what happens when a person leaves. Your own team should know who can grant and remove access on your side too.
Ask about shared logins, admin rights and any access to your site, analytics or customer systems. A vendor may need to read a report without needing the right to change billing or add users. Have the vendor explain each requested role in plain words. If a request is too broad, agree on a smaller role or a safe way to share the needed data.
If the work covers public service pages, challenge a request for full access to your customer database. Ask which fields the vendor needs and why. Share a report with only the fields needed for the job, and keep the rest out of the handoff.
Review the list with the people who own each system. A site editor, an analytics viewer and an account administrator can have very different powers. Ask the vendor to separate the work it must do from the access it would like to have. If a task changes, revisit the role instead of leaving old access in place. Write down who can remove each account when the work ends.
Do not approve broad access just because it is easy to set up. Keep the access list with the signed scope, including the role, purpose and named owner for each grant. Name an owner at each firm who can approve changes. Ask for notice before a new outside firm handles your data. End the review with a dated list of people, roles and approved access.
Have a question about the access your team needs to share? Email us about your question
What data will the vendor collect and use?
Ask the vendor to map the data it expects to receive. This can include site access, search reports, draft content and files your staff share. Some files may contain personal information, such as a name, email address or customer history. Mark those fields before you send a sample.
For each kind of data, ask why it is needed, where it will go and who can use it. Ask whether the vendor will put your data into an AI service, and which account and settings will apply. Get the answer for the actual product and plan used for your work. A general statement about AI does not tell you what happens in that account.
Ask whether prompts, files or outputs can be used to train models. Ask what choices apply and who can change them. Also ask if your data can be used for product testing, sales samples or other clients. If a use is not part of the work you want, raise it before the first file is sent.
Before you send a draft brief, check it for customer email threads and other details that do not belong in the work. Remove them and share public facts instead. If a private thread is needed, record the reason and the safeguards before anyone sends it.
Ask the vendor to list its outside providers and what each one does with your data. An outside provider is a separate firm the vendor relies on to deliver the work. Ask how the vendor learns of changes and how it will tell you. A report about the main vendor alone may not answer every question about those other firms.
Do not accept a vague answer that says data is used only to improve the service. Ask the vendor to spell out the uses that phrase covers. If an outside provider handles a file, ask whether the same limits follow it there. Keep the answer beside the data map so the people sharing files know what has been approved and what still needs a decision.
Put the allowed uses and limits into the deal documents. NIST advises firms to put supplier security needs into agreements and keep watching risk during the relationship. Give your security and privacy teams the data map, the proposed uses and the list of outside providers. Ask for a dated copy of the agreed limits before the first file is sent.
See whether an AI answer names your business. Does ChatGPT name you?
Where is your data stored, and how is it deleted?
Ask where each kind of data is stored, including working copies, exports and backups. Ask which countries or regions are involved and whether the answer can change. If location matters to your firm, put the agreed limits in writing and ask how a change will be approved.
Ask how data is protected while it moves and while it is stored. Encryption means using a code to make data unreadable without the right key. Ask where it applies and who controls the keys. Also ask how the vendor separates your files from those of other clients.
Next, ask how long each type of data is kept. A retention period is the time a firm keeps data before it is deleted or otherwise handled. The answer should cover active files, logs, backups and copies held by outside providers. Ask which items cannot be deleted right away and why.
If you share a draft with private staff details, track where it goes. At the end of the project, ask the vendor to identify the working copy, any backup and the person who will confirm what was done. Use that list to check the exit steps against the files you actually shared.
Ask for the exit steps before you sign. What can you take with you, in what format, and who will help? When will access end? What proof of deletion can the vendor give, and what does that proof cover? Set a clear path for exceptions, such as a copy kept for a legal reason, with your counsel’s help.
Test the plan on paper before work begins. Pick a file your team expects to share and trace the path from receipt to storage, return and deletion. Ask who holds each copy along the way. If the vendor cannot explain a step, leave it open in the decision record and get a written answer before sending that file.
NIST includes planning for the end of a supplier relationship in its framework. Settle the exit questions while both sides can agree on the scope. Keep a written exit plan that names the files to return, the copies to delete, any stated exceptions and the person who will confirm each step.
How should you review a security report?
Ask what security reports or other evidence the vendor can share. Ask for the date, the service covered and the period reviewed. Your security team may need to sign a nondisclosure agreement before it can review a document.
Check that the named firm and the service you will use are in scope. Ask your security team to read the findings and limits in the report. Ask the vendor what it did about any issue that matters to your work, and ask for support in writing.
A report for a hosting service may leave questions about the team that handles your files. Ask how the report relates to the proposed service, then request the vendor’s own evidence for the parts outside that report. Mark the gap beside the service it affects.
Ask whether the evidence assumes that your team will perform certain tasks. For example, your firm may need to manage its own users and access. Give those duties to a named owner and make sure that person understands what is expected.
If the vendor cannot share a report, ask what other evidence it can provide. Your reviewer can decide whether that evidence addresses the data and services involved. Record any gap so the person responsible for the decision can review it.
Do not let a report title stand in for a review. Match the service in the document to the service in your proposed scope. List the duties your own team must perform, then put a name beside each duty. If the evidence is missing or covers a different service, ask for a written response and record the decision on the gap.
Keep a record of the documents you reviewed and when you reviewed them. Ask how the vendor will tell you about changes that affect the work. A report is evidence for a defined scope, not a promise that no incident can happen. Save its date and scope with the reviewer’s decision and any open gaps.
See the story behind our founder’s own result. Read the founder’s case study
What happens if data is exposed or lost?
Ask the vendor to explain how it finds and handles an incident. An incident is an event that may put data or systems at risk. Ask who receives the alert, who will contact your team and how you can reach them outside normal hours. Make sure the contact path still works if the usual project lead is away.
Ask what the first notice will contain, when you can expect it and how updates will follow. The vendor may not know every detail at the start. Your agreement can still set out who will share known facts, how often the parties will check in and how new facts will be passed along.
Ask how the vendor will preserve useful records and help your team assess the scope. Which data was involved? Which systems or outside providers were affected? What steps were taken to stop further exposure? Ask how the vendor will share a written account and what steps will address the cause.
If a file goes to the wrong outside party, your team needs a direct contact, a record of what was sent and updates as the vendor learns more. Ask for a written plan that says where the notice goes and who takes the next step.
Bring your security, privacy and legal teams into the discussion before you sign. They can compare the proposed notice and response terms with your own needs. NIST calls for relevant suppliers to be included in incident planning, response and recovery. Ask how that shared plan will be kept useful as contacts and services change.
Make the contact path usable by the people who will need it. Ask for a role or team that can receive a notice if the usual contact is away. Agree on where updates will be sent and who records open questions. A plan buried in a sales thread is hard to use when your team needs an answer. Keep the current contact details with the agreement.
Ask about service outages and recovery too. What work can continue if a system is down? How will the vendor tell you when access is restored? Name the person who decides when to resume sharing files, and keep that name with the incident contacts and notice steps.
What should you put in writing before you sign?
Bring the answers into the agreement, the work scope or another document your team approves. A sales email can help you spot a gap, but ask your counsel which promises belong in the signed terms. Include the data types, allowed uses, access roles, outside providers and the process for changes.
Add the report and review details that matter to your decision. State what evidence the vendor will provide, who can review it and how you will handle gaps. Ask how you will learn about a material change to the service or its security practices. Give each open item an owner and a date for review.
In California, rules for service providers and contractors handling personal information set contract requirements where they apply. These include limits on use and notice if the vendor can no longer meet its obligations. Your legal team should decide whether those rules apply to your deal and review the actual terms. This page is a buying guide, not legal advice.
A broad promise to keep data safe leaves too much to settle later. Send the vendor a list of allowed uses, notice steps and exit duties, and ask for answers in writing. Put each open point beside the person who must resolve it before the deal is signed.
Keep a short decision record. Note the documents received, the date and scope of each report, the gaps, and who accepted any remaining risk. If the vendor will not answer a key question, keep it open and hold the deal until your team makes a decision.
Do not sign without a named owner for each open action. The record should show what is still missing, who will get it and when the team will review it. Keep the vendor’s written answers with the signed scope so the people doing the work can find the same terms the buyer reviewed.
Review the answers as the work changes. A vendor that first receives public pages may later ask for customer records or wider access. That is a different risk question. NIST recommends monitoring supplier risk across the relationship. Ask for an updated data map and a dated review before the new work begins.
Need to ask a quick question before you compare proposals? Text our team
What should your final security review cover?
- List each person and role with access
- Map the data and its approved uses
- Review storage, outside providers and deletion
- Read the report, its scope and its date
- Agree on incident contacts and notice
- Put open risks and exit steps in writing
Frequently Asked Questions
Does an AEO vendor need a SOC 2 Type II report?
Your firm sets its own review needs for the work and data involved. Ask for the report if it matters to your policy, then check the covered service, dates and findings. If it is not available, ask for other evidence and have your security team decide whether any gap is acceptable.
What if a vendor cannot share its security report?
Ask what other evidence the vendor can provide and whether it covers the service and data involved. Have your security team review the evidence, record any gap and decide whether the remaining risk is acceptable. Note who reviewed the documents and when, and ask how the vendor will report changes to the service.
Can an AEO vendor use your files to train AI?
Ask the vendor and get the answer in writing for each service and account that will handle your files. Check what the agreed terms allow, who can change settings and whether outside providers receive the data. Your team can restrict the files it shares while the answers are under review.
Who should review an AEO vendor’s security answers?
Include the people who own the data and the systems the vendor wants to use. Your security and privacy teams can review the evidence and data flow. Counsel can review proposed terms. A business owner should also understand any open risk and who is responsible for the next decision.
What should happen to data after the work ends?
Agree on return, access removal and deletion before work starts. Ask what happens to working files, backups and copies at outside providers. The vendor should explain any limits and what written confirmation it can give. Your team should name an owner to check that the agreed exit steps are complete.
Do California privacy rules apply to every AEO deal?
Do not assume the same rule applies to every deal. California rules set terms for service providers and contractors handling personal information where the rules apply. The facts of the work and the parties matter. Ask your legal team to assess your agreement and the data involved before you rely on a general answer.
Sources
- The NIST Cybersecurity Framework 2.0NIST
- California Consumer Privacy Act RegulationsCalifornia Privacy Protection Agency
Next step
Find out what your business needs
Our own business was the test case. Let’s find out what it could do for yours.
Get your free Answer Engine audit