Version 2026-10-24 · Effective upon publication.
Privacy notice
Who operates the service
Rasiel Perez Castillo operates BrightHub at getbrighthub.com. Contact the operator about account and privacy questions at:
Rasiel Perez Castillo, operating BrightHub308 Ave G SW, Suite 202
Winter Haven, FL 33880, USA
support@getbrighthub.com
Information used by BrightHub
Account information includes your name, email, password hash, email-verification status, sessions and account-recovery records. Workspace information includes membership, access roles, business settings, subscription status and records showing which terms and privacy-notice version an account accepted.
Businesses may add staff hours, tasks, appointments, client contact details, notes, custom fields, forms, answers, signatures, attachments and optional operational records. Business owners choose what to collect and who may access it. Private form links allow the intended recipient to view and complete a requested form; anyone given that link may be able to use it, so keep it private.
How information is used
Information is used to provide accounts and workspace features, verify access, maintain business records, manage subscriptions and customer appointment payments, record and reconcile refunds, deliver requested account messages, answer support requests, investigate service problems and maintain backups. Businesses are responsible for their own notices and lawful collection and use of client or employee information.
BrightHub uses the limited first-party measurements described below to understand signup and early product use. It does not use third-party advertising pixels or external marketing embeds on its public pages, sell personal information, or use workspace records to create advertising audiences. Account cookies maintain sign-in and access; signing out everywhere revokes active BrightHub sessions and unused workspace handoffs.
Workspace usage measurements
BrightHub collects limited daily counts of authenticated workspace operation requests to understand which tools businesses use, identify operational failures and improve the service. Each count contains the UTC calendar day, a workspace identifier, a defined tool category, whether the request succeeded or failed, and the number of requests. Retries may count more than once. These measurements do not count individual people or the number of business records created.
Usage measurements do not contain staff or client names, email addresses, client or appointment identifiers, notes, form contents or answers, attachments, payment-card or bank information, checkout links, typed text, raw URLs, location coordinates, IP addresses, session tokens or screen recordings. Workspace identifiers remain linkable to the business; these are private workspace-level statistics, not anonymous data. Access is restricted to verified platform administrators. BrightHub stores these statistics within its existing AWS infrastructure and does not send them to a separate analytics provider.
Workspace-linked daily counts use a 90-day reporting window. Automated maintenance removes older active counts and runs on startup and at least hourly while the application is operating; processing may be delayed during an outage or recovery. Active counts are removed when the operational workspace is permanently removed. Backup copies follow the separate expiration process below; recovery must honor surviving workspace deletion decisions. Account, security, subscription and customer-payment records have their own purposes and retention described in this notice. Contact support@getbrighthub.com about usage measurements or privacy requests.
Optional website and signup measurements
On BrightHub public marketing and signup pages, you may choose Allow or Decline optional measurement. Before Allow, BrightHub does not create a measurement identifier or send visit and signup events. Declining does not prevent signup or use of the service. A first-party preference is stored in your browser for up to 90 days so the site can remember your choice. BrightHub honors the browser's Do Not Track and Global Privacy Control signals for these optional measurements.
If you allow measurement, your browser creates a random identifier and stores it with your choice and a limited set of campaign labels for up to 90 days. The server stores a hash of that identifier, your consent version, the time of your first measured visit and signup-form interaction, and recognized source, medium, campaign and content labels from the link you used. Unknown labels are discarded. BrightHub does not store the full referring page or URL, arbitrary query values, form field values, IP address, device fingerprint or screen recording in these measurements. An untagged link has an unknown source; campaign labels supplied by a browser are not independently verified.
If you create a workspace within seven days of that first measured visit and after a measured signup-form interaction, BrightHub can link the browser measurement to the new workspace identifier. This helps identify where the measured browser cohort stops between visiting, starting signup, creating a workspace and using tasks. The measurements count consenting browser identifiers, not all visits or unique people. No past visits are reconstructed.
Use Measurement choices on a public marketing, signup, sign-in or workspace-hub page to withdraw. Withdrawal stops optional measurement in that browser and requests removal of its active visitor record and workspace attribution. A hashed suppression token is retained for up to 90 days after withdrawal to reject delayed events; it contains no campaign labels or workspace link. If the network request fails, the browser keeps only the identifier needed to retry removal and shows that removal is still pending. Separate workspace service measurements described below remain. Clearing browser storage removes the local preference but does not itself request server removal; contact support if you no longer have the browser identifier.
Early workspace use
For eligible new workspaces created after measurement is enabled, BrightHub records the workspace identifier, creation timestamp, whether it was created by a new or existing account, the first qualifying committed task save and completion timestamps, UTC dates of qualifying task activity, and the first later-day task-use timestamp. A qualifying task save is a meaningful manual change to a task that has an assignee and due date. Failed saves, unchanged retries, automatically generated tasks and imported records do not produce these milestones. Client and staff names, task text, task identifiers and other record contents are not included.
These limited service measurements are recorded independently of optional browser measurement. They help improve the new-workspace experience, including for businesses whose visit source is unknown. Configured internal workspaces and platform administrator accounts are excluded; anonymous internal browsing cannot always be identified before sign-in. Saving a task or registering a workspace does not establish that a person became an active or paying customer. BrightHub reports new workspaces separately from consenting browsers and does not infer unique new people from additional workspaces.
Visitor records expire 90 days after the first measured visit. Workspace milestone records expire 90 days after workspace creation, or when the operational workspace is permanently removed. Hashed withdrawal tokens expire 90 days after withdrawal. Automated removal runs on startup and at least hourly while the application operates; outages or recovery can delay processing. These records are private, can remain linkable to a workspace, are accessible only to verified platform administrators, and stay within BrightHub's existing AWS infrastructure without a separate analytics provider. Backup copies follow the separate expiration process below. Contact support@getbrighthub.com about measurement or privacy requests.
Observed subscription outcomes
For the eligible new-workspace cohorts described above, BrightHub may compare the workspace identifier with existing, server-verified software-subscription billing records to report whether a positive payment has been confirmed. Reports can group these observed outcomes by the limited campaign labels when an optional browser-to-workspace link exists and you have explicitly allowed measurement that includes these outcomes before creating that workspace. Earlier permission for visits and early task use is not automatically extended to payment attribution. When this expanded choice is offered, Allow records its version and consent time; declining keeps access available and leaves payment attribution unknown. This reporting is independent of task activation and does not require a task action to count an observed payment. Missing, declined, expired or withdrawn attribution remains unknown.
This comparison reads existing confirmed invoice and access records; it does not add advertising pixels, send data to an advertising provider, change subscription access or copy client records into analytics. A trial enrollment, checkout return, test payment or complimentary period is not counted as a positive payment. Reports contain aggregate workspace counts, coverage and observation times. They do not establish current subscriber counts, a complete payment or refund history, net revenue, or that an advertisement caused a payment.
The comparison is available only while the existing acquisition cohort and any optional attribution remain within their 90-day retention windows. Withdrawal removes the browser attribution while separate workspace-level outcomes can remain available for that cohort window. Existing subscription billing records keep their separate operational retention described below. Only verified platform administrators can access these reports.
Optional location checks
If a business enables location-based staff access, nonowner team members may be asked to allow browser location access when opening that workspace. The server checks the reported location against approved sites. Current checks retain outcomes and matched site identifiers rather than employee coordinates. Browser-reported location can be inaccurate and does not guarantee physical presence. Ask your business owner about its access policy if location is unavailable or denied.
Service providers and access
BrightHub uses AWS infrastructure in the United States, including hosting, encrypted backups and transactional account email. Stripe processes BrightHub's software subscription payments and, where enabled, customer appointment payments through its hosted pages. BrightHub stores subscription identifiers and status separately from the customer-payment ledger described below. Payment-card entry takes place directly with Stripe. Porkbun hosts the support mailbox. Providers process information needed to supply their respective services.
Workspace records are available to authorized members according to their roles. Operational support may require approved technical access; do not send private client records, passwords, payment-card data or sensitive form answers by ordinary email. We may disclose information when required by law or needed to address unlawful activity or threats to the service.
Customer appointment payments
Businesses use their own Stripe merchant accounts to collect customer appointment payments. BrightHub collects, stores and sends Stripe the business registration country selected by the owner to begin merchant setup. The remaining identity and payout verification information, including any identity document requested by Stripe, is provided directly to Stripe under its own notices and terms. BrightHub also stores the connected merchant-account identifier and setup status needed to check whether the account can accept payments.
To create and reconcile an appointment checkout, BrightHub sends Stripe the amount, currency, a generic appointment-payment description and identifiers linking the transaction to its workspace and appointment. BrightHub does not send the saved client name, service name, client notes or form answers as the checkout description. Stripe also receives the information the customer supplies on its checkout page. BrightHub does not collect or store card numbers or security codes through this workflow. Do not put them in client records, forms, notes or support messages.
The separate BrightHub payment ledger contains client and service identifiers and names, the appointment date and time, the saved amount and currency, payment and refund status, timestamps, merchant and transaction references, and receipt or checkout links where supplied. It also retains refund requests, retry records and provider-event identifiers used to prevent duplicate actions and verify outcomes. These are identifiable business records, not anonymous usage statistics.
Owners, managers and front-desk staff can review their workspace's payment records; employee-only accounts cannot. Only the owner can connect the merchant account or request refunds through BrightHub. After ordinary workspace access ends, financial-record access is limited to the verified owner or a separately verified support request. Exported files contain personal information and should be stored and shared only with authorized people.
Retention, export and deletion
Records are retained to provide accounts, workspace features, subscriptions, customer payments, support, security and backups. When cancelled paid access is confirmed to have ended, the operational workspace records enter a 30-day recovery window with an exact deadline shown in Subscription. Delayed confirmation may extend that window. The verified owner can download an operational workspace ZIP, subject to the launch server's 64 MiB export limit, or reactivate before the deadline. Ordinary team access is paused during this window. Trial expiry and payment retries alone do not schedule permanent removal.
BrightHub attempts owner notices at scheduling, approximately seven days before the deadline, and approximately one day before it. After the deadline, records become eligible for permanent removal, subject to safety checks, warning delivery and any applicable legal requirement. Removal can take longer than the displayed deadline; this does not promise continued access or recovery. Contact support@getbrighthub.com for export or deletion assistance. We verify identity and authority before releasing information or acting on a request.
Operational removal clears the affected workspace's active operational records, team links, pending requests and local attachments; it does not automatically remove the separate customer-payment ledger. Shared accounts and other businesses' workspaces are not removed with it. Limited software-subscription billing references, security records and deletion receipts remain to process later payment events, investigate problems and prevent an older backup from reopening removed information. Deletion receipts contain workspace identifiers and removal metadata rather than saved client records or form answers.
Encrypted backups have their own expiration process. Backup copies may persist after active removal until their versions expire; the active-record deadline is not a promise of simultaneous deletion from every backup. A recovery must honor the surviving deletion authority before records can be used again. Contact support for information about a specific deletion request or applicable retention requirement.
Separate customer-payment records
Customer-payment records are held separately from operational workspace backups. The ordinary workspace ZIP does not contain this ledger, and restoring an operational backup does not reverse payments or refunds. A verified owner can open Workspace administration → Customer payment records to download a separate payment-record export while the owner's account remains available and ownership can be verified, including after subscription access ends or operational workspace records have been removed. Contact support if the export is too large, the owner's account is unavailable or ownership needs review. We do not release financial records based only on a supplied email address or workspace identifier.
The separate ledger remains after operational workspace closure to support transaction reconciliation, refunds, disputes, verified requests and protection against duplicate financial actions. It is not subject to the automatic 30-day operational recovery deadline, and no fixed automatic deletion period is currently established for these records. Contact support to request a separate payment-record deletion review. We review which client, service and appointment details can be removed or minimized when they are no longer needed for unresolved transactions, refunds, disputes, security or an applicable legal obligation. The review may preserve transaction references and other necessary records; it is not a promise that all financial information can be erased immediately.
Financial-record review also considers copies held in protected platform backups. Backup expiration follows the separate lifecycle described above rather than an immediate per-record erasure. A platform recovery must preserve the applicable deletion or minimization decisions and reconcile payment records with Stripe before customer collection resumes. Stripe controls its own payment and merchant records under its own retention rules; removing information from BrightHub does not delete Stripe's records.
Requests and your choices
Contact support about access, correction, export, deletion or privacy questions. We verify identity and authority before fulfilling a request. If a business collected your information in its workspace, contact that business first so it can address your request and instruct BrightHub where needed. Applicable law may provide additional rights; these statements do not limit those rights.
BrightHub accounts are intended for adult business users, not accounts created by children. Businesses remain responsible for information they collect about clients. Special categories of regulated information are not supported until appropriate arrangements have expressly been agreed.
Changes and international use
The public notice will identify its effective version and date. Material changes will be communicated before they apply. Hosting is currently in the United States; customers in other countries should assess the requirements applicable to their business before entering personal information. An international-facing website is not a claim of worldwide regulatory certification.