Privacy Policy
Last Updated: November 9, 2026
STREAM ABA LLC ("Stream ABA," "we," "us," or "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our platform at Stream ABA.com (the "Service").
Please read this Privacy Policy carefully. By accessing or using the Service, you acknowledge that you have read, understood, and agree to be bound by this Privacy Policy.
1. Information We Collect
1.1 Information You Provide
We collect information you provide directly to us, including:
- Account Information: Name, email address, phone number, professional credentials (e.g., BCBA, RBT certification), and organization details when you create an account.
- Billing Information: Payment card details, billing address, and transaction history processed through our secure payment providers.
- Client Information: Information about your clients that you enter into the Service, which may include Protected Health Information (PHI) as defined by HIPAA.
- Communications: Information you provide when you contact us for support, submit feedback, or communicate with us.
1.2 Information Collected Automatically
When you access or use the Service, we automatically collect:
- Usage Data: Pages viewed, features used, time spent on the Service, and other usage statistics.
- Device Information: Device type, operating system, browser type, IP address, and device identifiers.
- Log Data: Server logs including access times, pages viewed, and referring URLs.
- Cookies and Similar Technologies: We use cookies, pixels, and similar technologies to collect information about your browsing activities. See Section 1.3 below for details.
1.3 Cookies, Analytics, and Advertising Technologies
We use cookies and similar tracking technologies on our marketing website to analyze traffic, improve our services, and deliver targeted advertising. Note: These tracking technologies are used only on our public marketing pages, not within the authenticated application where Protected Health Information is stored.
Types of Cookies We Use
- Essential Cookies: Required for the website to function properly (e.g., session management, security).
- Functional Cookies: Remember your preferences and settings to enhance your experience.
- Analytics Cookies: Help us understand how visitors interact with our website by collecting anonymous usage data.
- Advertising Cookies: Used to deliver relevant advertisements and track the effectiveness of our marketing campaigns.
Analytics Providers
We use the following analytics services:
- Google Analytics 4: Collects data about website traffic, user behavior, demographics, and interests. Google may use this data to contextualize and personalize ads on its advertising network.
- Google Tag Manager: Manages and deploys marketing tags and tracking scripts on our website.
Advertising and Retargeting
We work with advertising partners to show you relevant ads on other websites and platforms. These partners may collect information about your visits to our website and use it to deliver targeted advertisements. This is sometimes called "retargeting" or "remarketing."
Our advertising partners include:
- Google Ads: Displays ads across Google's advertising network and tracks conversions from our marketing campaigns.
- Meta (Facebook/Instagram): Uses the Meta Pixel to track conversions and enable retargeting on Facebook and Instagram.
- LinkedIn: Uses the LinkedIn Insight Tag to track conversions and enable retargeting for professional audiences.
- Reddit: Uses the Reddit Pixel to track conversions and deliver ads on the Reddit platform.
These advertising technologies may collect information such as:
- Pages you visit on our website
- Actions you take (e.g., signing up, requesting a demo)
- Your IP address and device information
- Information from cookies placed by these services
1.4 Information We Receive from Meta (Facebook and Instagram)
A practice that uses Stream ABA can connect its own Facebook Page and linked Instagram professional account through Facebook Login for Business. When it does, we receive the following from Meta on the practice's behalf:
- Lead Ads submissions: the answers a person gives on the practice's Facebook or Instagram lead form, such as name, phone number, email address, and the form's own questions.
- Messages: Facebook Messenger and Instagram Direct messages sent to the practice, the replies its staff send, any attachments, and the sender's name and Meta-provided ID.
- Account details: the IDs and names of the connected Page and Instagram account, and the access tokens needed to receive and reply to messages.
We use this information only so the connecting practice can reply to and follow up with the person who contacted it. We do not sell it, we do not use it for advertising, and we do not use it to train artificial intelligence models. We do not share it with third parties except the service providers that host our platform.
If a person unsends an Instagram or Messenger message, we erase its text and attachments from the practice's inbox. Practice staff can also delete a message from their inbox.
To have us delete the information we received about you from Meta, email us at support@streamaba.com, or ask the practice you contacted to delete your messages. If you connected Stream ABA to your own Facebook account, removing Stream ABA in your Facebook settings (Business Integrations, or Apps and Websites) also sends us a deletion request automatically.
Meta does not sign a Business Associate Agreement. Please do not send diagnoses, treatment details, insurance member IDs, or other health information over Facebook or Instagram.
1.5 Information We Receive from Google
A practice that uses Stream ABA can connect Google products in two ways. It can connect its Google Ads account by signing in with Google. If it uses Google Workspace, its Workspace administrator can also connect Gmail and Google Drive by authorizing Stream ABA in the Google Admin console (domain-wide delegation). Staff members can each connect their own Google Calendar by signing in with Google or, if the practice installed Stream ABA from the Google Workspace Marketplace, through that install. Each product is authorized and can be removed separately.
Google Ads
A practice that uses Stream ABA can connect its own Google Ads account by signing in with Google and granting Stream ABA access to Google Ads. When it does, we access the following Google user data through the Google Ads API on the practice's behalf:
- Account list: the IDs and names of the Google Ads accounts the signed-in Google user can access.
- Performance reports: daily cost, impressions, clicks and conversions for the practice's campaigns, ad groups and ads, with their IDs and names.
- Click details: the campaign and ad behind a Google click ID, so an inquiry can be matched to the campaign that sent it.
- Authorization tokens: the OAuth access and refresh tokens Google issues for the connection.
How we use it. We use this data only to show the connecting practice what its Google campaigns cost beside the inquiries, intakes and clients they brought in (the Lead Acquisition report). Stream ABA only reads reporting data. It never creates, changes, pauses or deletes anything in the practice's Google Ads account.
Sharing. We do not sell Google user data, use it for advertising, or share it with third parties, except the service providers that host our platform, or when required by law. The data is visible only to the connecting practice's own authorized staff.
Protection. Google user data is encrypted in transit (TLS) and at rest. Access and refresh tokens are additionally encrypted at the application level, and access is limited by role-based permissions.
Retention and deletion. We keep the synced campaign names and daily spend while the practice's account is active, so its historical reports stay accurate. When a practice disconnects Google Ads in Stream ABA, we revoke our access with Google and delete the stored tokens immediately. You can also remove Stream ABA's access at any time from your Google Account (Security, Third-party apps and services). To have the synced Google Ads data deleted, email us at support@streamaba.com, and we will delete it within 30 days. All of it is deleted when the practice's account is closed, as described in Section 6.
Google Workspace: Gmail and the Workspace Directory
To connect Gmail, the practice first proves it owns its Workspace domain by adding a DNS record. Its Workspace
administrator then authorizes Stream ABA's Gmail client in the Google Admin console with three scopes: read Gmail
(gmail.readonly), send Gmail (gmail.send), and read the Workspace user directory
(admin.directory.user.readonly). Stream ABA only acts for addresses in the verified domain, and only
for the mailboxes the practice approves. We access the following Google user data:
- Directory users: each Workspace user's Google user ID, name, primary email address, email aliases, and whether the account is suspended, read as the administrator account the practice records. We use this list only so the practice can choose which mailboxes to connect, and we keep these details only for the mailboxes it approves.
- Email headers: for each approved mailbox, Google tells us when a message arrives in the Inbox or is sent. We read that message's headers (sender, recipients, subject, date and message IDs) and its labels to check whether it involves a lead or client the practice has in Stream ABA. If it does not, we discard it without storing anything.
- Email content: if the message involves one of the practice's leads or clients, we read the full message, including its body and attachments, and store it on that lead's or client's record. If the practice asks, we also bring in earlier messages from a date range it chooses, using the same rule.
- Sending: when practice staff send an email to a lead or client from Stream ABA, including follow-up emails the practice sets up, we send it from that staff member's own Gmail address, so it appears in their Sent folder.
Stream ABA never changes, labels, moves or deletes messages in Gmail.
Google Workspace: Google Drive
To connect Google Drive (Linked Documents), the practice proves it owns its Workspace domain and its administrator
authorizes Stream ABA's Drive client in the Google Admin console. The administrator chooses read-only access
(drive.readonly), or read-and-write access (drive) if the practice wants to create
folders from Stream ABA. Stream ABA acts as the one Workspace account the practice names, and we access the
following Google user data:
- File and folder details: for the Shared Drives and folders the practice links, each item's ID, name, folder path, file type, size, version, checksum, created and modified times, web link, and what the connected account may do with it, plus the owner's email address for each linked folder. We keep this list in sync so staff can browse the folders inside Stream ABA.
- File content: when staff open a file in Stream ABA, we fetch it from Google Drive to show it and do not keep a copy. When staff import a file into a client's record, we save a copy of it there as a client document.
- Folders we create: with read-and-write access, Stream ABA creates a folder when staff ask it to. It never edits, moves or deletes files in Google Drive.
Google Calendar
A staff member can connect their own Google Calendar by signing in with Google and granting two scopes: manage events (calendar.events) and manage the calendars Stream ABA
creates (calendar.app.created). If the practice installed Stream ABA from the Google Workspace
Marketplace, a staff member whose address is in the practice's Workspace domain connects through that install
instead of signing in. The install grants the same two scopes and a third: see when the person is busy
(calendar.freebusy). We receive and use the following:
- Account details: the Google account's ID, name, email address and profile picture, so the person can see which account is connected.
- Authorization tokens: the OAuth access and refresh tokens Google issues when the person signs in. A calendar connected through the Marketplace install stores no refresh tokens. It uses short-lived delegated access tokens, which may be cached for up to 55 minutes for calendar event synchronization; busy-time queries obtain an uncached token.
- Calendars we create: for each calendar subscription the person turns on, Stream ABA creates a separate calendar in their Google account, named after the subscription, and writes its items there: appointments, tasks and deadlines, each with its title, date or time, a short description and a link back to Stream ABA. Titles can include client names. We store only the IDs Google gives the calendar and its events, so we can update them.
- Call events: when a call with a staff member is booked in Stream ABA, by staff or by a family through a booking link, Stream ABA adds it to a separate calendar named "Stream ABA calls" that it creates in the staff member's Google account. The event has the call's time, a title with the name of the person the call is with, the call's topic, and the phone number to dial or the video link. For a Google Meet call, Google adds the Meet link. Stream ABA moves or deletes the event when the call is rescheduled or cancelled. We store the IDs Google gives the calendar and the event.
- Busy times: through the Marketplace install, when Stream ABA shows the open times for a call with a staff member, it asks Google which times are busy on that person's primary calendar. Google returns only start and end times. Stream ABA never receives event titles, descriptions, attendees or locations. We keep the busy times for up to five minutes so we don't ask Google again each time the open times are shown, and we don't save them to any record. A calendar connected by signing in with Google does not grant this scope, so Stream ABA reads no busy times from it.
Apart from busy times, Stream ABA never reads, changes or deletes events in any calendar it did not create. When the person deletes a subscription, Stream ABA deletes the calendar it created for it. (Family Portal calendar links are a feed the family adds to their own calendar app; they do not connect a Google account.)
How We Use, Share, and Protect Google Workspace Data
How we use it. We use Gmail, Google Drive, Google Calendar and directory data only to provide these features: showing practice staff the emails they exchange with leads and clients on the right record, sending their emails, letting them browse and import documents, keeping the calendars Stream ABA creates up to date, and finding open times for calls with staff. Stored emails and documents are visible only to the practice's own authorized staff, according to their role permissions.
Artificial intelligence. If a practice turns on Stream ABA's AI features, a staff member who has permission can ask for suggested replies on a lead or client. To write them, recent messages with that person, which can include emails received through Gmail, are sent to an AI model that runs in Stream ABA's Amazon Web Services environment (Amazon Bedrock). The suggestions are shown only to that staff member. When a staff member processes an image attached to an email as an insurance card, that image is sent to the same AI model to read the card's details into the form for the staff member to review. We do not use Google user data to train, develop or improve AI or machine learning models.
Sharing. We do not sell Google user data, use it for advertising, or share it with third parties, except the service providers that host our platform, or when required by law. Stream ABA personnel do not read it unless the practice asks us to for support, it is needed for security, or the law requires it.
Protection. Google user data is encrypted in transit (TLS) and at rest, and stored attachments and documents are kept in private storage. We never store Google passwords. For Gmail and Google Drive we store no refresh tokens or service account keys: Google signs a short-lived access token for each use, and only Stream ABA's production servers can request one.
Retention and deletion. Stored emails, attachments and imported documents become part of the practice's records in Stream ABA and are kept while its account is active, then deleted as described in Section 6. To have Google Workspace data deleted sooner, the practice can delete it in Stream ABA or email us at support@streamaba.com, and we will delete it within 30 days.
Removing access. A practice can disconnect Gmail in its Stream ABA email settings, which stops email sync and drops our access tokens. It can likewise disconnect Google Drive in its Stream ABA Google Drive settings, which stops syncing every linked folder and drops our access tokens. A Workspace administrator can also end Stream ABA's access to Gmail or Google Drive at any time by removing its client from the Google Admin console (Security, Access and data control, API controls, Domain-wide delegation) or, if the practice installed Stream ABA from the Google Workspace Marketplace, by uninstalling the app in the Google Admin console (Apps, Google Workspace Marketplace apps), which ends its access to Gmail, Google Drive and Google Calendar together. Removing a linked folder in Stream ABA stops syncing that folder. A staff member can disconnect Google Calendar in Stream ABA, which deletes the stored tokens and stops updates; calendars already created stay in their Google account until they remove them. They can also remove Stream ABA's Google Calendar access from their Google Account (Security, Third-party apps and services). Data we already stored stays until it is deleted as described above.
Google API Services User Data Policy
Stream ABA's use and transfer of information received from Google APIs, including the Google Ads, Gmail, Google Drive, Google Calendar and Admin SDK Directory APIs, adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models, and we do not use or transfer it to serve advertising.
1.6 Information We Receive from Zoom
A practice that uses Zoom Phone can connect its Zoom account to Stream ABA. The practice's Zoom account owner or Zoom Phone administrator authorizes the "Stream ABA" app, and chooses which Zoom Phone lines Stream ABA syncs. Staff members who want to send texts from their own Zoom Phone number can each also authorize the separate "Stream ABA SMS" app with their own Zoom login. When a practice connects, we access the following Zoom user data through the Zoom API on the practice's behalf:
- Account and user details: the connecting Zoom user's ID, name and email address, the Zoom account ID, and the practice's Zoom Phone users with their names, email addresses and phone numbers, so the practice can choose which lines to sync.
- Calls: call logs for the selected lines: the numbers and names of both parties, direction, start and end time, duration and result.
- Voicemails and transcripts: voicemail recordings and Zoom's voicemail transcripts, and the transcripts of recorded calls.
- Text messages: SMS and MMS messages sent and received on the selected lines, with their participants and any attachments, and the texts staff send from Stream ABA through their own number.
- Faxes: fax logs and fax documents sent and received on Zoom Phone, and faxes staff send through Zoom Phone when the practice turns that on.
- Authorization tokens: the OAuth access and refresh tokens Zoom issues for each connection.
How we use it. We use Zoom data only to show the connecting practice its calls, voicemails, texts and faxes on the matching lead's or client's record, and to send the texts and faxes its staff choose to send. We match each one to a lead or client by phone number. We do not use Zoom data for advertising, and we do not use it to train artificial intelligence models.
Sharing. We do not sell Zoom data or share it with third parties, except the service providers that host our platform, or when required by law. It is visible only to the connecting practice's authorized staff who can see the related family.
Protection. Zoom data is encrypted in transit (TLS 1.2 or higher) and at rest. Access and refresh tokens are additionally encrypted at the application level, and access is limited by role-based permissions. Every notification Zoom sends us is verified with Zoom's signature before we use it.
Retention and deletion. Synced calls, voicemails, texts and faxes become part of the practice's records and are kept while its account is active. When a practice disconnects Zoom Phone in Stream ABA, we revoke our access with Zoom and delete the stored tokens immediately. A practice can also remove the "Stream ABA" app in the Zoom App Marketplace (Manage, then Added Apps); Zoom then notifies us, and we end the connection, delete the stored tokens, and remove every staff member's Zoom texting connection for that practice. A staff member can remove their own texting connection in Stream ABA (Preferences, then Texting) or by removing "Stream ABA SMS" from their Zoom Added Apps. To have synced Zoom data deleted, email us at support@streamaba.com, and we will delete it within 30 days. All of it is deleted when the practice's account is closed, as described in Section 6. Our Zoom Phone guide explains how to add, use and remove the integration.
1.7 Information We Receive from Microsoft (Outlook Calendar)
A staff member can connect their own Outlook calendar by signing in with their Microsoft account and granting
these permissions: sign in and read their basic profile (openid, profile,
email, User.Read), keep access while they are not signed in
(offline_access), and read and write their calendars (Calendars.ReadWrite). Microsoft's
permission to write calendars also allows reading them, so this section describes what Stream ABA actually does.
We receive and use the following:
- Account details: the Microsoft account's ID, name and email address, so the person can see which account is connected.
- Authorization tokens: the OAuth access and refresh tokens Microsoft issues for the connection.
- Calendars we create: for each calendar subscription the person turns on, Stream ABA creates a separate calendar in their Outlook account, named after the subscription, and writes its items there: appointments, tasks and deadlines, each with its title, date or time, a short description and a link back to Stream ABA. Titles can include client names. We store only the IDs Microsoft gives the calendar and its events, so we can update them.
- Call events: when a call with a staff member is booked in Stream ABA, by staff or by a family through a booking link, Stream ABA adds it to a separate calendar named "Stream ABA calls" that it creates in the staff member's Outlook account. The event has the call's time, a title with the name of the person the call is with, the call's topic, and the phone number to dial or the video link. For a Microsoft Teams call, Stream ABA asks Microsoft to make the event a Teams meeting, and Microsoft adds the Teams join link. Stream ABA moves or deletes the event when the call is rescheduled or cancelled. We store the IDs Microsoft gives the calendar and the event.
- Busy times: when Stream ABA shows the open times for a call with a staff member, it asks Microsoft for that person's free/busy schedule. If Microsoft cannot give a schedule for the account, Stream ABA lists the person's calendar events for those days and asks only for each event's start time, end time, free/busy status and whether it was cancelled. From either answer, Stream ABA keeps only the start and end of the times marked busy, tentative or away, and never stores event titles, descriptions, attendees or locations. We keep the busy times for up to five minutes so we don't ask Microsoft again each time the open times are shown, and we don't save them to any record.
Apart from busy times, Stream ABA never reads, changes or deletes events in any calendar it did not create. When the person deletes a subscription, Stream ABA deletes the calendar it created for it.
How we use it. We use Outlook calendar data only to keep the calendars Stream ABA creates up to date and to find open times for calls with staff. We do not use it for advertising, and we do not use it to train artificial intelligence models.
Sharing. We do not sell Microsoft data or share it with third parties, except the service providers that host our platform, or when required by law.
Protection. Microsoft data is encrypted in transit (TLS) and at rest, and access is limited by role-based permissions.
Removing access. A staff member can disconnect Outlook in Stream ABA, which deletes the stored tokens and stops updates; calendars already created stay in their Outlook account until they remove them. They can also remove Stream ABA from the apps that have access to their Microsoft account, and their organization's Microsoft administrator can remove it for everyone. To have Outlook data we stored deleted sooner, email us at support@streamaba.com, and we will delete it within 30 days. All of it is deleted when the practice's account is closed, as described in Section 6.
2. Protected Health Information (PHI)
Stream ABA is designed to help ABA therapy practices manage client information, which may include Protected Health Information (PHI) as defined under the Health Insurance Portability and Accountability Act (HIPAA).
2.1 Our Role
When you use our Service to store or process PHI, Stream ABA acts as a Business Associate under HIPAA. Our obligations regarding PHI are governed by:
- The HIPAA Privacy Rule and Security Rule
- The Business Associate Agreement (BAA) we enter into with you
- Our HIPAA Privacy Statement
2.2 Your Responsibilities
As a Covered Entity or Business Associate, you are responsible for:
- Ensuring you have proper authorization to enter client PHI into our Service
- Obtaining necessary patient consents and authorizations
- Complying with applicable privacy laws and regulations
- Entering into a Business Associate Agreement with us before entering PHI
3. How We Use Your Information
We use the information we collect to:
- Provide the Service: Operate, maintain, and improve our platform and features.
- Process Transactions: Handle billing, payments, and subscription management.
- Communicate: Send service-related notices, updates, security alerts, and support messages.
- Analyze and Improve: Understand how users interact with our Service to improve functionality and user experience.
- Comply with Law: Meet legal obligations and respond to lawful requests from authorities.
- Protect Rights: Detect, prevent, and address fraud, security issues, and technical problems.
4. How We Share Your Information
We do not sell your personal information. We may share your information in the following circumstances:
4.1 Service Providers
We share information with third-party vendors who perform services on our behalf, such as:
- Cloud hosting and infrastructure providers
- Payment processors
- Analytics providers
- Customer support tools
These providers are contractually obligated to protect your information and use it only for the services they provide to us.
4.2 Advertising Partners
We share certain information with advertising partners to deliver targeted advertisements and measure the effectiveness of our marketing campaigns. This includes:
- Website browsing data collected through cookies and pixels
- Conversion data (e.g., whether you signed up after clicking an ad)
- Hashed identifiers for audience matching
Our advertising partners include Google, Meta (Facebook/Instagram), LinkedIn, and Reddit. Each partner has its own privacy policy governing how they use this data.
Important: We do not share Protected Health Information (PHI) or data from the authenticated application with advertising partners. Advertising technologies operate only on our public marketing pages.
4.3 Legal Requirements
We may disclose information if required by law, regulation, legal process, or governmental request, or when we believe disclosure is necessary to protect our rights, your safety, or the safety of others.
4.4 Business Transfers
If Stream ABA is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change.
5. Data Security
We implement robust security measures to protect your information, including:
- Encryption of data in transit (TLS/SSL) and at rest (AES-256)
- Regular security assessments and penetration testing
- Access controls and authentication requirements
- Employee training on data protection and HIPAA compliance
- Incident response and breach notification procedures
While we strive to protect your information, no method of transmission or storage is 100% secure. We cannot guarantee absolute security.
6. Data Retention
We retain your information for as long as your account is active or as needed to provide the Service. We also retain information as necessary to:
- Comply with legal obligations (including HIPAA record retention requirements)
- Resolve disputes
- Enforce our agreements
When you terminate your account, we will delete or anonymize your information within 90 days, except as required by law or as outlined in our data retention policies.
7. Your Rights and Choices
7.1 Account Information
You may access, update, or delete your account information at any time through your account settings or by contacting us.
7.2 Communications
You may opt out of promotional communications by following the unsubscribe instructions in those messages. You cannot opt out of service-related communications.
7.3 Cookies and Tracking
You have several options to control cookies and tracking technologies:
Browser Controls
Most browsers allow you to control cookies through their settings. You can typically find these in your browser's "Settings," "Preferences," or "Privacy" menu. Note that disabling cookies may affect the functionality of the Service.
Platform-Specific Opt-Outs
You can opt out of personalized advertising from our advertising partners:
- Google: adssettings.google.com
- Facebook/Meta: facebook.com/settings/?tab=ads
- LinkedIn: linkedin.com/psettings/advertising
Industry Opt-Out Tools
You can also use these industry-wide opt-out tools:
- Network Advertising Initiative: optout.networkadvertising.org
- Digital Advertising Alliance: optout.aboutads.info
- Your Online Choices (EU): youronlinechoices.eu
Please note that opting out does not prevent you from seeing ads; you will still see ads, but they may be less relevant to you.
8. California Privacy Rights (CCPA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):
8.1 Right to Know
You have the right to request information about the categories and specific pieces of personal information we have collected about you, the sources of that information, the business purposes for collecting it, and the categories of third parties with whom we share it.
8.2 Right to Delete
You have the right to request deletion of your personal information, subject to certain exceptions.
8.3 Right to Opt-Out of Sale/Sharing
Under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CPRA), you have the right to opt out of the "sale" or "sharing" of your personal information.
Do We Sell Personal Information? We do not sell personal information in the traditional sense. However, our use of advertising cookies and pixels to deliver targeted advertising may be considered "sharing" of personal information under California law.
How to Opt Out: You can opt out of targeted advertising by:
- Using the opt-out links provided in Section 7.3 above
- Enabling "Do Not Track" or similar signals in your browser
- Contacting us at support@streamaba.com with the subject "Do Not Sell or Share My Personal Information"
8.4 Right to Non-Discrimination
We will not discriminate against you for exercising your CCPA rights.
8.5 Exercising Your Rights
To exercise your California privacy rights, contact us at support@streamaba.com. We will verify your identity before processing your request.
9. Children's Privacy
The Service is designed for use by healthcare professionals and is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe we have collected information from a child under 13, please contact us immediately.
Note: While client records may contain information about minors receiving ABA therapy, this information is entered and managed by authorized healthcare professionals, not by the minors themselves.
10. International Users
Stream ABA is based in the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States, which may have different data protection laws than your country.
11. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by posting the new Privacy Policy on this page and updating the "Last Updated" date. Your continued use of the Service after changes are posted constitutes acceptance of the updated Privacy Policy.
12. Contact Us
If you have questions about this Privacy Policy or our privacy practices, please contact us:
For HIPAA-related inquiries, please reference our HIPAA Privacy Statement.