Bright Privacy Policy
Effective date: 5 November 2026
Last updated: 5 November 2026
The short version
- We never sell your personal information, and we never share it for advertising.
- Bright contains no analytics, advertising or tracking software of any kind. Not one third-party measurement SDK ships in this app.
- We cannot read your messages. They are encrypted on your device and we hold only sealed ciphertext we have no key for.
- We do not collect your device's location. The app never asks for it, and the permission is blocked in the build itself.
- We do not store your Social Security Number, passport number or taxpayer identification number. Our identity provider verifies it; we keep only which kind of document was checked and that it passed.
- We cannot delete your transaction history, and neither can you. U.S. law requires us to keep money-movement records, and our ledger is built so that nothing can rewrite them. This is explained under Your choices and rights.
The rest of this policy is the detail behind those six sentences.
1. Who we are
Bright is operated by Bright Investments Group, LLC, a California limited liability company ("Bright", "we", "us").
- Registered address: 18002 Irvine Blvd., Suite 108, Tustin, CA 92780
- Privacy contact: privacy@bright-sphere.com
- Postal privacy requests: 18002 Irvine Blvd., Suite 108, Tustin, CA 92780
This policy covers the Bright mobile app, the Bright web app at https://bright-sphere.com, and the services behind them.
Bright is for people aged 18 and over. Our identity checks reject anyone under 18, and we do not knowingly collect information from children. If you believe a child has given us information, write to privacy@bright-sphere.com and we will delete what we are permitted to delete.
2. What we collect, and why
We have grouped this by why we have it, because that is the question that actually matters. Where something is required by law rather than chosen by us, we say so.
2.1 To open and hold your account
| What | Why |
|---|---|
| Your mobile number | It is how you sign in and how other people send money to you |
| Your name | Required to open an account that moves money |
| A password, stored only as a one-way hash | So we can check it without being able to read it |
| A six-digit wallet PIN, stored only as a one-way hash | Confirms it is really you before money leaves your account |
We never store your password or your PIN in a form anyone — including us — can read or recover. Both are hashed with bcrypt.
2.2 To verify who you are, because the law requires it
U.S. law requires a company that moves money to identify its customers before it does so. This is the Customer Identification Program under the Bank Secrecy Act. We collect:
- your full legal name
- your date of birth
- your residential address (a PO box is not accepted, because the rule requires a residential address)
- one identification number: a Social Security Number, an ITIN, or a passport number
We do not keep the identification number. It goes to our identity verification provider, which checks it. What we retain is the kind of document that was checked, whether each element was verified, and your date of birth. The number itself is not written to our database, our logs, or our audit records.
We also screen your name against U.S. government sanctions lists, including the Specially Designated Nationals list, and we keep a record of every screening — including the ones that found nothing, because those records are the evidence that the screening happened.
If a sanctions screening blocks your account, we are legally prohibited from telling you that is the reason. We are not permitted to explain it, and this is the one circumstance in which Bright will not tell you why something happened. It is a federal prohibition, not a policy choice.
2.3 To move money, and to keep the records the law requires
Every movement of money creates a permanent record: who sent it, who received it, the amount, the currency, when, and a cryptographic seal that makes the record tamper-evident.
These records cannot be changed or deleted — not by you, not by us, not by anyone at Bright. Our ledger is append-only by construction, with database rules that refuse any attempt to modify or remove an entry. A correction is recorded as a new entry; a refund is a new entry; a reversal is a new entry. Nothing is ever rewritten.
We do this for two reasons. The Bank Secrecy Act requires money services businesses to retain transaction records for five years. And an audit trail that someone can quietly edit is not an audit trail.
2.4 To detect fraud
| What | Why | How long |
|---|---|---|
| Your IP address | Every request to our servers includes it | See §4 |
| An approximate location derived from your IP — country, region, city, and how accurate that estimate is | To notice a payment from somewhere it is implausible you could be | 90 days |
| Whether the connection appears to be a VPN, proxy or hosting provider | A pattern worth weighing, not a reason to decline on its own | 90 days |
| Your device's identifier within Bright, and which devices hold your card | So you can review your own devices and spot one you do not recognize | While the account is open |
Bright does not collect your device's location. The app does not request location permission, and the Android build explicitly blocks the fine and coarse location permissions so that no dependency can request them either. The location we work with is estimated from your IP address, is accurate to roughly a city at best, and we record how inaccurate it may be so our own rules cannot pretend to a precision they do not have.
Under California law, precise geolocation is sensitive personal information. What we derive from an IP address is not precise geolocation — we treat it as ordinary personal information, and we do not collect the precise kind at all.
2.5 To let you message people
Bright's messaging is end-to-end encrypted using the Signal protocol.
- Your private keys are generated on your device and never leave it.
- Our servers hold your public keys, so people can start a conversation with you.
- Our servers hold sealed ciphertext that we have no ability to open, plus the minimum routing information needed to deliver it: who it is from, who it is for, which devices, and when.
- There is deliberately nowhere in our database to put readable message content.
We can see that you messaged someone. We cannot see what you said. That distinction is real and it is structural, not a promise about our conduct.
The same applies to Note to Self: it is encrypted with a key only your devices hold.
2.6 To let you post, and to keep the feed usable
If you set a profile picture or post to the feed, we store the image and any caption. Both are public-facing: anybody you transact or chat with can see your profile picture, and feed posts are visible as the feed's settings allow.
If you report a post, we keep the report so a human can act on it.
A decision about content never touches your money. Removing a post or suspending someone from the feed does not freeze a balance, block a transfer, or write anything to the ledger — and a payments decision never removes a post. These are separate powers inside Bright and no single action exercises both.
2.7 If you accept card payments as a business
Merchant onboarding collects information about the business and about the people behind it: the legal and trading name, entity type, formation state, registered address, business purpose, merchant category, expected monthly volume, and a taxpayer identifier. For each beneficial owner holding 25% or more and for at least one controlling person, we also run the personal identity check described in §2.2 — being named on a business application is not identification.
As with personal identification, we do not store the business's Employer Identification Number. Only the kind of identifier presented and whether it was verified.
When you tap a card on a Bright device, we never see the card number. The payment token the reader produces is encrypted for our payment service provider; we forward it without opening it. What our records hold is the network's reference, the card network's name, and the last four digits — the things that appear on a receipt.
Suspending a business never touches anyone's personal money. If a business is suspended from accepting payments, the people behind it keep their personal wallets, their balances, their ability to send and receive, their messages and their feed.
2.8 What we do not collect
To be concrete, because "we value your privacy" is not information:
- No analytics. No Google Analytics, no Firebase, no Segment, no Amplitude, no Mixpanel, no crash-reporting SDK. None.
- No advertising identifiers, no ad networks, no ad SDKs.
- No tracking across other apps or websites. We do not do it, and there is no code in Bright capable of it.
- No device location, as described in §2.4.
- No contact list upload. We never read your address book.
- No microphone access. The permission is blocked in the build.
- No message content. As described in §2.5, we cannot read it.
3. Who we share information with
We do not sell your personal information and we do not share it for cross-context behavioral advertising. Under California law those terms have specific meanings, and neither applies to anything Bright does.
We share only with parties that do something we cannot do ourselves:
| Who | What they get | Why |
|---|---|---|
| An identity verification provider — not yet engaged | The identity details in §2.2, including the identification number | To verify your identity, as the law requires |
| A sanctions screening provider — not yet engaged | Your name, date of birth and country | To screen against government lists |
| A partner bank — not yet engaged | Account and transaction information | Deposits are held at a partner bank; it is the bank that holds them |
| A payment service provider — not yet engaged | Transaction details and the encrypted card token | To authorize and settle card payments |
| Card networks and card issuers | Transaction details, through a payment service provider — not yet engaged | To authorize a payment and to handle disputes |
| A card issuing bank — not yet engaged | The details needed to issue and service a Bright Card | A card is issued by a bank, not by us |
| A business verification provider — not yet engaged | The business details in §2.7 | To verify a business exists and is what it says |
| Amazon Web Services | Whatever our systems store, as the infrastructure they run on | To run the service |
| Government authorities | What we are legally compelled to produce | Subpoenas, court orders, and reports required by law |
| An acquirer of our business | Your information, subject to this policy | If Bright is ever sold or merged |
A row marked “not yet engaged” describes something that is not happening yet. Bright is in development, and where we have not signed an agreement with a provider, we say so rather than leaving the row out — you are entitled to know where your information is designed to go, not only where it goes today. These are categories, which is what the law asks us to disclose; we will name the specific company in this table before any of your information reaches them, never afterwards.
Until then, nothing is sent to those providers, and that is enforced rather than intended: identity verification, sanctions screening and business verification each refuse to run when no provider is configured, instead of passing you by default.
We require every provider above to use what we give them only to do the job we hired them for.
4. How long we keep things
| What | How long | Why that long |
|---|---|---|
| Transaction records in the ledger | At least 5 years after the transaction, and in practice permanently | Required by the Bank Secrecy Act; our ledger is append-only and cannot delete |
| Identity verification records | 5 years after your account closes | Required by the Customer Identification Program |
| Sanctions screening records, including clear results | 5 years | They are the evidence that screening happened |
| Delivered messages (ciphertext) | 24 hours after delivery, then deleted | Nothing needs them once they have arrived |
| Undelivered messages (ciphertext) | 30 days, then deleted | A phone that has been off for a month is not coming back for them |
| Approximate location from IP | 90 days | It stops being useful for fraud comparison long before it stops being sensitive |
| Audit records of actions on your account | 5 years | They are how a dispute gets resolved |
| Profile picture and feed posts | Until you delete them, or the account closes | — |
| Account details (name, number, PIN hash) | While the account is open, then as long as the retention rules above require | — |
5. Your choices and rights
Everyone
You can, at any time:
- see and correct your account details in the app
- delete your profile picture and your own feed posts
- see your full transaction history, with a traceability record for every movement
- see which devices hold your Bright Card, and remove one
- close your account
If you live in California
Under the California Consumer Privacy Act as amended (CCPA/CPRA) you have the right to know what we collect, to a copy of it, to correct it, to delete it, to limit our use of sensitive personal information, and not to be discriminated against for exercising any of these. We do not sell personal information or share it for cross-context behavioral advertising, so there is nothing for you to opt out of — but you may ask us to confirm that.
If you live in another U.S. state with a privacy law
[CONFIRM WHICH STATE LAWS APPLY — at minimum Virginia, Colorado, Connecticut, Utah and Texas have comparable rights, and the list grows. A lawyer should set this section.]
The honest limit on deletion
We cannot delete your transaction records, and we will tell you so rather than pretending otherwise.
Two reasons, and both are real:
- The law requires us to keep them. A money services business must retain transaction and identity records for five years. A deletion request does not override that, and every U.S. privacy law has an exception for records a business is legally required to keep.
- Our ledger is built so they cannot be deleted. Entries are sealed in a cryptographic chain and the database refuses any statement that would modify or remove one. This is deliberate: a financial record that someone at Bright could quietly erase would not be worth anything to you either, on the day you needed it to prove what happened.
What we will do on a deletion request: close your account, delete your profile picture and your posts, delete your messages, delete your location history, and stop using your information for anything other than the records we are required to keep. We will tell you specifically what was deleted and what was retained, and why.
How to make a request
Write to privacy@bright-sphere.com. We will verify that the request is really from you — for an account that holds money, we are not willing to act on an unverified request — and we will respond within 45 days, extending once by a further 45 days if we must and telling you if we do. You may use an authorized agent; we will ask for proof of their authority.
6. How we protect your information
Specifics, because generalities are not reassuring:
- Messages are end-to-end encrypted, with private keys that never leave your device (§2.5).
- Nothing travels in the clear. The app refuses plaintext network connections at the operating system level.
- Passwords and PINs are hashed with bcrypt and are not recoverable.
- We never hold a card number. Card data is tokenized before it reaches us (§2.7).
- Identification numbers are not stored at all (§2.2).
- The ledger is tamper-evident. Each entry is cryptographically chained to the one before it, so altering a past entry is detectable.
- Our application cannot modify the audit log or the ledger. It connects to the database as a role that holds no permission to update or delete those tables, in addition to the database rules that refuse it.
- Your wallet PIN is checked on our servers, and the lockout count lives there too — so reinstalling the app cannot reset it.
- Sensitive values are kept out of logs by design, including identification numbers, card tokens and taxpayer identifiers.
No system is perfectly secure, and we will not claim ours is. If a breach affects you we will notify you and the relevant regulators as the law requires.
7. Where your information is held
Bright's systems run in the United States, in the United States — AWS us-west-2 (Oregon), with us-east-2 (Ohio) as a warm standby.
If Bright later serves customers outside the United States, we will update this section before doing so, and say what changes.
8. Changes to this policy
If we change this policy in a way that materially affects you, we will tell you in the app before the change takes effect — not by quietly updating a date at the top of a web page. Every version is kept, and https://bright-sphere.com/privacy/versions/ lists them.
9. Contact
Bright Investments Group, LLC 18002 Irvine Blvd., Suite 108, Tustin, CA 92780 privacy@bright-sphere.com
If you are not satisfied with how we have handled a privacy request, you may complain to your state attorney general, and California residents may complain to the California Privacy Protection Agency.
Appendix A — Apple App Privacy answers
Not part of the policy. This is the matching set of answers for the App Privacy section of App Store Connect, which must be consistent with the policy above — Apple compares them, and a mismatch is a rejection.
Does your app collect data? Yes. Do you use data to track users? No. Nothing in Bright tracks across apps or websites, and no advertising or analytics SDK ships in the app.
| Apple category | Collected | Linked to identity | Used for tracking | Purposes |
|---|---|---|---|---|
| Contact Info → Name | Yes | Yes | No | App Functionality |
| Contact Info → Phone Number | Yes | Yes | No | App Functionality |
| Contact Info → Physical Address | Yes | Yes | No | App Functionality |
| Financial Info → Payment Info | Yes | Yes | No | App Functionality |
| Financial Info → Other Financial Info | Yes | Yes | No | App Functionality, Fraud Prevention |
| Identifiers → User ID | Yes | Yes | No | App Functionality |
| Identifiers → Device ID | Yes | Yes | No | App Functionality, Fraud Prevention |
| Sensitive Info | Yes | Yes | No | App Functionality — government identification for the legally required identity check |
| User Content → Photos | Yes | Yes | No | App Functionality |
| User Content → Other User Content | Yes | Yes | No | App Functionality — message ciphertext we cannot read |
| Location → Coarse Location | Yes | Yes | No | Fraud Prevention — derived from IP address, not from the device |
| Location → Precise Location | No | — | — | The app never requests it |
| Usage Data | No | — | — | No analytics of any kind |
| Diagnostics | No | — | — | No crash-reporting SDK |
| Contacts | No | — | — | We never read your address book |
| Browsing History | No | — | — | — |
| Search History | No | — | — | — |
| Purchases | Yes | Yes | No | App Functionality — purchases made inside Bright |
Two answers worth getting right, because both are easy to get wrong:
- Coarse Location: Yes. It is tempting to answer No, since the app never asks for location permission. But Apple asks what data you collect, not what the device grants — and Bright's servers derive an approximate location from the IP address. Answering No would be inaccurate.
- User Content → Other User Content: Yes. Also tempting to answer No, since the content is ciphertext we cannot read. But we do collect and store it. Declare it, and explain in the policy that it is sealed.