Scope
This notice applies to mabnee.com, Mabnee accounts, guided onboarding, roadmaps, Business Passport and workspace features, billing records, contact requests, and other Mabnee-operated workflows that link to this notice. A third-party provider’s separate notice also applies when its service is used.
Information Mabnee handles
Account information
When you create or use a Mabnee account, the authentication service may process your name, email address, authentication credentials or federated sign-in identifiers, sessions, and security information needed to sign you in and protect the account.
Business profile and planning information
Mabnee may process business type, legal or working name, structure, formation state, planned start date, business description, goals, timeframe, roadmap progress, selected services, business members, application-readiness information, compliance tasks, and related workspace records.
Some onboarding continuity can exist in browser local storage. When you are signed in, eligible onboarding and business-workspace information can also be synchronized to Mabnee’s account-linked cloud database so it can follow the authorized account across devices.
Payment and billing information
Stripe processes payment-card, bank, wallet, and other payment credentials used in Stripe-hosted checkout or billing-management surfaces. Mabnee does not need to store raw payment-card numbers. Mabnee stores transaction references and operational billing records such as the selected service, Mabnee service amount, separately tracked government fee, tax amount, total amount, payment or subscription status, Stripe customer/session/subscription/invoice references, and verified webhook event history.
Government and provider workflow information
When an activated filing, registered-agent, vendor, licensing, or other provider workflow is requested, Mabnee may process the business information needed to prepare, coordinate, or transmit that authorized service. Sensitive identifiers are handled only through a dedicated workflow when actually required.
Secure document-vault information
When the Secure Document Vault is activated and you choose to upload a file, the file is sent directly to Mabnee’s private AWS S3 quarantine using a short-lived, exact-size upload grant. AWS applies customer-managed encryption and GuardDuty malware scanning. Mabnee’s database stores the owning business, random object reference, original filename, content type, size, SHA-256 checksum, scan state, retention state, and access/deletion audit events. The file is not released for download unless the live AWS scan tag reports no threats.
Vault files are customer-controlled records retained until an authorized owner deletes them or another disclosed legal or account-lifecycle requirement applies. An owner deletion removes all S3 object versions and delete markers for the random key. Minimal deletion and security-audit evidence may remain where needed for security, legal obligations, or dispute resolution; CloudTrail vault audit logs have a 365-day infrastructure retention policy.
Stripe Identity verification
For the purpose-limited formation-owner authorization workflow, Mabnee may offer Stripe Identity’s hosted verification. Stripe—not Mabnee—collects identity-document images, facial images, ID numbers, addresses, advanced fraud signals, and device information. Stripe shares the verification result with Mabnee and uses the information to provide and improve its services, including fraud detection, subject to Stripe’s terms and privacy notice.
Mabnee stores only the authenticated business and user references, Stripe verification-session reference, purpose, consent version and time, minimized status, safe error code, and signed event history. Mabnee does not store Stripe’s identity images, verified personal fields, biometric template, raw webhook, or verification report. An authorized owner can request provider redaction when Stripe permits it; Stripe states that completion can take up to four days. A non-biometric support path is available when consent is declined or the hosted method is unavailable.
Contact and support information
Contact requests may include your name, email address, business context, support topic, and message. Do not place sensitive identity, financial, medical, credential, or private-key information into ordinary support messages.
Website request and security data
Hosting, content-delivery, authentication, database, domain, network, email, and security infrastructure may process technical data such as IP address, date and time, requested path, browser/device information, referral information, session/security signals, error logs, and abuse-prevention events.
Information Mabnee does not request in ordinary profile fields
Ordinary Mabnee business-profile and roadmap fields are not designed for Social Security numbers, full payment-card data, online-banking passwords, private keys, patient health information, or identity-document images. A future or activated workflow that legitimately needs high-risk data must use a dedicated secure field or provider flow with separate purpose, access, retention, and deletion controls.
How information is used
- To authenticate users and protect Mabnee accounts.
- To save, restore, and synchronize authorized business-planning work.
- To generate roadmaps, application-readiness queues, compliance obligations, and business-workspace views.
- To create eligible payment sessions from Mabnee’s server-controlled catalog and reconcile verified payment-provider events.
- To fulfill or coordinate services that a user expressly requests and authorizes.
- To respond to support, security, privacy, and service inquiries.
- To deliver, secure, troubleshoot, audit, and improve the platform.
Sharing and service providers
Mabnee uses service providers needed to operate the platform. Depending on the feature, those may include hosting and deployment providers, Neon for database/authentication infrastructure, AWS for encrypted document storage, malware scanning and audit logs, Stripe for payments, billing and hosted identity verification, email-delivery providers, DNS/security providers, and specifically activated business-service providers.
For a filing, registered-agent, licensing, vendor, or professional workflow, Mabnee shares information only as needed for the authorized service and subject to the applicable provider relationship and disclosures. Government agencies receive information only through an authorized submission or user-directed handoff.
Mabnee does not sell personal information to advertisers and does not silently alter service recommendations because a third party paid for placement. Any future sponsored placement must be clearly disclosed.
Payment security
Stripe-hosted payment surfaces are used to keep raw payment credentials out of ordinary Mabnee application storage. Mabnee verifies Stripe webhook signatures and maintains an idempotent server-side event ledger before authoritative transaction states change.
Cookies and local storage
Mabnee uses browser storage and authentication/session technologies needed for account continuity, security, and product functionality. Hosting and security infrastructure may also use cookies or similar technologies. Optional analytics or advertising technologies require separate review and notice before material deployment.
Retention
Mabnee retains account, business-workspace, transaction, audit, and service records for the period reasonably necessary to provide the service, maintain security and financial records, comply with law, resolve disputes, and enforce agreements. Different record classes can have different retention requirements.
Browser-local data remains until browser settings, application controls, profile changes, or browser behavior removes it. Account-linked cloud records are handled separately from browser-local copies.
Deletion and account choices
You may request account or data assistance through the Contact page. Some records cannot be immediately deleted when retention is required for payment reconciliation, tax/accounting, fraud prevention, security, legal obligations, provider disputes, or government filing evidence. Where deletion is not immediately available, Mabnee should limit continued use to the required purpose.
Security
Mabnee uses HTTPS, account authentication, row-level authorization for protected business records, server-controlled billing logic, verified payment-provider events, and other technical and organizational controls appropriate to the active feature. No internet service can guarantee absolute security. See the Security page for additional information.
Children
Mabnee is intended for adults building or operating businesses and is not directed to children. Do not submit a child’s personal information through the platform.
Your choices
- Choose whether to create and use a Mabnee account.
- Limit the information entered to what is needed for the requested workflow.
- Clear browser-local Mabnee data through browser controls.
- Manage eligible recurring billing through the available billing-management path or contact Mabnee for help.
- Request privacy or account assistance through the Contact page.
Changes
This notice may be updated as Mabnee’s functionality and providers change. Material changes will receive an updated effective date and additional notice or consent where required.
Contact
Use the Contact page for privacy questions. Do not include SSNs, payment-card numbers, financial credentials, passwords, patient information, private keys, or identity documents in an ordinary contact message.
Effective date: August 28, 2026
Back to top