Skip to content
RevAddress

Terms of Service

Revision date:
October 1, 2026
Version:
2026-10-01
Revised service terms operative:
on recorded express acceptance
Provider:
Revasser LLC, New York, NY

These terms govern your RevAddress account, API access, connected workflows and payment. Accepting the current service terms does not accept an individual offer to settle earlier usage.

1. Agreement and acceptance

This revision is dated October 1, 2026 and is identified as version 2026-10-01. It governs new service access when you expressly accept it at signup, paid activation, or another recorded acceptance step. Existing agreements and representations remain relevant to activity before that acceptance; this publication does not establish that this wording was previously published or accepted.

Prior use may be addressed in a separate written settlement offer identifying its period, amount and scope. It binds the parties only upon the offer’s specified acceptance. An invitation to review activity or pay a proposed settlement is not itself acceptance or an admission of liability.

If a separately signed agreement conflicts with these terms, that agreement controls within its stated scope. The written settlement controls only the identified account, usage period, amount, and matters expressly resolved; it does not create future service entitlement unless it expressly says so.

2. The service and its data sources

Revasser LLC operates RevAddress at revaddress.com and api.revaddress.com, including REST APIs, remote MCP access, and related client software. We provide standardization, geographic and Census data, and authorized provider integrations. We are an independent software company, not USPS.

Census standardization and geocoding do not establish USPS delivery-point verification, ZIP+4 deliverability, or the existence of a unit. ACS statistics describe published historical estimates and their stated limitations; they are not forecasts or individual household facts. Read the response source and verification status before relying on a result.

USPS service availability, postal charges, mailing eligibility, delivery commitments, and account licensing are subject to USPS requirements. RevAddress access does not confer a USPS license or guarantee delivery. Shipping labels and payment authorization remain unavailable unless separately enabled and expressly authorized.

3. Accounts, authority, and API keys

Provide accurate contact and organization information and act with authority for the organization you represent. A project label is a display name, not evidence of ownership of another account. Do not create or use accounts to evade limits, obtain another customer’s entitlement, or conceal automated traffic.

Keep keys and connected credentials confidential, outside public repositories and browser code. You are responsible for your authorized users and integrations. Notify support@revaddress.com promptly about compromise, incorrect ownership, or unexplained usage so we can investigate and revoke credentials.

Account migration, key rotation, or organization changes require verified ownership. We may restrict an account while ownership or authorization is unresolved. We do not assign shared historical activity to a person solely from a repeated label or public profile.

4. Acceptable use

Use the service for lawful, authorized operational purposes. Observe request and batch limits, implement backoff after rate limits, and prevent uncontrolled retries. Do not attack, circumvent funding or access controls, harvest provider data in violation of applicable rights, or submit prohibited or fraudulent transactions.

You may integrate RevAddress into your own authorized workflows and applications. Reselling access as a competing standalone RevAddress or USPS API product requires our separate written permission. You remain responsible for permissions, privacy notices, and provider requirements applicable to data you submit.

We may immediately stop provider calls, restrict keys, or suspend workflows to prevent unfunded spending, misuse, security incidents, or unauthorized postal operations. We will provide an explanation and contact route when practical. A restriction does not itself determine the outcome of a disputed historical charge.

5. Subscriptions, request allowances, and prepaid funding

Prices are in USD unless checkout states otherwise. The pricing page and final Stripe checkout identify the subscription, interval, prepaid block, and amount before you pay. Starter is $29 per month; activation with an initial $50 purchased credit block is $79 initially, followed by the $29 monthly subscription. Other plan and annual prices appear at checkout.

A paid subscription grants the stated software features and request allowance while its paid-through entitlement is valid. It does not include unlimited or unfunded provider calls. Platform USPS delivery-point verification requires a valid paid entitlement and an additional reservation of 10 purchased credits ($0.01) for each address sent for verification, including each batch or job row. Subscription allowances cannot substitute for this reservation. A separately purchased verification service may instead reserve from its confirmed prepaid row budget, as disclosed in that service order.

Free access is limited to eligible Census and local reference data operations within published limits. It does not fund USPS, paid AI inference, or another paid upstream provider. Signup, beta, bonus, and promotional credits have no cash or refund value and cannot fund a paid upstream call. Their permitted uses and expiry are shown in the balance and credit catalog.

