Terms of service

1. Who you are agreeing with

These terms are an agreement between you and Valya AI Corp, a Colorado corporation with its place of business in Sandpoint, Idaho, doing business as Permity USA ("Valya AI", "we", "us", "our"). Permity is the name of the service Valya AI operates; it is not a separate company. Where these terms say "Permity" they mean the service, and where they say "we" they mean Valya AI. "You" means the person or company holding the account, or the person buying a single report without one. If you accept for a company, you are confirming that you may bind it, and "you" means that company. The service is for businesses and adults. You must be at least 18.

Five words carry a fixed meaning on this page. "Data" means everything the service gives you: every report, every answer from the API or a connected app, and every record, name, date, summary, building fact, address suggestion, map and image in them, together with anything you make from them. A "report" is one answer about one property, as we delivered it. A "connected app" is any software that reaches Permity with your credentials: a key from your API keys page, an AI assistant you signed in to your account, the Zapier app, or code of your own. A "name" means the name of a person or a company as it appears in a report or export: an owner of record, a party to a recorded transfer, or a contractor named on a permit. "Outreach" means contacting a person, or sending them anything, to promote or sell goods or services, whether in person, by post, by phone, by text message, by email or by any messaging app.

2. The service

Permity reports the building-permit history of a property address, through a web application, an HTTP API, an MCP server for software agents (which is what an AI assistant such as Claude connects to), a Zapier app, and an iOS app. Whichever of those you use, the rules on this page apply: the same limits on the data, the same licence, the same prices, and the same question before you are charged twice for one property.

3. What the data is, and is not

Our answers are built from records that issuing jurisdictions publish, which we collect, and from data we license from others. On top of those we do work of our own. We resolve the address you typed to a property, match records to it, choose which date to report for each trade, combine records that come to us separately, and sometimes infer something (for example, that a system is probably original) and label it as an inference. So a report has two layers, and they carry different limits.

The records are the jurisdiction’s, not ours. We do not inspect the property, and we do not guarantee that a jurisdiction’s record is accurate, complete, current or correctly coded. Where a record is wrong or late, our answer can be wrong or late.

The matching, the summaries and the inferences are ours. We take care over them, and we say where each one came from, but they are our reading of the records rather than the records themselves, and they can be wrong in ways the record is not: an address can resolve to the wrong property, two records that describe different work can be combined, and an inference is a guess with its basis attached, never a measurement.

Four limits follow, and they are the most important thing on this page.

Unpermitted work does not appear. A roof replaced without a permit leaves no record anywhere in this product. Absence of a permit is not evidence that work was not done. A property showing no permits may have had extensive work.

Not every jurisdiction reports. Where coverage is thin we say so explicitly rather than returning silence that looks like a negative answer. A result marked no_coverage means we know nothing, not that nothing happened.

A date is not always a completion. Every year we return is accompanied by which field it came from. A permit filed in 2012 and work completed in 2012 are different claims, and we distinguish them rather than flattening both to a number.

What we hold is a copy, and it lags. Every record we hold is refreshed on its own schedule and never in real time. A permit issued this morning may not be in our answer this afternoon, a jurisdiction that stops publishing can leave what we hold frozen without our knowing, and a record amended or withdrawn after we copied it may stay as we copied it. The only current record of a property is the jurisdiction’s own.

Some of the data is licensed to us by others, and some is published by public bodies on conditions of their own. That data reaches you on those conditions, and section 7 passes them on.

Permity is not an inspection, a survey, a title search, a lien or encumbrance search, an appraisal or a certification of code compliance. Where a report shows a value, it is an estimate of market value, not an appraisal, and market value is not the cost to rebuild. It is not engineering, architectural, legal, insurance, tax or investment advice, and nothing in a report is the opinion of a licensed professional. It is one input to a decision that you make and that you own.

4. What a report establishes, and the decisions you make on it

You decide what to do with the data. You may use Permity when pricing, quoting, underwriting, renewing or servicing a property insurance policy, including when deciding whether to offer, decline, renew, surcharge or rate a policy on a property. You may use it when buying, selling, valuing, lending against, inspecting, insuring or managing a property. Each of those is a decision you make, on information you chose to rely on, and it is yours: its consequences, the standard of care it has to meet, and any duty you owe a person it affects. Valya AI does not make, recommend or take part in any decision, and is not liable for one, however it was reached and whatever it cost. Section 16 says the same thing in the words a court expects.

