Can this be signed electronically?

Yes. Electronic signatures meet the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and retention requirements are satisfied; check New York’s ESRA for state-specific rules.

Is notarization required?

Generally no for a standard Personal Information Request. Notarization may be required for related legal instruments (deeds, powers of attorney) depending on state law and the document’s legal effect.

What if the SSN or TIN is incorrect?

An incorrect TIN can trigger backup withholding and penalties under IRC §6721; verify taxpayer identification early and provide instructions for correction to the payer.

How long must records be kept?

Retain according to the longest applicable rule: IRS records 3 years (IRC §6501(a)), HIPAA 6 years (45 CFR §164.530(j)), and any industry-specific timeframes.

Can a signer revoke consent?

Yes, signers can withdraw electronic consent where ESIGN consumer-disclosure rules apply; retain evidence of the withdrawal and follow any contractual or regulatory notice periods.

What identifiers are safest for verification?

Use a government ID plus a secondary check (SMS code, email confirmation, or knowledge-based verification) for higher assurance and a stronger audit trail.

Electronic Signature
Templates
Miscellaneous
Personal Information Request

Personal Information Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

PERSONAL INFORMATION REQUEST AGREEMENT

This Personal Information Request Agreement (the "Agreement") is entered into as of by and between Requesting Party: and Data Provider: .

WHEREAS

WHEREAS, Requesting Party requires certain personal information to perform legitimate business functions, including evaluation, onboarding, or regulatory compliance; and

WHEREAS, Data Provider is willing to provide such personal information to Requesting Party subject to the terms, conditions, and safeguards set forth in this Agreement; and

WHEREAS, the parties desire to specify the scope, permitted uses, retention, and protection of the personal information to be disclosed.

DEFINITIONS

For purposes of this Agreement, "Personal Information" means any information that identifies or reasonably can be used to identify an individual, including but not limited to the categories listed in the Scope of Requested Personal Information below.

SCOPE OF REQUESTED PERSONAL INFORMATION

The Data Provider is requested to disclose only the following categories of Personal Information necessary for the Purpose of Request identified below. Select all applicable categories and provide any necessary detail.

Requested Categories: Full legal name Date of birth Contact information (address, phone, email) Identification numbers (e.g., government ID, social security number) Employment history Financial information Other (specify below)

If Other, specify details:

SCOPE OF WORK

Requesting Party will use the requested Personal Information to perform the following scope of work. The use shall be limited to the activities expressly described below; any additional use requires written amendment and Data Provider consent.

Describe Scope of Work:

PURPOSE OF REQUEST

State the lawful business purpose for which the Personal Information will be collected, used, or disclosed.

Purpose:

PAYMENT TERMS

If Requesting Party will pay a fee for processing or providing copies of Personal Information, indicate the agreed amount, payment schedule, and late fee assessment.

Fee amount (USD): Payment schedule: Late fee:

TERM AND TERMINATION

This Agreement commences on the Start Date and continues until the End Date unless earlier terminated pursuant to this Section.

Start Date: End Date:

Notice period for termination (days):

Either party may terminate this Agreement for material breach by the other party if the breach remains uncured thirty (30) days after written notice, or immediately for unauthorized disclosure of sensitive Personal Information.

CONFIDENTIALITY AND DATA PROTECTION

Requesting Party shall treat all Personal Information received under this Agreement as confidential and shall not use, disclose, or process such information except as necessary to fulfill the Purpose of Request and as authorized in writing by Data Provider. Requesting Party will implement reasonable administrative, physical, and technical safeguards appropriate to the sensitivity of the Personal Information to protect against unauthorized access, disclosure, alteration, or destruction.

In the event of a confirmed security breach affecting the Personal Information, Requesting Party shall notify Data Provider without unreasonable delay and cooperate in any required mitigation and notification processes.

THIRD-PARTY DISCLOSURES

Requesting Party shall not disclose Personal Information to third parties except (a) to service providers bound by written obligations consistent with this Agreement, (b) as required by law, or (c) with the express written consent of Data Provider. Where disclosure is compelled by law, Requesting Party will provide prompt notice to Data Provider unless prohibited by applicable law.

DATA SUBJECT RIGHTS

Upon written request from Data Provider, Requesting Party shall provide confirmation of whether Personal Information concerning the Data Provider is being processed and shall provide access, correction, or deletion of such Personal Information as required by applicable law and as reasonably practicable.

