Online form breach compliance: 20-year data exposure lesson

by Ron Trotto | Nov 9, 2026

Illustration for an article about online form breach compliance

York University confirmed a cybersecurity breach exposing personal information submitted through departmental online forms between 2007 and October 2026. The online form breach compliance question facing every small business owner is straightforward: do the forms your teams build and maintain put you at the same risk?

The answer is yes, and the timeline matters. York University disclosed that an unauthorized actor accessed online forms used by university departments, exposing criminal background and health information dating back two decades. The institution is notifying individuals whose personal information was compromised.

Why do departmental forms create compliance risk?

Picture a professional services firm where the HR manager creates a Google Form to collect background check authorizations, or a medical practice where a clinic coordinator builds a patient intake form in Microsoft Forms. Both sit outside the systems your IT provider or compliance consultant knows about.

When a breach occurs, you face notification obligations for every record exposed. The longer you retain data, the larger the exposure. York University’s breach stretched back to 2007, meaning records nearly twenty years old remained accessible to an attacker.

Ask yourself: does every department head or office manager know which forms they maintain, what data those forms collect, and whether they still need it? If the answer takes longer than a day to assemble, the compliance risk is already present.

What information do departmental forms typically hold?

The York University incident exposed criminal background and health information. In a small business context, departmental forms often collect:

  • Employment applications containing Social Security numbers and references
  • Background check authorizations with dates of birth and consent records
  • Client intake forms holding addresses, payment details, and service notes
  • Volunteer or contractor onboarding documents with identification and emergency contacts
  • Internal request forms capturing employee health accommodations or leave reasons

Each category may trigger different notification obligations when breached. Health information falls under one set of rules, financial account details under another, and Social Security numbers under state-specific timelines.

How long should you retain form data?

Retention creates exposure. The York University breach demonstrated that holding data from 2007 through 2026 meant notifying individuals who submitted information nearly two decades ago, many of whom no longer have any relationship with the institution.

Establish retention schedules tied to operational need, not storage convenience. For employment applications, retain finalist documents according to your counsel’s guidance on discrimination claim windows, then destroy the rest. For background check records, keep what your attorney advises for the employment relationship, then delete.

Audit your forms twice a year. Identify what each form collects, where responses are stored, who has access, and whether the data still serves a business purpose. If a form hasn’t been used in eighteen months, archive or delete the responses and disable the form.

How do you bring shadow forms under compliance control?

Start with inventory. Require every department to list the forms they maintain, the data collected, the storage location (shared drive, form service, email inbox), and the retention period. Set a deadline measured in weeks, not months, and make one person accountable for the complete list.

Classify each form by the sensitivity of data collected. Criminal background checks and health information demand encryption, access logging, and formal retention policies. Lunch orders and conference room bookings do not. Focus your resources where the compliance exposure lives.

Centralize form creation through a designated IT contact or compliance officer. Ban the practice of individual managers spinning up new data-collection forms without review. A simple approval gate catches forms before they accumulate years of unprotected data.

Move high-risk data out of general-purpose form tools. If you collect information that triggers breach notification obligations, store it in a system designed for regulated data, not a department manager’s personal productivity app.

What does breach notification look like for old data?

York University is notifying those whose personal information was compromised. When exposed data spans years or decades, notification becomes an operational and reputational burden.

Suppose your firm discovers a breach in an employment application form that has collected submissions for ten years. You must attempt to notify every applicant, including those you never hired, at addresses and email accounts that may no longer be current. Each failed delivery requires additional effort, and each successful one reopens a relationship that ended years ago.

The cost is not just postage and attorney time. Contacting hundreds or thousands of individuals you no longer serve generates questions, complaints, and attention you would rather avoid. Former applicants ask what you did with their data, why you kept it so long, and whether identity theft protection is provided.

Minimize that scenario by destroying data promptly. If you cannot articulate a business reason to retain a record, you are keeping it for convenience, and that convenience becomes expensive during breach response.

How do you secure forms already in use?

For forms you must keep active, apply the same controls you use for any regulated system. Require multi-factor authentication for accounts that access form responses. Enable access logging so you can see who viewed submissions and when.

