STR Platform Data Sharing Laws 2026: What Cities Can Now See

What Changed and Who It Reaches

For years, cities tried to find unlicensed rentals by hand. Code enforcement staff would search Airbnb and Vrbo manually. They would cross-check addresses against permit databases. The process was slow. It was also easy to miss listings because a listing could use a nickname or an incomplete address. Many hosts assumed that being hard to find was enough protection, and for a while that assumption held up against understaffed enforcement teams.

That assumption is now wrong. A host who relied on obscurity in the past now faces a monthly data pipeline that delivers their address, permit status, and booking volume directly to city staff. The consequence for the host is that a listing that was invisible last year is now flagged in the next report. The mechanism is the automated report. Platforms assemble the data without human review, pulling every host record into a single file. That means a city analyst receives a structured file that highlights blank or expired permit fields. For the reader, this removes any buffer between an incomplete listing and an enforcement action. The edge case where obscurity still holds is when a platform falls below the listing threshold for reporting. But even then, a city can still find the listing through other channels, like tax records or guest complaints, so no host should consider themselves safe just because their platform does not report.

The shift started when cities realized manual searches could not scale. New York City had tens of thousands of active listings. San Francisco had thousands more. No code team could keep up because each listing required a separate search and cross-check. So cities changed their approach. Instead of hunting for listings, they started requiring platforms to hand over the data. That change turned enforcement from a search problem into a matching problem, which is much faster for the city and allows for comprehensive coverage of the entire rental market without needing extra staff.

Under the new model, platforms must report host data to local governments on a set schedule. They do not wait for a complaint. They do not wait for a city inspector to search. The data flows automatically, often monthly. This is the core change every host needs to understand. A city that receives a monthly report does not need to prove a violation exists because the report itself shows the gap. For the reader, this means a permit that was valid last month but expired this month will appear in the next report. The consequence for the host is that an expired permit becomes visible within weeks, not months or years. The mechanism is the automated comparison. The city runs the report against its permit database. If the permit number is missing or expired, the listing is flagged. The edge case where this does not apply is a city that has not yet built the system to process the reports. But most large cities have already invested in that infrastructure, so relying on that gap is a gamble that usually fails.

California's AB 1731 is the clearest example. It took effect on January 1, 2025. It covers any platform with 250 or more listings in the state. Those platforms must send monthly reports to local jurisdictions. The reports include the listing address, the host's registration number, and booking activity data. If your registration number is missing or invalid, the city knows immediately. The consequence for the host is that a blank field in the report triggers an inquiry. The mechanism is the field-by-field validation the city runs. For the reader, this means you cannot hide a missing permit behind a busy city department. The edge case is a host whose permit number is entered correctly but the city's database has a typo. That mismatch still flags the listing. So you must verify that your number matches city records exactly.

New York City's Local Law 18 took effect in 2023 and went even further. It required hosts to register before listing. Platforms could not process bookings for unregistered hosts. The result was a sharp drop in available listings. The law did not just share data. It used platform access as the enforcement lever. New Orleans, San Francisco, and several other cities have passed similar rules. The details differ by city, but the direction is the same everywhere. Platforms are now the compliance checkpoint, not just the marketplace. The consequence for the host is that a listing cannot go live without a valid permit on file with the platform. The mechanism is the pre-verification step. The platform checks the permit number against the city's database before the listing is published. For the reader, this means you cannot bypass the registration requirement by listing on a different platform. Each platform runs the same check. The edge case is a city that has a registration-first law but has not yet integrated its database with all platforms. In that case, the platform may accept any number entered, and the city catches the error later in a monthly report.

Why It Matters

Some hosts have operated for years without a permit. They listed under a slightly different address. They used a nickname instead of a legal name. They assumed no one would look. That approach carried real risk before. Now it carries near-certain exposure. The consequence for the host is that a monthly report will show the address and the blank permit field. The mechanism is the automated flag. The city does not need to search. The report highlights the missing field. For the reader, this means a listing that was invisible to code enforcement five years ago is now visible every month. The edge case is a host who lists on a platform that does not report to the city. But even then, the host is only protected until the city passes a new law or the platform changes its policy.