Use a report for what it establishes, and no more. A report establishes what the issuing jurisdiction has published about permits at a property, and what the county has recorded about the building, as we matched, combined and summarised it on the day you ran it. A value in a report is an estimate. A hail report in a report says that hail of a size was reported near the property on a date, and nothing about any roof. A report does not establish that work was or was not done, when a roof or any other system was last replaced, the condition of anything at the property, whether the property complies with any code, or anything about a person. Absence of a permit in our data is not evidence that work was not done, and no_coverage is not evidence of anything.

A report is not a substitute for an inspection. Where a law, a regulator or your own standards require a decision to rest on an inspection or on verified property characteristics, a report does not supply them. Where a decision needs more than a report establishes, the rest is yours to obtain, and the decision is still yours.

Do not present a report as proving what it does not. Do not offer the absence of a permit in our data as evidence that work was not done, was not permitted, or was done badly, and do not present a report as proof of any of those things in a claim, a coverage dispute, a negligence case or a legal proceeding, including a case about whether an agent, broker, inspector, contractor or other professional failed to discover, disclose or act on work at a property. Absence in our data is not absence of a permit, and absence of a permit is not absence of work. Nothing here stops you producing a report, intact, where a court, a regulator or a law requires it; what you may not do is describe it as establishing something it does not.

A report is about a parcel. Where the public record names them, a report may show the owner of record, the parties to recorded transfers, and the contractor named on a permit, as the county or the issuing authority recorded them, on the date shown. We do not verify these names and we do not evaluate anyone.

Property facts may inform insurance. Names may not. You may use the property facts in a report (permits, years, flags and building facts) when you price, quote, underwrite, renew or service a property insurance policy. Names are different. Do not use a name, or anything in the data about who a person is, to decide whether to offer, price, decline, renew or cancel insurance for an individual, or to decide whether an individual is eligible for credit, employment, housing, tenant screening or any other benefit. If a law such as the Fair Credit Reporting Act or a state equivalent governs the way you use a report, complying with it is your responsibility, and by using the service you confirm that you will not use a report, or let anyone use it, in a way that would make it a consumer report in your hands, unless we have agreed otherwise in a signed agreement. These terms are not a certification of anything, and we give none.

If you tell us you are an insurer, an agency or an underwriter, we may not show you names at all.

What we do not provide. Valya AI does not give audit rights, model documentation, validation reports or help with a regulator’s inquiry about your use of the data, except under a signed agreement. The service is a set of records and summaries. It does not score, rate, rank or decide anything about a person, and it is not an automated decision-making system. If you use the data as an input to a system that makes or assists a decision about a person, you are responsible for that system and for any notice, review or correction right the law gives the person.

5. Names of people, and outreach

A name is a record, not a lead. A name in the data is copied from a public record as the county or authority wrote it. It can be out of date, because a sale may not be recorded yet. It can be a trust or a company rather than the person who lives there. It does not tell you who occupies the property or who can authorise work on it.

What you may use a name for. You may use a name (a) to understand the record: whether a permit belongs to this property, who held the property when, who the county says pulled a permit; and (b) if you ticked "Include owner names" on an export and accepted the notice shown there, or the export was made by a key whose holder turned on owner names for it and accepted the notice shown there, to contact the owner of a listed property about your own goods or services, in person, by post, or in any other way the law allows.

What you may not use a name for. Do not use a name, alone or with anything else, to follow, locate, surveil, threaten, pressure or harass a person; to decide whether a person is eligible for credit, insurance, employment, housing, tenant screening or any other benefit; to evaluate, rate or screen a person or a contractor; to treat people differently because of race, colour, religion, sex, national origin, disability, family status or any other protected characteristic; to build a database or list of people that you sell, share or give to anyone outside your business; or to pretend that you act for the owner’s insurer, the county or us. We do not supply phone numbers, email addresses or mailing addresses. If you find them elsewhere and use them, the law that governs that contact is yours to follow, and we take no part in it. A contractor’s name on a permit says the permit named them. It does not establish who performed particular work, the quality of that work, or whether anyone was negligent.

The law on contacting people is yours. Outreach is regulated: telephone and text rules (including the National Do Not Call list, the Telephone Consumer Protection Act and state laws on telemarketing and texts), email rules (including the CAN-SPAM Act), door-to-door sales and solicitor permit rules, and the rules for roofing and storm repair in the state where you work (licensing, contract notices, cancellation rights, and bans on offering to pay or waive an insurance deductible). You are responsible for knowing which apply, for the licences and registrations you need, and for every contact you make. We may show a reminder about some of these in the service. A reminder is a courtesy, it is not complete, and it is not legal advice.

