Trust Center

What we do with your data — and what we won’t claim.

ApprovedIn is a technology platform, not a law firm or an insurance agency. This page explains, in plain English, exactly what data we collect, how we protect it, who can see it, and the certifications we have and haven’t earned. If anything here is unclear, ask us — we’d rather answer a hard question than hide one.

What data we collect & why

We collect only what compliance requires — nothing more:

  • Certificates of Insurance — to verify each vendor carries the coverage your association requires.
  • Trade licenses — to confirm vendors are licensed to perform the work they’re approved for.
  • Corporate filings — to confirm the business entity is active and in good standing.
  • Hold Harmless agreements — the executed contract between a vendor and an association.
  • Contact details — name, email, phone, and service area so managers and residents can reach vendors.

We do not collect Social Security numbers, bank account numbers, or credit card data on our servers. Payment processing is handled by Stripe.

How your data is stored & encrypted

All data is stored on secure cloud infrastructure provided by our platform partner, Base44:

  • Encryption in transit — all connections use TLS (HTTPS).
  • Encryption at rest — the underlying database encrypts stored data.
  • Automated backups — your compliance records are backed up to prevent data loss.
  • Uploaded documents — certificates and licenses are stored as files tied to the vendor and association that uploaded them.

We’re transparent that compliance documents are currently stored in our platform’s standard storage. As we move sensitive documents toward private, access-controlled storage, this page will be updated to reflect it.

Who can see what (role-based access)

Access is strictly role-based. No user can see another user’s data without an explicit relationship:

  • Association managers see only the associations they manage and the vendors linked to those associations.
  • Vendors see only their own profile, documents, and the associations that have approved them.
  • Residents see only vendors approved by their association (and, where opted in, the network-wide resident directory).
  • Platform admins can assist with accounts, but every admin action is recorded in an audit log.

A vendor’s compliance documents are never shared across associations — each association sees its own relationship to that vendor.

Audit trails on every action

Every meaningful action is logged with a timestamp and the user who took it:

  • Document uploads and AI parses
  • Vendor approvals, correction requests, and rejections
  • Compliance requirement changes
  • Manager assignments and role changes
  • Admin account views and field edits

When a board asks “who approved this vendor and when,” the answer is one click away — not a reconstruction from memory.

Sub-processors we rely on

We use a small set of trusted third parties to run the platform. Each handles a specific, limited function:

  • Base44 — the platform that hosts our database, file storage, authentication, and backend logic.
  • Resend — transactional email delivery (invitations, alerts, reminders).
  • Twilio — SMS delivery for vendor invitations.
  • Stripe — payment processing for paid plans. Card data never touches our servers.

We do not sell your data to anyone, and we do not share it for advertising.

Data retention

We retain compliance records for as long as your account is active, because the whole point is to maintain a continuous compliance history. Specifically:

  • Active accounts — records are kept until you delete them or close your account.
  • Account deletion — you can request deletion from your Data & Privacy settings; it is permanent and irreversible.
  • Audit logs — retained to preserve a defensible compliance history, as is standard for fiduciary record-keeping.

For the full terms, see our Privacy Policy.

Certifications: what we have, and what we don’t

SOC 2 is committed on our roadmap — not claimed yet. We will not display a certification badge on this page until an independent auditor has actually issued one. Claiming a certification we haven’t earned would be exactly the kind of behavior a compliance product should never model. This is our honest posture today; check back as we grow.

Why our legal pages look unfinished (and why that’s deliberate)

Our Terms of Service and Privacy Policy are intentionally kept empty of substantive legal language until they are reviewed by a qualified attorney. We could paste a generic template today — many products do — but a compliance platform publishing boilerplate it hasn’t vetted would undermine the very trust we’re asking you to place in us. We’d rather show you an honest placeholder than a fabricated promise.

ApprovedIn is a technology platform, not legal or insurance advice

ApprovedIn helps you organize and track vendor compliance documents, but it does not provide legal advice, insurance advice, or a guarantee of coverage. The compliance requirements configured for each association are set by that association’s manager (and, where confirmed, by a licensed insurance agent) — not by ApprovedIn. A vendor being marked “compliant” in ApprovedIn means their documents meet the requirements your association configured; it is not a substitute for your own due diligence or the advice of a qualified attorney or insurance professional.