Skip to main content
Tiny Solutions
  • Demo
  • Pricing
  • What's new
  • Contact
Log inCreate agency
Create agency

Product

  • Intake
  • Services
  • Tiny Agent
  • Billing
  • Pricing
  • Security

Features

  • Referral forms
  • Authorizations
  • Session notes
  • EI Hub claim files
  • Integrations
  • Changelog

Company

  • About
  • Careers
  • What's new
  • Contact

Resources

  • Switch from ProviderSoft
  • Start an agency
  • Early Intervention guide
  • Help center
  • Developers
  • Roles

Connect

  • Explore the demo
  • Contact us
  • Help center
PrivacySecurity

© 2026 Tiny Solutions, Inc. · Each agency sees only its own records · Audit history is never rewritten · Email carries no PHI

Security

Every record stays inside its agency

Tiny Solutions checks the agency and the role before it reads or changes a child record. Files open only after sign-in. The audit history is only added to, never rewritten. Account email carries no health information.

Start a security reviewRead the privacy notice

Keeping records separate

The agency is checked before the record. On every request, the server checks who is signed in, which agency they are working in, and their role. Hiding a button is never the only protection.

  • Agencies kept apart

    The server confirms the current agency before it reads or changes a child record or a document.

  • Access by role

    The server checks each person's role (Owner, Admin, Service coordinator, or Provider) against each action and each record.

  • Audit history

    Each entry records who acted, when, and which record changed. Earlier entries are never rewritten.

  • Protected files

    Files on a child record open only for signed-in people in that agency. There are no public links to documents.

Accounts and sign-in

Security that people can understand and use. A secure account still needs a clear way back in.

  • Passkeys

    Log in with a passkey, a password, an email code, or a sign-in provider your agency sets up.

  • Two-step verification

    A second step at sign-in, and another check before higher-risk actions.

  • Single-use links

    Account links work once and then expire.

  • Signed-in devices

    People see the devices they are signed in on, and can sign out of one device or all others.

  • Invitations

    Admins can cancel or resend an invitation that has not been accepted.

  • History stays after removal

    When you remove a person from the agency, the history of who did what stays.

Protected information

Each outside service gets only what its job needs. A service that does not need child or family information does not receive it.

  • Account email

    Email carries sign-in and account details only. It never contains a child's name, a fact about the case, or a Medicaid ID.

  • Stripe

    Stripe receives only what it needs to bill the agency. It never receives child records or EI Hub claims.

  • Address search

    Google receives only the street address a person types into the address search.

Shared responsibility

Your agency's policies still matter

Software alone does not meet HIPAA and FERPA duties. They also depend on agreements, devices, staff training, access reviews, and the choices an agency makes after setup.

What Tiny Solutions controls

Product design, permission checks on the server, audit history, account security, what outside services receive, and recovery.

  • Each agency sees only its own records
  • Access checked by role and caseload
  • Audit history that is never rewritten
  • No PHI in account email
  • Protected file access

What your agency controls

Who gets access, which devices are approved, how staff handle records outside the product, and when access is reviewed.

  • Role assignment and access review
  • Managed devices and screen privacy
  • Staff training and what to do after an incident
  • Records in exports and in other systems
Ask for the current evidence
Security documents change while the product is in development. Before you enter real health information, ask for the current agreements and the evidence for each control.

Send us your security questionnaire

Our answer says what the product does, what our hosting providers do, and what still depends on your agency's policy.

Start a security reviewRead the privacy notice

Leave child and family information out of the questionnaire.