Stop when asked. If a person asks you to stop contacting them, or asks you not to keep their name, you stop and delete their name from your lists and files within ten days. If we send you a removal notice for a name, you do the same. We send one only when the person has asked us to remove the name. Honour any no-soliciting sign.

Your confirmation, and our log. Each time you export names you confirm the notice shown with the export, or, for a key, the notice its holder accepted when turning names on for it. We keep a log of each names export (which account, which key, when, how many names and which states) and may use it to investigate misuse or answer a legal request.

Names can be switched off. We may stop showing names for a state, a county, an account, a key or a single person if a law, a county, a person’s request or our own judgment requires it. That is not a breach of these terms. We do not charge for names we do not deliver.

6. Your licence to the data

While your account is active and in good standing, we grant you a limited, non-exclusive, non-transferable, non-sublicensable licence to use the data for your own internal business purposes: insuring, underwriting, quoting, buying, selling, lending against, servicing, inspecting or managing properties you have a legitimate business reason to look up, properties on a list you already hold for one of those reasons, and outreach to the owners of properties as section 5 allows. The licence covers the data you obtained while it was in force. It ends when your account closes, when your subscription lapses, or when our own right to supply a part of the data ends, whichever comes first, and section 18 says what happens then. We keep every right we do not grant here. The service, its software, its design and its text are ours or our licensors’; the public records inside it belong to nobody, and nothing here claims them.

Names are licensed more narrowly. A names export is for outreach about the properties on it, by your business, for twelve months from the day you export it. After that, delete the names.

Within that licence you may look up properties, keep each report for as long as the property or client it concerns needs it, pass answers into your own systems, CRM and workflows for your own use, and share an intact individual report with a person it concerns, as section 13 says. A person who buys a single report without an account gets the same licence for that one report, for personal or business use.

If you want to do something this licence does not cover, ask. The answer is a separate written agreement, and the Enterprise plan exists for it.

7. What you may not do with the data

The principle: you may use Permity inside your own business, for your own clients and properties, as much as your plan allows. You may not turn Permity into someone else’s supply of data. Each rule below is that principle applied.

(a) No redistribution. Do not sell, resell, rent, lend, transfer, distribute, publish, sublicense or otherwise make the data, or any part of it, available to anyone outside your business, except an intact individual report shared as section 13 allows. Do not sell, resell, sublicense or charge anyone for a report, or for access to one, without Valya AI’s prior written permission.

(b) No public posting. Do not post a report or its contents where people you have not identified can read it: a public website, a listing, a forum, a shared drive open to the public, a social network.

(c) No pass-through access. Do not let anyone outside your business query Permity through your account, your key, your app, your AI agent or your Zap, and do not build or run a service, a bot, an assistant or a product that answers other people’s questions from the data. Output from the API, the MCP server or the Zapier app stays inside your own systems, for your own use.

(d) No derived datasets. Do not copy, modify or create derivative works from the data, including any dataset, database, directory, listing, index, model, score or data product built from it, whether or not you charge for it.

(e) No bulk or automated collection. Reach Permity only through the website, the apps, the API, the MCP server and the Zapier app, within your plan. Do not crawl or scrape the website, do not collect from it with automated tools, and do not make systematic pulls through any door to build a copy of what we hold.

(f) No warehousing. Keep what the property or client in front of you needs, for as long as that matter needs it, and no longer than your licence lasts. Do not keep a warehouse or bulk copy of the data, and do not keep anything to rebuild, in whole or in part, the database the service answers from.

(g) No AI or machine-learning use. Do not use the data to train, test, validate, fine-tune, evaluate or improve any machine-learning or artificial intelligence model, and do not hand it to a model for anyone else to do so. Asking an AI assistant you have connected to your account to read an answer to you is use, not training, and is allowed. Do not give names to any model, tool or service that keeps them or trains on them.

(h) No competing product. Do not use the service or the data to build or operate a product, service, API, database or platform that competes with Permity or with anyone who supplies data to us, and do not gather information for someone who does.

(i) Address suggestions, maps and imagery are for use while you use the service. Use an address suggestion only to choose the address for a lookup inside the application you are using. Do not copy, store, index, export, re-host, bulk download or screen-capture suggestions, maps or imagery for reuse, do not use them to build a listing, directory, mapping or address product, and do not use them to train or improve any model.

(j) Notices stay. Do not remove, obscure or alter any copyright, proprietary, attribution or map notice, logo or link that the service or a report displays, and do not strip a report of its limitations.