REPRESENTATIONS AND WARRANTIES

Each party represents and warrants that it has the full power and authority to enter into this Agreement and that the execution and performance of this Agreement will not violate any other agreement or applicable law.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction specified by the parties below. The parties submit to the exclusive jurisdiction of the courts of that jurisdiction for disputes arising under this Agreement.

Governing law (state or jurisdiction):

ENTIRE AGREEMENT

This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, and communications, whether oral or written. Any modification or amendment must be in writing and signed by authorized representatives of both parties.

ACKNOWLEDGMENT AND CONSENT

By checking the box below, Data Provider acknowledges receipt of this Agreement, confirms that the information requested is limited to what is necessary for the stated Purpose of Request, and consents to the disclosure and processing of the specified Personal Information pursuant to the terms of this Agreement.

I, the Data Provider, consent to the release and processing of my Personal Information as set forth in this Agreement. I certify that the information I have provided to Requesting Party in connection with this request is true, accurate, and complete to the best of my knowledge.

NOTICES

All notices under this Agreement must be in writing and delivered to the contact information provided by each party below. Notice is effective upon receipt.

Requesting Party contact information: Data Provider contact information:

Requesting Party - Printed Name:

By:

Date:

Data Provider - Printed Name:

By:

Date:

What a Personal Information Request Is and When It’s Used

A Personal Information Request is a written form used to collect an individual’s identifying and contact details, tax identifiers, and other data needed to process transactions, verify identity, or complete regulatory filings. Organizations use this document to standardize the data they collect from customers, contractors, employees, students, or vendors. The form typically names the requester, explains the purpose of collection, lists required fields, and includes signature and date lines. When handled electronically, the request must meet ESIGN and applicable state electronic transaction rules to be legally effective across jurisdictions.

Why a Clear Personal Information Request Matters

A well-constructed Personal Information Request reduces errors, speeds verification, and documents consent for the use and retention of personal data. Clear fields and legal notices help meet ESIGN and state electronic transaction requirements while limiting follow-up contacts and processing delays.

Who Typically Completes or Receives This Request

Organizations that collect personal data for onboarding, tax reporting, benefits, or service delivery commonly use a Personal Information Request. The form is adaptable across departments and industries.

Human resources teams and onboarding staff who gather identity, employment, and tax information for payroll and benefits.
Finance and accounts payable groups requesting taxpayer identification for vendor setup and backup withholding compliance.
Healthcare intake coordinators and administrative staff collecting contact and consent details consistent with privacy rules.

Step-by-Step: Filling and Submitting the Request

Complete the request in the following order to avoid omissions and to support validation checks before submission.

01

Prepare: Assemble IDs and tax documents before starting the form.
02

Enter Data: Complete each required field using the required formats.
03

Authenticate: Confirm identity via photo ID, SMS code, or other method.
04

Sign & Submit: Sign, date, and use the indicated submission channel.

Typical Online Workflow Configuration

When automating the Personal Information Request, configure fields, authentication, and storage to match your compliance needs.

Field	Configuration
Automatic Detection	Enable Magic fields to detect name, address, and SSN patterns.
Conditional Fields	Show tax fields only when the recipient is a U.S. taxpayer.
Authentication	Use email, SMS, or multi-factor authentication for signer identity.
Storage Format	Save completed records as PDF/A with an audit trail.

Typical Electronic Submission Flow

The electronic flow follows established steps that capture consent, identity, signature, and an audit trail for legal admissibility.

Upload Document: Sender uploads the request and maps fields.
Assign Signers: Enter signer emails or generate signing links.
Sign and Authenticate: Signer authenticates and executes the signature.
Archive and Audit: System stores signed PDF and completion certificate.

Technical Options for eSubmission and Integration

Choose platform settings and integrations that match your authentication, retention, and storage policies for personal data collection.

Integrations: Salesforce, NetSuite, Microsoft 365 and others supported
Formats: PDF, DOCX, HTML, Excel supported for uploads
Authentication: Email, SMS code, KBA, or SSO options

Security and Compliance Checklist

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

HIPAA: BAA required for protected health information

Audit Trail: Timestamps, IP, and action log retention

Standards: SOC 2 Type II and ISO 27001 certified