When a platform sends your listing data to the city every month, your address is in a government database. Your booking volume is there too. If your permit number is blank, that field is blank in the report. A city analyst does not need to search for you because the report flags you automatically. The consequence for the host is that a blank field is a direct signal to the city that you may be operating without a permit. The mechanism is the report structure. Every field is a row in a table. A blank row is as visible as a filled one. For the reader, this means you cannot rely on the city being too busy to check. The edge case is a city that receives the report but does not have staff to review it immediately. That delay is temporary because the report is stored and can be reviewed later.

This guide matters even if you are fully compliant. If your permit number is entered incorrectly in your listing, the city's system may flag you as non-compliant. A typo in your registration field can trigger an inquiry. Getting your records right is not just about avoiding fines. It is about making sure the data the platform sends matches what the city has on file. The consequence for the host is that a simple typo can lead to weeks of back-and-forth with the city. The mechanism is the exact-match validation. The city's system compares the permit number in the report to the number in its database. A single character difference causes a mismatch. For the reader, this means you must enter your permit number exactly as it appears on your permit document. The edge case is a city that uses a fuzzy match algorithm. Some cities allow a small margin of error. But you should not rely on that. The safest approach is an exact match.

Fines for non-compliance vary by city. Some cities issue warnings first. Others move straight to fines or listing removal. New York City's enforcement under Local Law 18 resulted in thousands of listings being removed from platforms within months of the law taking effect. A delisted or suspended listing loses revenue every day it is offline. Getting relisted after a compliance action can take weeks. The cost of being unprepared is much higher than the cost of getting compliant now. The mechanism is the data-sharing report itself. The city receives the report and identifies hosts who are not registered. Then it sends a notice. For the reader, this means a notice can arrive without any prior warning. The edge case is a host who receives a notice but can prove the permit number was entered correctly. In that case, the notice may be a data error. But you still need to respond quickly to avoid escalation.

See also: STR Permit Compliance Service 2026 for a breakdown of permit services that can help you stay current.

How It Works

Here is the basic flow. You list your property on a platform. The platform collects your listing details. Those details include your address, your listing ID, and your registration or permit number. Your booking activity is also tracked. Under a data-sharing law, the platform packages that information into a report. The report goes to the city on a set schedule, often monthly, to ensure oversight.

The city receives the report and runs it against its own permit database. If your permit number matches a valid permit, you are clear. If the number is missing, expired, or does not match, the city flags your listing. Depending on the city, the next step may be a notice, a fine, or a request to the platform to remove your listing. The consequence for the host is that a flag can lead to a listing suspension. The mechanism is the automated comparison. The city's system processes the report without human review. For the reader, this means a flag can be generated within hours of the report arriving. The edge case is a city that manually reviews each flag before taking action. That manual review adds time but does not change the outcome if the flag is accurate.

Some cities go further. They require platforms to verify permit numbers before a listing goes live. This is called a registration-first model. New York City used this model under Local Law 18. A host could not publish a listing until the platform confirmed a valid registration number with the city. The platform became the gatekeeper, not just the reporter. The consequence for the host is that you cannot list at all without a valid permit. The mechanism is the pre-verification API call. The platform sends the permit number to the city's system and gets a yes or no response. For the reader, this means you must have a permit before you even start the listing process. The edge case is a city that has not integrated its database with all platforms. In that case, the platform may accept any number, and the city catches the error later.

The exact data fields vary by law. But most data-sharing mandates cover a common set of information.

• The listing's physical address
• The host's name or business name
• The listing's unique platform identifier
• The host's local registration or permit number
• The number of nights booked in the reporting period
• The gross revenue collected in the reporting period

Some laws also require platforms to share the host's contact information. Others require the platform to report whether the host is present during guest stays. The hosted versus non-hosted distinction matters in cities that allow hosted rentals but restrict non-hosted ones. The consequence for the host is that the data report can reveal whether you are following occupancy rules. The mechanism is the field that indicates host presence. For the reader, this means a city can enforce rules about who is allowed to rent. The edge case is a host who is present during some stays but not others. The report may not capture that nuance, so you need to understand how your city defines hosted versus non-hosted.

How to Tell If It Already Applies to You