(k) No circumvention. Do not work around a rate limit, an allowance, a security feature, a pause on a key, or a jurisdiction’s own terms.

(l) No harm to a person. Section 5 applies to every name, and nothing in the data may be used to harass, profile or locate an individual.

(m) No lists of people. Do not combine names from the service with names from anywhere else to build a list, directory or database of people, and do not give or sell a list of names to anyone outside your business. Your employees and contractors working the same properties for you may use it.

(n) No unlawful contact. Do not use the data to contact a person in a way the law forbids, or to contact a person after they have asked you to stop.

Conditions set by others. Some of the data is licensed to us by others, and some is published by public bodies under a licence or with conditions, including a requirement to credit the body that issued a record. Those conditions apply to your use of that data too, and these terms pass them on. Where we must tell you of such a condition, we will, and you will comply with it. You will not use the service in a way that would put us in breach of our obligations to anyone who supplies data to us.

The service includes Google Maps features and content. Use of those features and content is subject to the then-current Google Maps End User Additional Terms of Service (https://maps.google.com/help/terms_maps/) and the Google Privacy Policy (https://policies.google.com/privacy). If you place the service inside a product of your own, that product’s terms must carry the same notice.

Postal city names are derived from GeoNames (geonames.org), licensed under CC BY 4.0.

If you use the iOS app, Apple’s standard licence for apps (the Apple Media Services terms and the standard Licensed Application End User License Agreement) also applies, and Apple is not a party to these terms.

Written permission means a signed agreement or an email from us granting it. A conversation, a website, a product name or a silence is not permission.

This list is what we have thought of. It is not exhaustive. If your use depends on our data being complete, current or independently verified, it is out of scope here, and the right answer is a separate written agreement, not these terms.

8. Connected apps, keys, AI assistants, and the people who use your account

A connected app acts for you. When you give an AI assistant, the Zapier app, a script or any other software access to your account, by signing in to it or by giving it a key, it acts on your behalf. Every request it makes is your request, every lookup it spends is your lookup, and everything it does with an answer is done by you. Read what it asks before it asks, and read what it says a lookup will cost, because the confirmation it gives us is your consent. You are responsible for what a connected app requests, spends and does with the answers, and for what the people who use the assistant through your account do with them. Granting a connected app access costs nothing; the lookups it runs are charged exactly as yours are. You can revoke a connected app at any time on your API keys page, and revoking it stops it at once.

An AI assistant is not a person. It can be wrong, and text inside the data or inside a page it reads can steer it. You review what an assistant does before anything is sent to a person. Do not let an assistant contact owners, decide anything about a person, or export names unless a person has read and accepted the notice that comes with the export. Answers an assistant writes from our data are your statements, not ours. If you give names to a model run by someone else, you are responsible for what that operator keeps or learns from them, and you must use settings that do not retain them or train on them.

Your key is your responsibility. Anything done with it counts as done by you until you tell us it is exposed and we revoke it, unless the exposure was caused by us. Keys are shown once and stored only as a digest, so a lost key is replaced rather than recovered. Tell us promptly if one is exposed and we will revoke it. Every key on an account spends from the same allowance. A key receives names on an export only if its holder turned owner names on for it and accepted the notice there; you can turn that off for any key at any time.

Everyone on your account is bound. You will see that every employee, contractor, agent and connected app that uses your account follows these terms, and a breach by any of them is a breach by you.

9. Reporting a wrong match

If a report matches the wrong property, attributes a permit to the wrong address, combines records that do not belong together, or summarises a record in a way you believe is wrong, tell us at nate@valyaai.us and quote the request id printed on the report. We will review it within ten business days, tell you what we found, and correct what is ours to correct: our matching, our summary or our inference. We cannot change a jurisdiction’s record. Where the record is wrong we will say so, and where the jurisdiction offers a way to correct it we will point you to it. A lookup that returned the wrong property because of our error is not charged, and if it was, the charge is returned.

10. If your name is in a report or an export

Names in our reports come from public records, and you can ask us to remove yours. Use the form on our privacy page, or email nate@valyaai.us, with the name as it appears and the property address. Within ten business days we stop showing that name, for that address, in reports and exports we deliver from then on, and we tell you when it is done. We keep a short record of the request (the name, the address, your email address and the date) so the removal holds, and we use it for nothing else. If you are a judge, prosecutor, police officer or anyone else whose address a law protects, say so and we act as quickly as we can. We cannot change the county’s record, and we will tell you where to ask the county to correct it. If a name is wrong, tell us the same way.

A customer who received your name in an export before we removed it must still stop contacting you when you ask them to, and delete your name, as section 5 says.

11. Billing

Subscriptions carry an included allowance of lookups, and the allowance is monthly on every plan. You can pay monthly or a year at a time; paying yearly costs 15% less and buys twelve monthly allowances, not one large one. Once your allowance and any credits are used, lookups pause until the allowance resets or you add credits. Nothing is charged beyond your allowance unless you buy it.

What a lookup is. A lookup is one property, answered: we identified the property you asked about and reported what we hold for it. An answer that the property has no permits on record is an answer, it is often the one you were buying, and it costs a full lookup. So does an answer that the jurisdiction does not report to us (no_coverage). That is not evidence about the property; it is the cost of the search, and we would rather say so here than at the charge.

Opening a report you already have is free. Running a lookup again is charged. Every lookup you run counts against your allowance, however recently you ran the same property, and whether or not the answer turns out to have changed. Reports stay retrievable for their full 90 days and opening one costs nothing, ever.

We ask before charging you twice for the same property. When you run a property this account has run in the last 30 days, we tell you first: when you ran it, whether we can tell that anything has been published since, a link to the report you already have, and what running it again would cost. That is a question, not a charge, and asking is free. Saying yes, in whichever interface you are using (the web app, the API, the MCP server or the iOS app), is your consent to be charged for that run. It is consent for that property and that run only. A re-run costs one lookup, from your monthly allowance if any remains and otherwise from your credits; the prompt says which we expect, and the response says what was actually taken.

We can only ask when we already know which property you mean. If the address you sent has to be resolved afresh before we can tell whether you have run it, the lookup runs and is charged, because finding out would itself cost us a paid call. On the API, your request says whether you want to be asked (on_repeat: "prompt"), or whether a property you ran in the last 30 days should simply be answered from the report you already have for nothing (on_repeat: "reuse"), which is what the Zapier app sends; a request that asks for neither is run and charged, because a client that is not listening cannot answer. On the MCP server, a property you ran in the last 30 days is reopened from the report you already have, free, and running it again is a separate tool that the assistant may call only after telling you it costs a lookup. A batch never asks, for the reasons below.

Retries. The API accepts an Idempotency-Key. A request repeated with the same key and the same body within 24 hours returns the original answer and is not charged again. A request repeated without one is a new lookup and is charged, because we cannot tell a retry from a fresh ask.

A batch runs every row and charges every row. Uploading a file does not reuse answers from an earlier run, and nobody is asked before a row runs, so addresses you have run before will be run again and charged again, including addresses that repeat within the file.

Where the API offers a street comparison, it is its own answer and its own lookup. Comparing a property to its block is a different question from what permits the property has, and it is charged separately from the property’s lookup.

Two failed lookups cost one lookup between them. A failure is an address we could not identify, or one that matched several properties and left you to choose. The first failure in a pair takes nothing from your allowance and the second takes one lookup for both. This is not a half credit you can spend: it is a whole lookup, deducted on the second failure, and an odd failure carries over, into the next month and through a cancellation, until it is paired. If the fault is ours (our systems, or the data behind them, were unavailable) you are charged nothing and the failure is not counted.

Building facts alone cost half a lookup. Asking only what a building is, without its permits, costs half a lookup when facts come back and nothing when none do. Halves pair the same way failed lookups do: the first half takes nothing from your allowance, and the next half, from building facts or a failed lookup, takes one lookup for both.

Exports are free. Saving an area, exporting it as a spreadsheet, a map file or a PDF, and including owner names in an export where that is offered, spends no lookup: every number in an export comes from reports you already paid for.

An annual subscription is billed in full on the day you buy it, and it is not refundable. Not in part, not pro-rated, not for months you did not use. If that is not a bet you want to make, pay monthly: the price is the only difference.

Cancel any time from your billing page. Cancelling stops the next renewal; it does not end the period you have already paid for and does not return money for it. A monthly plan runs to the end of its month, an annual plan to the end of its year, and the lookups stay available until then.

If a payment fails, lookups stop and reports do not. Every report generated while you were paying stays retrievable for its full 90 days. We think revoking work you already paid for is the wrong way to collect a debt.

Credit packs are lookups bought once, at the price shown, charged in full when bought. They are spent only after the month’s allowance and do not reset with it. They are good for twelve months from purchase and are then forfeited. They are not refundable once any credit from the pack has been used; an unused pack can be refunded on request within fourteen days. Unused credits are not refunded when a subscription is cancelled; they stay on the account for their twelve months and can be spent again if the subscription is restarted.

Charges we got wrong are returned. If we charge you for something this page says is free, or for a failure that was ours, tell us and we return it: to your allowance or your credits, whichever it came from, or to your card where that is where it came from. That is owed in full, and nothing in the liability section limits it.

There is no free tier and no trial allowance. An account with no subscription can sign in and read its reports, but cannot spend a lookup: every lookup costs us money, and we would rather charge for it than pretend it is free.

12. Buying one report without an account

You can buy one report for one property, at the price shown, without an account. It is a purchase rather than an allowance: it is charged once, when you buy it, and buying the same report twice is charged twice, because without an account we hold no record of what you have run and cannot ask you first. If we cannot produce the report, you are not charged. If we deliver a report for the wrong property, we refund the purchase, and that refund is your remedy for a single report; it is not limited by the liability section. A report bought this way is delivered by a signed link that expires, and it is retained for 90 days like every other report. Everything on this page about what the data is and is not, about what a report establishes, about names, and about what you may and may not do with the data applies to it. The indemnity below does not apply to a report bought for personal, family or household use. The limits on our liability apply to such a purchase only to the extent the law allows, and nothing in these terms takes away a right you have under consumer-protection law that cannot be limited by agreement.

13. Reports you share

You may share a report you have generated, intact, by its signed link, by email or as the file, with a person it concerns and who you have a legitimate reason to show it to: your client, an underwriter, a buyer, a seller, a lender, an inspector, a colleague working the same matter. A report you share is for that person’s own use on that matter. They may keep it and act on it; they may not pass it on as data, and you will not send it to them so that they can. What you may not do is alter a report, strip it of its limitations, share it with people you have not identified, or redistribute the records in it as a dataset. Section 7 applies to every copy.

No resale. Sharing a report is free, and a report you share is for the recipient’s own use. You may not sell, resell, sublicense or otherwise charge anyone for a report, or for access to one, without the prior written permission of Valya AI Corp, doing business as Permity USA. Written permission means a signed agreement or an email from us granting it; a conversation, a website or a silence is not permission. If you quote or summarise a report, carry its limits with it: which field a date came from, what no_coverage means, and that unpermitted work does not appear.

Forwarding a report does not make the person who opens it a party to these terms, and does not bind them to anything on this page. Every report carries, on every page, the same statement about unpermitted work that appears here, so a reader who never agreed to anything still sees the limit. You are responsible for what you send, to whom, for what you say about it, and, as section 17 says, for what the recipient does with it.

A signed link expires seven days after it is issued. The report behind it is retained for 90 days from generation and then deleted. A copy someone has downloaded is outside our control, and we cannot promise to delete it.

14. Availability

We depend on data we do not control and do not promise uninterrupted service. When the data behind an answer is unavailable we return a distinct error rather than a confident wrong answer, and that error is not charged. We may change, withhold or withdraw a feature, a jurisdiction or a kind of data at any time, including because our own right to supply it has ended; where that cuts what you have already paid for, section 19 says what notice you get. We are not responsible for a failure or delay caused by something outside our reasonable control, including a jurisdiction’s own systems, a hosting or network failure, a change in the law, or a loss of supply of data.

15. No warranty

THE SERVICE, EVERY REPORT, AND ALL DATA IN THEM ARE PROVIDED "AS IS" AND "AS AVAILABLE", WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND. TO THE FULLEST EXTENT PERMITTED BY LAW WE DISCLAIM ALL WARRANTIES, EXPRESS, IMPLIED AND STATUTORY, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AND ANY WARRANTY ARISING FROM A COURSE OF DEALING OR A USAGE OF TRADE.

In particular, we do not warrant that the data is accurate, complete, current or free from error, that a property’s permit history is fully represented, that any jurisdiction’s records have been received or are up to date, that our matching, summaries or inferences are correct, that any name is correct, current or the name of an occupant, that a summary an AI assistant writes from our data is accurate, that any outreach you make will be lawful or successful, that a map, address suggestion or image is accurate or available, that the service will be uninterrupted, or that results will meet your requirements or any standard that applies to your profession or licence. You verify what you rely on. No information you get from us, in any form or from any person, creates a warranty we have not given here. This disclaimer does not cancel the specific promises this page makes about prices, refunds and the return of charges we got wrong.

Some states do not allow the exclusion of certain warranties or the limitation of certain damages. Where that is so, the exclusions and limits in these terms apply to the fullest extent permitted, and nothing here limits a right you have that cannot be limited by agreement.

16. Limit of our liability

TO THE FULLEST EXTENT PERMITTED BY LAW, WE ARE NOT LIABLE FOR ANY USE MADE OF THE DATA BY YOU, BY A CONNECTED APP, BY A USER OF YOUR ACCOUNT OR BY ANYONE YOU SHARE IT WITH, OR FOR ANY DECISION MADE, ACTION TAKEN OR NOT TAKEN, OR OUTCOME REACHED IN RELIANCE ON IT, INCLUDING A DECISION TO OFFER, PRICE, DECLINE, RENEW OR CANCEL INSURANCE, TO BUY, SELL, VALUE OR LEND AGAINST A PROPERTY, OR TO DO OR NOT DO WORK ON ONE. WE ARE NOT LIABLE FOR ANY CONTACT YOU MAKE WITH A PERSON, OR FOR ANY CLAIM OR PENALTY UNDER A LAW ABOUT MARKETING, TELEPHONE CALLS, TEXT MESSAGES, EMAIL, DOOR-TO-DOOR SALES, ROOFING OR INSURANCE CLAIMS.

TO THE FULLEST EXTENT PERMITTED BY LAW, WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST REVENUE, LOST BUSINESS, LOSS OF GOODWILL, LOSS OF DATA, UNDERWRITING LOSSES, RESERVE OR PRICING DEFICIENCIES, CLAIMS PAID OR DENIED, OR REGULATORY FINES OR PENALTIES, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER OR NOT WE WERE TOLD SUCH DAMAGES WERE POSSIBLE.

OUR TOTAL LIABILITY TO YOU FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THE SERVICE, TAKEN TOGETHER, WILL NOT EXCEED THE GREATER OF (A) THE FEES YOU PAID US IN THE TWELVE MONTHS BEFORE THE FIRST EVENT GIVING RISE TO A CLAIM AND (B) ONE HUNDRED US DOLLARS. That is one aggregate cap across every claim you may have, not a cap for each one, and it applies whatever the theory: contract, tort, negligence, misrepresentation, statute or anything else.

Neither the exclusions nor the cap above applies to our fraud or fraudulent misrepresentation, our wilful misconduct, our wilful and wanton or grossly negligent conduct, our liability for death or personal injury caused by our negligence, or anything else the law does not permit us to limit. Nor do they apply to money this page says we will give back: a refund we promised, a charge we got wrong, and the price of a single report delivered for the wrong property are owed in full, and they are not damages.

These limits are a basic part of the bargain between us. The price reflects them, and without them the service would not be offered at this price.

17. Your indemnity

This section is for business use of Permity. It does not apply to a report bought for personal, family or household purposes.

You will defend, indemnify and hold harmless Valya AI and its officers, employees, contractors and licensors against any claim, demand or proceeding brought by someone else, including by anyone who supplies data to us, and against the resulting losses, liabilities, damages, penalties and reasonable legal fees and costs, to the extent the claim arises from:

(a) your use of the data, or any decision made, action taken or not taken, or statement made in reliance on it, by you or by anyone acting for you;
(b) anything a connected app, a user of your account, or a person you shared a report with does with the data;
(c) your use of Permity for a use this page prohibits, or your breach of these terms, including the licence in section 6 and the rules in section 7;
(d) your use of the service or the data in breach of a law governing how property or personal information may be used, including the Fair Credit Reporting Act and its state equivalents, and any notice, certification or procedure such a law required of you;
(e) your alteration of a report, your removal of its limitations, or a statement you made about what a report establishes that the report does not establish;
(f) use of an API key or a connected app on your account by a person you gave it to or allowed to keep it, except where the exposure was caused by us; or
(g) any outreach you or anyone acting for you makes to a person using a name from the service, including any claim under a law about marketing, calls, texts, email, door-to-door sales, roofing or insurance claims.

It does not apply to the extent a claim is caused by our fraud, our wilful misconduct, or anything the law does not permit us to exclude. Where the law requires fault to be shared, it is shared. Nothing in this section makes you liable for our breach of the specific promises this page makes about prices, refunds and the return of charges we got wrong.

We will tell you promptly about a claim we want indemnified, give you control of its defence with counsel we reasonably approve, and cooperate at your expense. You will not settle anything that admits fault on our part, imposes an obligation on us, or does not fully release us, without our written agreement. Reasonable defence costs count towards what you owe under this section rather than sitting on top of it.

18. Suspension, closing an account, and what happens to the data

We may suspend or close an account, revoke a key, or disconnect a connected app for non-payment, for a use this page prohibits, for a risk to the service or to a jurisdiction’s own systems, or where a law requires it. Except where waiting would make things worse, we tell you first, say why, and where the cause can be fixed we give you a chance to fix it. You can close your account at any time. Where a prohibited use cost us something, including a fee, a penalty or a loss of supply, you will pay what it cost.

Suspension or closure for cause does not return prepaid fees. If we close an account for our own convenience rather than for cause, we return the unused part of a prepaid period. Either way, reports you have already generated stay retrievable for their 90 days, and you keep access to read and download them.

When the licence ends, so does your right to the data. When your account closes, when your subscription lapses, or when our own right to supply a part of the data ends, the licence in section 6 ends with it. Reports stay retrievable for their 90 days as this page promises, and nothing here reaches a report that a person is keeping for the matter it was sent for. Beyond that, on our request you will stop using the affected data, delete every copy you hold of it, including in your own systems, databases, backups, workflows and models, and confirm in writing that you have done so. We will ask only where our right to supply has ended or your account has, and we will say which data the request covers.

What survives the end of your account: everything on this page about what the data is and is not, about what a report establishes, about names and outreach, about the licence and what you may not do with the data, and about reports you have shared; the warranty disclaimer; the limit of our liability; your indemnity; the deletion duty above; any fees you owe; and the governing law and venue below.

19. Accepting these terms, and changing them

A person accepts, for the account. You accept these terms when you create an account with an email address, when you buy a report, a subscription or a pack of credits, and when someone with authority to bind your account accepts a new version on the website. An account made by signing in with Google, Apple or Microsoft accepts them on the website before its first lookup. Every acceptance is recorded against the version you were shown, and that version is the date printed at the top of this page. An API key, and every connected app that uses one, including the iOS app and the Zapier app, acts under the acceptance recorded for the account, and an account that has never accepted cannot spend a lookup through a key until someone accepts on the website. A request from a key is not acceptance: a scheduled job is not a person who read a version and had authority to bind a company.

A new version. When we change these terms in substance we publish a new version, keep every earlier version reproducible, and give notice by email to the account contact and on the website. A new version applies to a new purchase immediately. Everyone else accepts it at their next visit to the website, before their next lookup there. Keys and connected apps on an account that accepted an earlier version keep working, and every response to them carries a Permity-Terms-Update header naming the current version, the version your account last accepted, where to accept, and the date the notice gives, if it gives one. Where the notice gives a date, which is never sooner than thirty days after we send it, your keys and connected apps pause from that date, with an error that says the updated terms need accepting on the website, until someone with authority on your account accepts there. Nothing is charged while a key is paused, and the reports you already have stay retrievable. Accepting ends the notices and the pause.

Prices, and what you already paid for. A change to a price, to what a plan includes, or to anything you have already paid for takes effect no sooner than thirty days after we give notice, and never within a period you have prepaid unless the change is in your favour.

If you have paid for a period in advance, a month or a year, and have not accepted a new version, the version your account accepted governs the rest of that period. Renewing after it requires accepting the current version. A new version never takes away value you have already paid for.

You agree to receive notices from us by email and in the service.

20. Governing law, and where a dispute goes

These terms are governed by the law of the State of Idaho, without regard to its conflict-of-law rules.

Any dispute arising out of or relating to these terms or the service will be decided by the state courts in Bonner County, Idaho, or the United States District Court for the District of Idaho, and you and we consent to the jurisdiction of those courts. Nothing in this section takes away a right you have under a consumer-protection law that cannot be given up by agreement, or the remedies that law provides, and nothing in it restricts you from enforcing your rights in the courts of the state where you are located where that state’s law says such a restriction is void.

If you have signed a separate written agreement with us, that agreement controls wherever it differs from this page. Otherwise these terms and our privacy page are the whole agreement between us about the service. If any part of these terms is unenforceable, it is limited to the minimum extent necessary and the rest stands. A right we do not enforce straight away is not a right we have given up. You may not transfer your account or this licence without our agreement; we may transfer these terms to a successor to the business.

21. Contact

nate@valyaai.us for a question about these terms, a wrong match, a charge, or notice of anything this page says to tell us about. admin@valyaai.us for support with the API, a connected app or the Zapier app. For a name you want removed, the form on our privacy page, or nate@valyaai.us.

Legal notices to us go by email to nate@valyaai.us. Notices to you go to the account contact address we hold, and for a purchase without an account, to the address you bought it with.