For eligible software operations, request allowances apply before separately purchased overflow credits. Provider funding and software metering are distinct. A handled input error is not a successful verification; dashboards, authentication, rejected or rate-limited requests, and our server errors must be distinguished in any usage statement. Published endpoint weights, source status, and funding errors identify what an operation requires.

Credits require a deliberate one-time purchase. Purchased credits expire after 365 days and promotional credits on their stated schedule. We do not automatically reload balances or extend postpaid overage. If entitlement, purchased funding, or a provider budget cannot be confirmed, the funded operation stops before a new provider request.

Subscriptions renew on the selected billing interval unless canceled. Cancel through available billing tools or support; paid access continues to its paid-through date, subject to security and acceptable-use restrictions. A failed, reversed, refunded, disputed, or expired payment may restrict the corresponding entitlement. Upgrades, downgrades, or proration take effect only as confirmed in the billing flow.

Contact support promptly about an incorrect charge, service failure, or refund request. We review the payment, delivered service, remaining balance, and applicable rights. Nothing here excludes non-waivable legal rights or changes the refund policy of Apple or another purchasing platform.

6. Separate one-time settlements

A proposed prior-use settlement is separate from a subscription or credit purchase. Its individual written offer must identify the account and attribution basis, dates, measured usage, proposed amount, any exclusions, and the precise matters resolved. Proposed settlement pricing is not represented as our provider’s invoice or as an already collected payment.

Acceptance must follow the procedure in that offer. Payment of an identified settlement checkout resolves only the offer’s stated scope upon confirmed payment and acceptance. Unless expressly agreed otherwise, it does not release unrelated matters, create a recurring subscription, grant future API access, or add prepaid credits.

If you dispute ownership, quantity, applicable offer, or amount, contact generalcounsel@revasser.nyc with the settlement reference. We will review relevant records and prior correspondence. Do not send API keys or full address datasets by email.

7. Your own provider credentials

Where supported and enabled for a funded account, you may connect your own USPS app credentials. You retain responsibility for that account, licensing, postal billing, and authorization. Connecting credentials does not bypass RevAddress entitlement, limits, or security controls.

We encrypt connected credentials at rest and use them for authorized requests. If your provider revokes credentials or declines access, the integration may fail. You must obtain replacement credentials from the provider; we cannot recover a credential you lost. Any platform-funded verification remains subject to the purchased-credit requirement.

8. Client applications and purchasing platforms

Client applications, including iOS and MCP clients, remain subject to server-side entitlement and provider funding checks. A free trial or client subscription does not by itself fund additional paid upstream requests. On-device recognition and Census standardization must not be described as USPS verification.

For an Apple purchase, the price, trial, renewal, cancellation, and refund terms displayed by Apple govern that purchase. Manage auto-renewing Apple subscriptions through Apple account settings. Stripe purchases are separate; an MCP tool cannot complete payment for you.

Follow the privacy policy for data processing and retention information. Keep backups of locally saved records you need; local deletion or app removal may remove those records.

9. Availability and reliance

Operational health is published at api.revaddress.com/health. Unless a separate written agreement provides otherwise, service is offered on a commercially reasonable basis without a guaranteed uptime or automatic service-credit schedule.

Provider outages, maintenance, funding stops, and infrastructure incidents can interrupt service. Build appropriate retry limits, source checks, and fallback handling. Do not rely on a standardization result as confirmation of delivery or a statistical estimate as an individual factual determination.

10. Intellectual property and submitted data

You retain your rights in submitted data, code, and applications. Revasser LLC retains its rights in RevAddress software, documentation, and website; permitted access does not transfer ownership. Open-source SDKs remain governed by their published licenses.

You grant the permissions needed to process authorized requests and maintain account, usage, security, billing, and dispute records under the privacy policy. Do not submit data you lack authority to process.

11. Disclaimers and liability

To the maximum extent permitted by applicable law, service is provided “as is” and “as available,” without a warranty of uninterrupted operation, accuracy, deliverability, or fitness for a particular purpose. We do not exclude warranties or rights that cannot lawfully be excluded.

