To report Google Forms phishing, use the form's Report or Report Abuse control, select the relevant abuse category and submit the report to Google. Do not use Contact form owner as a substitute. Google says that contacting the owner shares your name and email address with them.
For a brand-protection or fraud team, that distinction matters. The person controlling the form may be the person impersonating your organization. Your job is to document the deception and reach the platform's review process without sending an investigative message to that person.
Check the request, not just the host
A form hosted on a familiar service can still contain an unauthorized request. A logo, business name or convincing description does not establish that your organization created or approved it.
Compare the form with your authorized collection process. Ask the relevant business owner whether this exact form and request are legitimate, using a known internal contact rather than the details supplied in the suspicious message.
Record what the form claims and what it requests. For example, a form might claim to restore access to a customer account while asking for a password. That is an illustrative scenario, not a finding about any particular form.
Google's abuse program policies prohibit phishing, including soliciting or collecting passwords, financial details and Social Security numbers. They also address impersonation, misrepresentation, fraud and spam. Select the category supported by what you observed. A form does not have to collect a password to raise an impersonation concern.
Not every unfamiliar form is malicious. A legitimate department or authorized partner may use a separate service. Confirm the claimed relationship before reporting a genuine business process as abuse.
Keep reporting separate from contacting the owner
Several controls can appear around a Google Form. They have different purposes.
- Report or Report Abuse sends an abuse complaint through Google's reporting process. This is the relevant path when the evidence indicates a policy violation.
- Contact form owner sends a message to the person responsible for the form. Google's responder help page explicitly warns that your name and email address are shared when you send that message.
- Product feedback reports a problem with the product experience. Do not assume that sending generic feedback has filed the abuse complaint you intended.
The privacy warning about owner contact is not a promise that abuse reporting is anonymous. Review the reporting interface and your organization's disclosure rules before submitting. Include necessary case evidence, not unrelated customer records or confidential investigation notes.
If your team needs to approach a legitimate but compromised form owner, make that a separate, approved decision. Verify an independent contact path first. Do not use the suspicious form itself to establish whom you are talking to.
Preserve the form without completing it
Keep the original customer or employee report, including the message containing the link. A screenshot helps explain the lure, but the exact form location is needed to identify the affected content.
An authorized analyst should record:
- The complete form URL and any original shortened or embedded link.
- The observation time, timezone and whether the analyst could view the form.
- The displayed title, organization name, logo and claimed purpose.
- The exact visible questions and field labels that support the complaint.
- Screenshots of the claim and requested information, with sensitive customer values excluded from the reporting copy where possible.
- The internal confirmation that the organization did not authorize this form or request.
- Any visible external link, phone number or other destination associated with the deception.
Do not ask a customer to revisit the form, supply another answer or upload a document to prove the case. Do not enter real credentials, payment details or personal information during validation.
Some questions or later sections may not be visible without progressing through the form. Record that limit rather than inventing what happens next. An empty required field is not a reason to submit sensitive information. If further examination is necessary, use your team's approved investigation environment and authorization process.
Preserve the original evidence in restricted case storage. Prepare a separate reporting copy when information needs to be minimized. Record any redactions so another analyst can distinguish the original observation from the version sent outside the organization.
Follow the responder abuse-reporting path
Google's current reporting instructions describe the responder path as opening Help at the bottom left of the form, choosing Report, selecting the abuse type and clicking Submit Abuse Report. Another official responder help page describes a Report Abuse link at the bottom. The labels can differ; the important distinction is the abuse-reporting control, not the owner-contact option.
Use the responder instructions when investigating a form you do not own. You do not need to request editing rights from the suspected operator to prepare the complaint.
Where the reporting interface accepts explanation, state the relationship clearly. Identify the organization being impersonated, the unauthorized claim and the sensitive information or fraudulent action requested. Keep the explanation tied to the specific form and observed behavior.
Save the submitted report details and any acknowledgement or reference provided. Do not add invented information to complete a field. If the form cannot be opened or its reporting control is unavailable, record the access failure and consult Google's official help rather than treating that failure as proof of enforcement.
Separate exposed information from external removal
If someone already submitted information, record the type of information involved without asking them to repeat passwords or other secrets in the case notes. Route the exposure through the organization's incident-response process. Credential, financial and personal-data exposure may require different owners and actions.
That work must not wait for a platform complaint to finish. Removing a form cannot establish that information already submitted was recovered or deleted from every recipient's possession.
Likewise, a form may direct people to a separate site or contact channel. Keep those destinations as distinct evidence items. Reporting the form does not establish that its linked website or messaging account has been addressed.
Outtake Intake connects inbound fraud complaints with indicator extraction, campaign investigation and external response workflows. It is a relevant next step when multiple customer reports point to connected impersonation assets. This does not imply a dedicated Google Forms integration or guaranteed platform action.
Verify what changed before closing the case
Google states that reporting does not guarantee removal or another action. Its documented options include removing content, restricting sharing or visibility, and limiting access to products. Preserve the actual response rather than assuming which action occurred.
A form that says it is no longer accepting responses is closed for submissions. Google's responder help documents that state separately from abuse enforcement. It is not, by itself, evidence that Google removed the form because of your report.
Record the observed outcome precisely:
- The report was submitted, but no decision is known.
- The form remains viewable but no longer accepts responses.
- The form cannot be accessed under the documented check conditions.
- Google supplied a response describing a restriction or removal.
Keep the platform response and your independent observation separate. A permission change, a closed form and confirmed enforcement are different findings. Check whether the original distribution messages and related destinations still expose customers, then assign any remaining work before closing the investigation.
Related reading
- Brand impersonation detection and removal explains how a form can fit into a wider operation.
- What is an email abuse box? covers preserving and triaging the original message.
- Phishing takedown services explains different removal outcomes and provider responsibilities.
Sources
- Google Docs Editors Help, Report a violation.
- Google Docs Editors Help, Fix common errors while you respond to a Google Form.
- Google Docs Editors Help, Abuse Program Policies & Enforcement.
- Outtake Intake.
Sources reviewed October 10, 2026.