Review permissions quarterly. Form creators often grant access to colleagues who move to other roles or leave the organization entirely. Those orphaned permissions remain until someone actively revokes them. Schedule a recurring task: every quarter, confirm that only current personnel with a need to access the data still hold permissions.

Store responses in a location your IT provider monitors. If form submissions land in a personal email inbox or a consumer cloud account, your managed security tools cannot detect unauthorized access. Route responses to a business account within your managed environment.

Test your incident response for forms. Simulate a scenario: a form containing client payment details is compromised. Who gets notified first? Who determines the notification list? Who drafts the message, and who reviews it before it goes out? If those questions do not have documented answers, write them now.

Should you audit third-party form services?

York University’s breach involved forms used by university departments, but the excerpt does not specify whether the forms were hosted by the institution or a third-party service. Either way, the university bears the compliance burden.

If your teams use form services, treat each one as a vendor relationship. Obtain a contract or terms of service that address data ownership, breach notification timelines, and liability. Ask where the data is stored, who can access it, and whether the service encrypts responses at rest.

Assume that any free consumer-grade tool does not meet your compliance obligations unless you verify otherwise. Free services are designed for convenience, not for handling employment records or client intake data. If you cannot get acceptable terms from the vendor, move the data to a service that provides them, or bring the form in-house under IT oversight.

Document your vendor assessment. When an auditor or regulator asks how you vetted a form service that later suffered a breach, produce the assessment, the contract, and the decision record. That documentation does not prevent a breach, but it demonstrates that you exercised judgment rather than allowing departments to adopt tools at will.

What is the one step to take this week?

Inventory your forms. Send a request to every department head and manager: list every form you maintain, what data it collects, where responses are stored, and who has access. Set a response deadline within the week, and compile the results into a single list.

Review that list with your IT provider or compliance counsel. Identify which forms collect regulated data, which have been active for years without a retention policy, and which sit in locations your security tools do not monitor. Those three categories define your immediate compliance gap.

Pick the highest-risk form on the list and bring it under control first. Migrate the data to a secure location, restrict access to current personnel only, and establish a retention policy. Then move to the next. Steady progress across six months will close the gap that a single audit would expose.

FAQ: Online form breach compliance

What makes a departmental form a compliance risk?

A departmental form becomes a compliance risk when it collects regulated information (names, Social Security numbers, health data, financial account details) but sits outside the systems your IT and compliance teams monitor and protect. Breaches in those forms trigger the same notification obligations as breaches in your core business systems, but the decentralized nature of form creation means you may not discover the exposure until an incident occurs.

How long should we keep employment application forms?

Retain finalist employment applications and background check records according to your attorney’s guidance, which will reflect your jurisdiction’s statute of limitations for discrimination claims. Destroy non-finalist applications promptly once the position is filled. Holding applications longer than necessary multiplies your breach exposure and notification burden without adding business value.

Do free form services meet compliance requirements?

Assume that free consumer-grade form services do not meet compliance requirements unless you verify their terms, data storage practices, and breach notification procedures. Free tools are built for convenience, not for regulated data. Obtain a written agreement that addresses data ownership, security controls, and vendor notification timelines, or migrate regulated data to a service that provides acceptable terms.

Who should approve new data-collection forms?

Designate one person, typically your IT lead or compliance officer, to review and approve every new form before it goes live. The review should confirm that the form collects only necessary data, stores responses in a secure location, and includes a documented retention policy. A simple approval gate prevents departments from creating unsecured data stores that accumulate exposure over time.

What is the first step to secure existing forms?

Inventory every form your organization maintains, noting what data each collects, where responses are stored, and who has access. Then classify forms by data sensitivity and focus on high-risk forms first (those collecting health, financial, or identification data). Secure those forms by migrating data to monitored systems, restricting access to current personnel, and establishing retention policies.

Keep reading

Sources

Source: York University data breach exposes personal information – Inside Halton

Researched and drafted with AI, then reviewed and approved by Ron Trotto before publishing.