Blumind Privacy Policy
Effective date: October 17, 2026
Blumind Group LLC (“Blumind,” “we,” “us”) operates the Blumind shared account and sign-in service at https://accounts.blumindg.com. This policy explains how we handle information when you create an account, sign in, connect a sign-in provider, manage your profile, or use your account to access a participating Blumind product.
Contact for support and privacy requests: support@blumindg.com
Business mailing address: Blumind Group LLC, 4450 Tubular Run, Land O Lakes, FL 34638, US.
This policy covers shared login, account profiles, provider linking, sessions, account recovery, and central account deletion. Participating products may include WindLoadAPI, SnowLoadAPI, SeismicLoadAPI, WindExposureAPI, and TopoFactorAPI where integration is available. Engineering queries, project locations, API usage, billing, purchases, and uploads are addressed by the relevant product’s privacy notice in addition to this account policy.
Information we handle
-
Account information: your name, email address, email-verification status, account identifier, and profile changes. If you set a Blumind password, we store a password hash.
-
Google or Microsoft sign-in information: your provider’s account identifier, name and email address when supplied, and information used to verify the sign-in, such as the provider and authentication time. We retain an association between your provider identity and your Blumind account.
-
Session and security information: session identifiers, sign-in and account-security events, technical request information such as IP address and browser information, and temporary information used to complete a login securely.
-
Product connections: the participating app you are signing into, the account linked to that app, and the destination needed to return you to the page where you started.
-
Communications: information you send when requesting support or exercising privacy choices.
Google and Microsoft sign-in
When you choose Google or Microsoft sign-in, we request basic identity permissions: OpenID, profile, and email. We use the returned information to identify you, create or authenticate your Blumind account, securely connect a sign-in method, and provide access to the participating product you selected.
This sign-in integration does not request permission to read your Gmail or Outlook messages, Google Drive or OneDrive files, contacts, or calendars. You enter your provider password with Google or Microsoft; Blumind does not receive that password.
We store the provider account identifier, email information, and connection status needed to recognize future sign-ins. Authentication responses are processed to validate the login. The current Google and Microsoft integration does not retain provider access or refresh tokens for later access to other provider services.
Google and Microsoft also process information under their own privacy policies. You may manage the connection in your provider’s account settings. Revoking provider access does not itself delete your Blumind account or product records.
How we use and share information
We use account information to operate sign-in, maintain sessions, verify email addresses, recover accounts, manage connected sign-in methods, prevent abuse, investigate problems, respond to support requests, and coordinate account changes with participating products.
When you sign into a participating Blumind product, we share the account identifier and profile information needed for that product to recognize your account. We also exchange account status and security information needed for account changes, sign-out, and deletion.
We use service providers for functions such as hosting, databases, email delivery, and operational support. They receive information needed to perform those functions.
We may disclose information where required by law or where necessary and legally permitted to protect people, accounts, or the service.
We do not sell account identity information, use it for personalized advertising, or use it to train general-purpose AI models. This commitment includes identity information obtained through Google and Microsoft sign-in. We use Google user data only for the purposes described in this policy and in accordance with the Google API Services User Data Policy, including applicable Limited Use requirements.
Marketing requires a separate opt-in and is not a condition of creating an account or signing in. Account, security, and service messages are separate from marketing. Product-specific practices are addressed in the relevant product notices.
Cookies and security
Blumind uses authentication and security cookies and related session information to keep you signed in, protect requests, and connect the steps of a login. It does not use third-party behavioral analytics. Blocking these cookies can prevent sign-in from working. Google, Microsoft, and participating products may set their own cookies under their respective notices.
We use safeguards such as HTTPS, password hashing, and checks designed to protect sign-in and account linking. No online service can guarantee complete security.
Retention and deletion
We retain account profiles and provider links while your account is open. After a verified deletion request, we aim to remove these active records within 30 days, subject to the limited exceptions described below. Temporary login information expires; expiration of a session or token does not by itself erase every associated security record.
You can request deletion through the account-deletion controls or by contacting support. Before confirmation, the deletion notice explains the affected linked accounts, product data, and access. Confirmed deletion promptly revokes account access and sessions, stops future subscription renewals, and initiates cleanup across linked products. Deletion can proceed in stages. Disconnecting a sign-in provider is different from deleting your account. Refunds follow the applicable product refund policy; deleting an account does not automatically issue a refund.
Documented legal holds or active investigations may require specific records to be kept longer than the normal schedule. Financial and accounting records follow a separate retention schedule under the relevant product notice and applicable law. Exceptions are limited to the records and duration needed for the documented purpose.
Retention schedule
| Record category | Retention period or deletion target |
|---|---|
| Account profiles and provider links | While the account is open; remove from active systems within 30 days of a verified deletion request |
| Sensitive login payloads | Clear on completion of login |
| Expired login transactions | Purge within 24 hours of expiry |
| Security and access logs | 90 days |
| Support conversations | 12 months after resolution |
| Minimal deletion audit records | 12 months |
| Backup copies of deleted data | Expire within 90 days after deletion from active systems |
| Financial/accounting records | Separate schedule under the relevant product notice and applicable law |
Your choices and privacy requests
You can update account information, manage available sign-in methods, sign out, and request account deletion. Keep an available recovery or sign-in method before removing a connection.
Contact support@blumindg.com to request access, correction, deletion, or other rights that apply to you. We may ask for information reasonably necessary to verify the request. We will acknowledge privacy requests within five business days and aim to complete them within 30 calendar days, subject to applicable legal deadlines and permitted extensions. The rights and exceptions available depend on applicable law.
We currently serve customers in the United States. Your rights depend on applicable law; nothing in this policy limits rights that cannot lawfully be limited.
Blumind’s account service is intended for people who are at least 18 years old and legally able to enter into the Terms. It is not directed to children. Contact support@blumindg.com if you believe an underage person has provided account information.
We will post an updated policy when our practices change. We normally provide 30 days’ advance notice of material changes, except where urgent security or legal circumstances require a shorter period. We will provide additional notice or obtain consent where required by applicable law. The effective date identifies the current version.