Privacy policy
Forebeam privacy policy
Who we are
FOREBEAM LLC ("Forebeam," "we," "us," or "our") is a Florida limited liability company that operates the Forebeam service. Its Florida document number is L26000479613, and its registration is active. For information Forebeam handles for its own business purposes—such as website inquiries, account security, and direct support communications—FOREBEAM LLC is responsible for the processing described in this notice. For information a school, district, charter network, or other education organization submits or connects for its own purposes, that customer determines why and how the information is used, and FOREBEAM LLC processes it to provide the service under the applicable agreement.
Overview and scope
Forebeam helps schools, districts, charter networks, and other education organizations evaluate software investments, contracts, renewals, implementation, and utilization. This notice explains how Forebeam handles information through its public website, customer workspaces, educator surveys, administrative-document workflows, and customer-authorized integrations.
Forebeam also handles account, security, support, and business-contact information needed to operate and protect the service.
Categories of information
Depending on the features a customer chooses, Forebeam may process:
- Business-contact and inquiry information: name, work email, organization, organization type, role or title, and information a person chooses to provide in a walkthrough, support, security, or privacy request.
- Account and authentication information: employee name, work email, password hash or external authentication identifier, organization membership, role, school or site access, sign-in events, and multi-factor authentication status.
- Organization and software-portfolio information: organization and school names, responsible people, vendors, products, funding sources, costs, licenses, contracts, quotes, invoices, renewal terms, documents, and review history.
- Employee directory and survey information: approved adult staff names, work email addresses, roles, schools or sites, survey invitations, response status, and identified or anonymous survey answers as selected by the customer.
- Implementation-action information: a customer-selected recipient’s name and work email, the customer-authored action plan and message, provider send acceptance or failure, first secure-link access, acknowledgment, a submitted completion summary and completion date, and the customer’s review decision.
- Application usage information: licensed or rostered-user counts, active or unique-user counts, launches, reporting periods, product and school associations, and—only if a future customer-authorized connection enables it—employee-level application assignment or activity.
- Support, security, and operational information: support messages, access and change history, file-validation and malware-scan results, audit events, device and session security information, and service logs.
- Limited website and product analytics: a hashed browser identifier, page path without query values, surface, event name, and a small set of bounded properties such as section, outcome, landing page, referring hostname, and short campaign source, medium, campaign, content, or target-region codes. Forebeam’s analytics event records do not include typed text, document contents, survey answers, student information, full query strings, or IP addresses, and Forebeam does not derive visitor location from IP addresses, although infrastructure providers may process connection information in ordinary service logs.
Sources of information
Forebeam receives information directly from people who request a walkthrough, contact support, create or use an account, upload an administrative document, respond to a survey, or respond to a customer-owned implementation action. It also receives customer-controlled information from authorized administrators, reviewed imports, and customer-directed service providers or integrations. Forebeam may derive limited operational information—such as response counts, adoption percentages, renewal timing, audit events, and evidence summaries—from those authorized sources. Forebeam does not purchase personal-information lists or obtain student records from data brokers.
Employee authentication and ClassLink
Forebeam supports a ClassLink OneClick OAuth sign-in flow for separately authorized employee tenants and roles. During certification, that flow is limited to ClassLink-provided test accounts; no real customer ClassLink tenant is currently active. Forebeam uses the immutable ClassLink tenant and user identifiers for account linking and may receive an employee's name, work email, role, organization name, and building identifier. Provider access tokens are not retained. Newly provisioned employees begin with no Forebeam product or school access until a customer administrator grants it.
Forebeam also supports reviewed ClassLink imports. The usage format accepts school-and-product totals, while the adult staff-directory format accepts names, work email addresses, roles, and school associations. A separate read-only OneRoster connection may be enabled only after the customer authorizes its tenant, resources, and adult roles and Forebeam activates protected provider credentials. That connection requests only schools and approved adult staff; it does not request classes, enrollments, grades, demographics, student roles, or family roles. ClassLink access and OneRoster rostering do not by themselves provide product-launch analytics.
Forebeam does not intentionally seek student data through ClassLink. Reviewed imports reject unsupported columns, and the OneRoster boundary rejects an entire provider page before persistence if it contains a student, family, disabled, inactive, unknown-role, malformed, or out-of-scope record. The current usage format does not accept individual activity. Forebeam does not claim that a provider or customer could never misconfigure a connection; each live tenant must still be explicitly authorized, tested, and approved through the customer's security and privacy review.
Individual and aggregated usage reporting
Usage information helps customers understand whether purchased applications are reaching their intended staff and schools. Forebeam may calculate totals, percentages, trends, and school-, product-, or organization-level summaries. If employee-level reporting is enabled in the future, it will be available only to users permitted by the customer’s organization, school, feature, and individual access rules. Usage is one decision signal and is not treated as proof of educator effectiveness, instructional quality, or the correct purchasing outcome.
How information is used
Forebeam uses information to authenticate users; maintain customer workspaces; organize software and contract records; administer educator feedback; route customer-owned implementation actions and review completion updates; connect authorized usage evidence; prepare human-reviewed summaries; support purchasing and renewal workflows; deliver requested messages; secure, troubleshoot, and improve the service; respond to support and privacy requests; and comply with applicable law. Forebeam does not sell customer data, use customer-provided data for behavioral advertising, or use educator information to build advertising profiles.
Responsible use of educator information
Forebeam is designed to help authorized teams review products and implementation—not to evaluate individual employees. Forebeam does not make automated employment, compensation, promotion, discipline, termination, or educator-performance decisions. Application usage and survey information can be incomplete or context dependent and must not be treated as proof of an educator’s effectiveness or conduct. Customers are responsible for using identified information lawfully, limiting access to people with a legitimate need, and providing any notices or choices required by their policies or applicable law.
Customer control and access permissions
Customers determine the authorized data scope, select users and survey participants, choose whether a survey is anonymous or identified, configure roles and school access, and decide whether optional integrations and AI assistance are enabled. Forebeam applies server-side organization membership, school or site scope, feature permission, and resource-access checks. Authorized customer administrators are responsible for maintaining accurate access and removing access that is no longer appropriate.
Anonymous survey responses are stored without a recipient, email, user, or IP reference, and small-group results remain hidden until the configured minimum response threshold is met. Identified surveys retain the invitation association so the customer can conduct the follow-up it selected.
Sharing and service providers
Forebeam may disclose information only as needed to the customer and its authorized users; approved service providers; customer-directed integrations; professional advisers, auditors, or authorities when reasonably necessary; or a successor in a transaction subject to applicable confidentiality and legal requirements. Forebeam does not authorize service providers to use customer information for their own advertising.
Forebeam’s current service-provider schedule is:
- DigitalOcean (required): application hosting, managed PostgreSQL, private object storage, backups, and infrastructure logs. Forebeam’s current application, database, and private object-storage regions are listed on the subprocessor page; limited support or operational processing may also occur where DigitalOcean and its approved subprocessors operate.
- Resend (used when email delivery is enabled): transactional account, survey, and workflow messages. It receives recipient email addresses, message content, delivery metadata, and secure Forebeam links; Forebeam does not send document attachments through Resend.
- OpenAI API (optional): AI-assisted extraction and summaries only after the service, workspace, and customer controls described below are enabled. It receives only the bounded content required for the selected request.
ClassLink and similar customer-directed integrations are enabled only within the customer-approved scope; their contractual processing role is defined by the applicable agreement and data-processing terms. Forebeam will document a materially new provider or processing purpose and, when reasonably practicable, follows an operating target of at least 15 business days’ advance notice before a material provider change begins processing customer information, subject to the applicable customer agreement. Provider location, transfer, retention, and contractual details are documented in the customer’s subprocessor schedule or data-processing agreement.
AI processing
AI assistance is optional and controlled by three gates: a server-side provider configuration, Forebeam authorization for the workspace, and the customer’s opt-in. When enabled, Forebeam can send text from supported administrative contracts, quotes, or invoices to prepare a draft, or send bounded commercial records, aggregate usage, and approved educator feedback to prepare an evidence summary. The currently implemented provider is the OpenAI API. Forebeam configures these API requests with provider-side application storage disabled and does not use customer information to train a Forebeam model or opt customer content into provider model-improvement programs.
AI does not automatically save records, identify anonymous respondents, or make purchasing, renewal, employment, discipline, compensation, or educator-performance decisions. Authorized people review the output, and manual workflows remain available. Forebeam does not intentionally send student data for AI processing. Disabling application storage is not a promise of universal zero retention: limited provider security or abuse-monitoring retention may apply under the provider’s terms unless separate approved controls establish otherwise. Provider terms and any customer-specific AI restrictions remain subject to the applicable agreement and customer approval. Additional details appear in Forebeam’s AI Transparency and Use Policy.
Retention and deletion
Forebeam applies retention by information category, subject to a shorter period required by the customer agreement or applicable law:
- Customer workspace, portfolio, survey, implementation-action, and contract records: retained while the customer account is active so authorized users can review historical cycles and decisions. After service ends, Forebeam provides a 30-day export window. At the end of that window—or earlier if the customer waives export—Forebeam deletes these records from active systems within 30 days unless legal preservation is required.
- Implementation-action recipients and links: recipient names, work email addresses, completion updates, and customer review history follow the customer-workspace schedule. Each secure external-recipient link expires after 30 days, and Forebeam stores only its hash rather than the usable link token.
- Survey-recipient information: names and work email addresses are deleted or irreversibly detached from response content 30 days after the survey closes. The response content, archived cycles, summaries, and trends remain available in deidentified form while the customer account is active.
- Verified deletion requests: personal information and uploaded administrative documents are deleted from active systems within 10 business days unless a legal hold applies; otherwise the post-service export and deletion schedule applies.
- Rejected or quarantined uploads: retained for bounded troubleshooting for no more than seven days. Confirmed-malware bytes are deleted after non-content evidence is recorded.
- Support and business inquiries: retained for 24 months after the request closes unless continued retention is legally required.
- Limited website and product analytics: retained for no more than 24 months.
- Access, review, deletion, and security audit evidence: retained for seven years in restricted form without retaining source documents or survey contents solely for the audit record.
- Protected backups: removed through the documented backup-rotation schedule after deletion from active systems, unless preservation is required by law or an approved legal hold. Forebeam’s approved target is expiration within 35 days, but it will not represent that target as a binding customer commitment until the applicable customer wording is reviewed and approved.
Verified requests may result in export, correction, deletion, or de-identification where applicable. Forebeam records deletion progress and backup-expiry state rather than claiming immediate deletion from every protected backup.
Security practices
Forebeam uses server-side organization and role checks, scoped school and feature permissions, production HTTPS, secure HTTP-only same-site session cookies, Argon2 password hashing, hashed expiring invitation and reset links, rate limits, and production-enforced authenticator-app MFA for Forebeam platform administrators. Commercial documents use private quarantine and clean storage, file type and checksum validation, malware scanning, non-public downloads, audit evidence, monitored backup coverage, and guarded deletion and recovery procedures. Important security and recovery procedures have been exercised with synthetic data.
No safeguard eliminates every risk. Forebeam has not completed an independent penetration test or obtained a formal security certification, and this policy does not claim otherwise.
Security incidents
Forebeam maintains procedures to identify, contain, investigate, document, and recover from suspected security incidents. If Forebeam confirms unauthorized access to customer information, it will notify the affected customer without unreasonable delay and no later than 72 hours after confirmation, unless applicable law requires earlier notice. Forebeam will provide information reasonably available for the customer’s response and take appropriate steps to contain and remediate the incident. Contract-specific contacts and cooperation duties are documented in the customer’s data-processing agreement or security exhibit.
Privacy rights and requests
Depending on location and applicable law, a person may have rights to request access, correction, deletion, restriction, objection, or portability; withdraw consent where consent is the basis for processing; and complain to a privacy or data-protection authority. These rights may be limited by exemptions or by another lawful basis for retaining information.
For customer-controlled information, employees should normally contact their employer or education organization first because that organization determines the relevant workspace and reporting settings. Forebeam will support verified customer instructions and will respond directly where Forebeam is responsible for the request. Submit a request through the privacy request form, email [email protected], or call (941) 315-4678. Forebeam will not discriminate against a person for exercising an applicable privacy right.
International processing and GDPR
Forebeam and its service providers may process information in the United States and other countries where they operate. Laws in those locations may differ from the laws where the individual lives. Before Forebeam accepts personal data subject to the European Union or United Kingdom GDPR, Forebeam and the customer must document the relevant roles, processing locations, transfer mechanism, and contractual safeguards. Where GDPR applies, the rights described above may also include a right to object to certain processing and to lodge a complaint with the appropriate supervisory authority.
Children and student information
Forebeam is an administrative service for authorized adults and is not intended for direct use by children. Customers must not submit student-level information unless Forebeam and the customer have first approved that data scope in writing and implemented the necessary technical and legal controls. No student-data scope is currently approved.
If Forebeam becomes aware that student-level information was submitted outside the approved scope, it will restrict access, investigate the source and affected records, notify and coordinate with the customer, and securely delete or return the information as directed, except where preservation is legally required. Forebeam will not use accidentally received student information for product analytics, AI processing, advertising, or a new purpose. Any future student-data feature would require prior written approval, a documented data flow, appropriate access and retention controls, customer review, and updated contractual and public disclosures before activation.
Changes and contact
Forebeam may update this notice as the service and approved integrations change. Material changes will be reflected by a new update date and, where required, customer notice.
Privacy, security, or rights requests may be sent to [email protected], by phone at (941) 315-4678, through forebeam.ai, or by mail to:
Forebeam LLC1317 Edgewater Dr #127
Orlando, FL 32804
United States