Start with your city's official website. Search for "short-term rental ordinance" or "short-term rental registration." Most cities that have passed data-sharing laws also have a registration requirement. If your city requires registration, there is a good chance it also has or is building a data-sharing arrangement with platforms.

Look for the ordinance number and the effective date. Check whether the ordinance has been amended recently. Many cities passed initial STR rules years ago and have since added data-sharing provisions. The version you read two years ago may not be current.

Major platforms publish information about the jurisdictions where they collect and remit taxes or share data. Airbnb's Help Center includes a section on local laws and regulations. Look for your city or state in that section. If your jurisdiction is listed, the platform is likely already sharing data or collecting taxes on your behalf.

Check your listing settings too. Many platforms now have a field for your local registration or permit number. If that field exists in your listing, your city almost certainly requires it. A blank field is a red flag in any monthly report the platform sends.

Log into your platform account and go to your listing details. Look for any field labeled "registration number," "permit number," "license number," or similar. If the field is there and blank, fill it in with your valid permit number. If you do not have a permit, that is the first problem to solve. You cannot fix a data-sharing exposure without first getting compliant at the local level.

A host in San Diego found out her listing had been flagged after a monthly report showed a blank permit field. She had a valid permit. She had just never entered the number in her Airbnb listing. The fix took five minutes. The inquiry from the city took three weeks to resolve. Enter your permit number correctly and verify it matches your city's records exactly.

Step-by-Step Procedure

Use this section as a decision checkpoint before you move to the next step.

Decision Criteria

Use this table to assess your exposure. Check each factor against your specific city and platform. If you are unsure about any row, that uncertainty is itself a signal to investigate further.

If you have two or more "Higher Exposure" factors, treat this as urgent. Do not wait for a notice from your city. Get your records in order now.

Data-sharing laws are not the only STR compliance issue you face. They sit alongside zoning rules, building codes, noise ordinances, and insurance requirements. A valid permit does not protect you from a zoning violation. A clean data report does not mean your listing meets fire safety standards.

Data-sharing laws also do not cover every platform equally. Some smaller platforms may fall below the threshold that triggers reporting requirements. But operating on a smaller platform does not make you invisible. Cities can still find listings through other means. And if you later move to a larger platform, you will be subject to reporting immediately.

Finally, these laws do not cover federal tax obligations. Platform data sharing with local governments is separate from IRS reporting. The 1099-K rules that apply to platform income are a different compliance track entirely. Know which track you are on for each obligation.

What to Prepare Before It Matters

There are three records that matter most when a city data request or inquiry arrives. You need your registration record, your tax remittance record, and your listing identifier record. When the city receives a data report, it will compare these records against what the platform sent. The consequence for the host is that a mismatch in any of these three can trigger a flag. The city runs a cross-reference that compares the permit number from the platform report against the permit number in its own database. If your permit number is correct but your tax remittance record shows a gap, the city may still flag you. For the reader, this means you need all three records aligned. The edge case is a host who has a valid permit and has paid taxes but the platform report has a data error. In that case, you need your own records to prove the error.

Your registration record is your permit or license from the city. It should show your name, your property address, the permit number, and the expiration date. Keep a digital copy and a paper copy. Know where both are.

Your tax remittance record shows that occupancy taxes have been paid. If your platform remits taxes on your behalf, download your annual platform statements. They will show the tax amounts collected and remitted. If you remit taxes directly, keep your payment confirmations and any filed returns. Some cities require hosts to file a return even when the platform remits the tax. Check your city's rules on this point specifically.

Your listing identifier record is the unique ID your platform assigns to your listing. This is not your username. It is the number in your listing's URL or in your platform account settings. When a city receives a data report from a platform, it uses this identifier to match the report to a specific listing. If you receive an inquiry, you will need this number to respond accurately.

A compliance file does not need to be complex. A single folder on your computer or in cloud storage works fine. Put your permit, your tax records, your listing IDs, and any city correspondence in that folder. Label each document clearly. Date every screenshot you take. Review the file every time you renew your permit. The goal is to be able to respond to a city inquiry within a few hours, not a few days.