To the extent permitted by law, Revasser LLC is not liable for indirect, incidental, special, consequential, or punitive damages arising from the service. Our aggregate liability for claims arising from the service is limited to the service fees you paid Revasser LLC during the 12 months preceding the event giving rise to the claim. These limitations do not apply to fraud, willful misconduct, gross negligence, or liabilities that applicable law does not permit us to exclude or limit. They do not limit payment obligations expressly agreed in a separate settlement or your non-waivable rights.

12. Suspension, termination, and changes

You may stop using the service and cancel renewal at any time. On termination, access and connected credentials may be disabled; relevant billing, acceptance, security, and dispute records may be retained under the privacy policy and applicable requirements. Cancellation does not expand the scope of a settlement or erase an unresolved dispute.

Material future changes will identify their publication and operative dates. We will communicate material contractual changes at least 14 days before they take effect where practical and required; a new paid activation may require express acceptance of the current version. Immediate operational funding or security restrictions do not assert that revised contract wording was previously accepted.

13. Governing law and contact

New York law governs, excluding conflict-of-law rules and subject to mandatory applicable protections. Disputes are to be brought in courts with jurisdiction in New York County, New York, except where applicable law requires otherwise.

Revasser LLC, New York, NY. Service and billing questions: support@revaddress.com. Terms and individual settlement review: generalcounsel@revasser.nyc.

14. Authority and responsibility for submitted data

You represent that you have authority to bind the account holder, grant the permissions required to process submitted data, and authorize connected integrations. Your users must comply with these terms. Do not submit third-party credentials, address data or personal information without the necessary authority.

You grant Revasser LLC a limited, non-exclusive license to process, transmit and reproduce submitted data solely to provide the requested service, secure the account, maintain usage and payment records, and resolve disputes, consistent with the privacy policy. This permission does not transfer your ownership or authorize unrelated sale of submitted address datasets.

Except to the extent caused by our breach, unlawful conduct or negligence, you will defend and indemnify Revasser LLC against third-party claims arising from your unlawful use, submitted data infringing third-party rights, or lack of authority to provide data or connect an account. We must promptly notify you of a claim, allow you to control the defense with competent counsel, and reasonably cooperate at your expense. You may not settle a claim imposing liability, an admission, or continuing obligations on us without our written consent. This clause applies only to the extent permitted by law and does not indemnify us for our own misconduct.

15. Notices and dispute review

Maintain a working account email. Service and billing notices may be sent there; contractual and settlement notices should identify the account or offer reference and be sent to generalcounsel@revasser.nyc. No email notice alters a signed agreement without the acceptance that agreement requires. Where law requires another method, that method governs.

Before bringing an ordinary service dispute, provide a written description and a reasonable opportunity for a good-faith response. This request does not shorten a statutory deadline, prevent urgent injunctive relief, require arbitration, or waive access to a court or regulator. We will distinguish attributed requests, provider-billable events, estimated costs, proposed settlement amounts and collected payments when reviewing a usage dispute.

16. General provisions

These terms, the accepted order or checkout disclosures, and any separately signed service agreement constitute the agreement for the service they identify. A signed agreement takes priority within its scope, followed by an accepted order’s specific commercial terms, then these terms. A separately accepted settlement controls only its stated prior-use matter. Provider and purchasing-platform terms apply to their services. The privacy policy governs processing disclosures and does not expand a payment obligation.

Any invalid provision will be limited or severed only to the extent necessary; the remainder continues where lawful. Failure to enforce a provision does not waive it. A waiver must be express and applies only to the identified instance. Neither party may assign the agreement to evade obligations; assignment with an acquisition or reorganization is permitted if the successor assumes the obligations and required notice is given. Other assignments require the other party’s written consent, not to be unreasonably withheld.

The parties are independent contractors; these terms create no agency, partnership, employment or intended third-party beneficiary. Performance delays outside reasonable control excuse only the affected obligation for their duration, require reasonable mitigation and notice, and do not excuse amounts already expressly owed. Neither party is required to perform an unlawful act.

Payment and settlement obligations expressly accepted, ownership, necessary data-processing permissions for retained records, limitations and their exceptions, indemnity for covered claims, dispute and general provisions survive termination to the extent their purpose requires. Survival does not authorize indefinite data retention or create a new historical charge.

Revision date: October 1, 2026 Privacy policy Pricing