Accessibility: WCAG 2.0 Level AA compliant

eSign Laws: Compliant with ESIGN and UETA/ESRA frameworks

Key Risks and Legal Consequences

Incorrect TIN: Triggers backup withholding and IRC penalties

Late 1099s: $60–$330 per form under IRC §6721

Intentional Disregard: $660+ per form, no max

HIPAA Violations: Civil and criminal penalties may apply

I-9 Failures: $281–$2,789 per violation

Retention Errors: Loss of evidence for audits and disputes

Common Preparation Mistakes to Avoid

Using inconsistent name formats between ID, tax documents, and the request, which causes verification failures and delayed processing.
Failing to collect explicit electronic-consent disclosures where consumer-facing records are delivered electronically under ESIGN requirements.
Omitting required tax identifiers (TIN/SSN) or entering them with formatting errors that trigger backup withholding or filing rejections.
Sending unsigned or partially completed requests without validation rules, creating downstream manual corrections and audit exceptions.

Timing Considerations and Related Filing Deadlines

Some requested data tie directly to statutory filing deadlines; collect and verify information early to meet those obligations.

W-9 Delivery:

Provide upon payer request; no fixed deadline

1099-NEC Filing:

Recipient and IRS due Jan 31 each year

1099-MISC Paper:

Paper filings to IRS due Feb 28

1099-MISC Electronic:

Electronic filings to IRS due Mar 31

Individual Tax Return:

Form 1040 due Apr 15 (Oct 15 extension possible)

eSignature Pricing Snapshot for Handling Personal Information Requests

Compare vendor starting prices and key features that affect ongoing costs and compliance for electronically collecting personal data.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Practical Tips for Accurate and Efficient Requests

Follow these best practices to minimize errors, support compliance, and make processing predictable.

Standardize Field Formats

Require MM/DD/YYYY for dates, two-letter state codes, and single-format phone numbers so automated validations succeed and downstream systems ingest data reliably.

Minimize Collected Data

Request only the data you need for the stated purpose and document the legal basis for collection to reduce privacy risk and storage obligations.

Use Conditional Fields

Display tax and sensitive fields only when applicable; conditional logic reduces accidental exposure and simplifies the signer experience.

Record Consent Clearly

Include ESIGN-compliant consent language for electronic records, demonstrate access ability, and provide instructions to withdraw consent if required.

Real-World Examples Using a Personal Information Request

These short case arcs show how organizations use a standard request to collect, verify, and store personal data.

Optica Ventures (COO)

Optica introduced an online request to collect investor and vendor data efficiently, reducing back-and-forth communications.

They used a simple, mobile-friendly form for faster completion.
As a result, the operations team reported fewer verification errors and faster onboarding while maintaining traceable consent and an auditable record for future compliance reviews.

Fertility Centers of Illinois

A medical practice adopted an electronic information request for new patients to capture demographics and consent before appointments.

They paired the form with HIPAA addenda.
The centers reduced front-desk processing time and ensured patient data entered into clinical systems matched identity documents, while preserving signed records and audit trails required for audits.

Frequently Asked Questions

Answers to common questions about execution, legal validity, retention, and electronic submission for a Personal Information Request.

Need help? Contact support

Can this be signed electronically?
Yes. Electronic signatures meet the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided intent, consent, attribution, and retention requirements are satisfied; check New York’s ESRA for state-specific rules.
Is notarization required?
Generally no for a standard Personal Information Request. Notarization may be required for related legal instruments (deeds, powers of attorney) depending on state law and the document’s legal effect.
What if the SSN or TIN is incorrect?
An incorrect TIN can trigger backup withholding and penalties under IRC §6721; verify taxpayer identification early and provide instructions for correction to the payer.
How long must records be kept?
Retain according to the longest applicable rule: IRS records 3 years (IRC §6501(a)), HIPAA 6 years (45 CFR §164.530(j)), and any industry-specific timeframes.
Can a signer revoke consent?
Yes, signers can withdraw electronic consent where ESIGN consumer-disclosure rules apply; retain evidence of the withdrawal and follow any contractual or regulatory notice periods.
What identifiers are safest for verification?
Use a government ID plus a secondary check (SMS code, email confirmation, or knowledge-based verification) for higher assurance and a stronger audit trail.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now