For hosts managing multiple listings, this process is more complex. Each listing may be in a different jurisdiction with different rules. Each listing has its own permit and its own platform identifier. A spreadsheet that tracks each listing's permit number, expiration date, and platform ID can save significant time when an inquiry arrives. See also: State Short-Term Rental Laws and Preemption 2026 for a broader look at how state and local rules interact.

The host who gets flagged is rarely the one who broke the rules on purpose. It is the one who assumed the rules did not apply yet.

Common Mistakes to Avoid

The most common mistake is simple. A host gets a permit, lists the property, and never enters the permit number on the platform. The platform sends a monthly report to the city. The report shows a blank permit field. The city flags the listing. The host gets a notice and spends weeks resolving something that would have taken five minutes to prevent.

Enter your permit number on every platform where you list. Check it after any platform update. Some platform redesigns have reset or moved registration fields. Do not assume the number you entered last year is still there.

Platforms handle some compliance tasks on your behalf. Many platforms collect and remit occupancy taxes in jurisdictions where they have tax agreements. But platforms do not get your permit for you. They do not verify that your listing meets zoning rules. They do not confirm that your property passes fire safety inspections. When a platform says it "remits taxes on your behalf," that means it collects the tax from guests and sends it to the government. It does not mean you have no filing obligation. Do not assume that because the platform handles the money, you have no paperwork to file.

STR permits expire. Many hosts get a permit, list their property, and forget to renew. The permit expires. The platform's next monthly report shows an expired permit number. The city flags the listing. Set a calendar reminder at least 60 days before your permit expires. Some cities have backlogs in processing renewals. Starting early gives you time to handle delays without a gap in your permit status.

If you list on more than one platform, you need to enter your permit number on all of them. A city's data report may come from any platform where your listing appears. A valid permit number on one platform does not protect you if another platform sends a report showing a blank field for the same address. Listing on both Vrbo and Airbnb means managing compliance on both platforms separately.

Use current platform documentation as a guardrail. Start with Airbnb Help, Airbnb host resources, and Airbnb Help before you make a pricing, legal, or operating decision.

Price is not the whole problem because pricing must align with market reality.

Stage decides the right move for your specific property.

Run the same review on one listing before you change the whole business. Pull the next 30 days of availability. Count the gaps, weak weekdays, and blocked weekends. Then compare those dates against your photos, rules, and reviews. Price changes should be surgical. Change one constraint at a time. Give the market seven days to answer before you change the next one.

A good article, course, or coach should make the next action obvious. The output should be a spreadsheet, checklist, message template, pricing rule, or market scorecard you can use today. If the advice stays general, it will not help the listing. If the advice creates one measurable action, you can test it. That is the difference between content that sounds smart and work that changes bookings.

Use current platform documentation as a guardrail. Start with Airbnb Help before you make a pricing, legal, or operating decision.

Do not fix every setting at once. Pick one listing. Pick one week. Pick one rule.

Good pricing is simple to test. Bad pricing hides inside averages.

The tool gives a signal. The operator makes the call.

Frequently Asked Questions

Final Recommendation

The shift from manual discovery to statutory disclosure is not coming. It is already here. California, New York City, San Francisco, and New Orleans have all moved to data-sharing models. More cities are following. The question for every host is not whether this will apply to them. The question is whether they are ready when it does.

Getting ready is not complicated. It is three things: a valid permit entered correctly on every platform, tax records that show you are current, and a file you can open in minutes if a city inquiry arrives. None of that takes more than a few hours to set up. The cost of not doing it is measured in weeks of lost revenue and legal fees.

If you operate in a state or city with an active data-sharing law, check your listing's registration field today. If it is blank, fill it in. If your permit is expired, renew it. If you are not sure which taxes the platform remits and which you owe directly, find out before the next filing deadline. For hosts managing multiple listings across different jurisdictions, the STR permit compliance services reviewed here can help you track expiration dates and permit fields across every listing in one place.

The host who gets through a city data audit without disruption is the one who treated compliance as an operating standard, not a reaction to a notice. Start with your permit number. Enter it on every platform. Verify it matches your city's records exactly. Then open and confirm your revenue records align with what your platform is reporting. Your numbers match on both sides of any inquiry.

Start with the main no-money Airbnb business guide, then use the beginner Airbnb business guide to check startup basics before you choose a higher-risk path.