Privacy Policy
Corply Privacy Policy
Last updated: October 31, 2026
Corply handles sensitive founder, company, filing, payment, and document information. This policy explains what we collect, why we use it, when we share it, and how founders can make privacy requests.
Important Summary
- We use founder and company information to provide incorporation, filing, document, approval, payment, support, security, and company record workflows.
- We do not sell personal information.
- We do not use customer company data, founder documents, or uploaded records to train AI models.
- We share information with service providers and workflow participants only when needed to operate Corply, complete authorized workflows, comply with law, or protect the service.
- Payments for Corply's own charges are entered in Stripe's secure payment fields on Corply or on Stripe's checkout page. For accounts billed through Corply Pay, Corply's payment software, card details are entered into secure payment fields provided by Finix, our card processor, and bank details into a secure bank form provided by Payabli, our bank (ACH) processor. These processors collect and store full card numbers, card security codes, and bank account numbers; Corply does not receive or store them.
- Corply Cards are issued by a sponsor bank through Lithic, our card-issuing processor. Full card numbers and security codes are shown only in Lithic's secure card frame; Corply does not store them.
- Formation workflows can require sensitive information. Do not upload anything you are not authorized to provide.
1 · Scope
This Privacy Policy explains how 0Lumen Labs Corp. d/b/a Corply collects, uses, discloses, retains, and protects information when you visit our websites, create an account, use Corply products, communicate with us, or authorize company formation, filing, document, approval, payment, or support workflows.
This policy applies to Corply's services. It does not apply to websites, portals, banks, registered agents, government agencies, payment processors, identity providers, attorneys, accountants, or other third-party services that operate under their own privacy policies.
2 · Information We Collect
- Account and contact information, including name, email address, phone number, login metadata, team membership, role, and support communications.
- Optional Google Workspace resale: when your company requests this separate service, Corply keeps its domain, selected member and Google account identifiers, initial administrator selection, consent, quote, subscription and payment references, setup evidence and cancellation status. Authorized operators share the setup information needed by Google and the fulfillment distributor. This setup workflow does not read or store your Gmail messages or Calendar events, collect Google passwords in Corply forms, or accept Google's agreement for your company. Your company's Workspace content and Google's processing role are governed by the applicable Google customer agreement and data-processing terms; Corply's account, billing and operational records remain subject to this policy. Optional Gmail document discovery is a separate permission and purpose.
- If you grant the optional Google profile permissions during Google sign-in, Google may provide your name, birthday, addresses, and phone numbers. Corply stores available values as unconfirmed suggestions so you can review and confirm or edit them instead of retyping them. Corply does not store the short-lived Google access token used for the import, and sign-in can continue if a profile field is unavailable.
- Founder and company information, including proposed company names, entity details, addresses, founder names, ownership details, equity context, officer/director/incorporator information, tax and filing facts, and workflow instructions.
- When you authorize supported tax-document workflows, we collect the taxpayer identification number through a secure form and use it to prepare the requested document. Sensitive tax PDFs are stored encrypted and accessed for authorized preparation, review, and filing. Paying for preparation or signing a stock agreement does not itself establish that a tax election was filed.
- Documents and records you provide or generate, including formation documents, founder approvals, signatures, uploaded files, generated drafts, filing evidence, receipts, audit logs, and company memory records.
- Payment and billing records, including Corply Pay checkout, payment, receipt-number, billing-cadence, selected-service, renewal-schedule, invoice, refund, dispute, and bank-return records and the related processor reference identifiers (such as Finix transfer, identity, and payment-instrument identifiers and Payabli transaction, customer, and stored-method identifiers); payment-method type and, when the processor provides them, card brand, card funding type, expiration, and last four digits, or bank name, account type, and last four digits; payment-method assignments for plan and, when enabled, Delaware tax purposes; order amount and currency; billing status; immutable quote and plan snapshots; and authorization evidence, including the authorization text and separate grants you accepted, when you accepted them, later changes or revocations, the Terms and Billing & Refund Policy versions in effect, and the IP address and browser user agent used. When Corply Tax is enabled and you authorize it, we also keep the annual-report facts, government-fee and franchise-tax calculation, exact advance notice, scheduled charge, reporting year, obligation fingerprint, settlement, filing, and reconciliation records. Card and bank details are entered into secure payment fields provided by Stripe, or into Finix card fields and the Payabli bank form for accounts billed through Corply Pay, which send them directly to those processors. The processors collect and store full card numbers, card security codes, and full bank account numbers. Corply does not receive or store those full card credentials or full bank account numbers. For payments processed by Stripe, Corply keeps the Stripe customer, Checkout, PaymentIntent, subscription, invoice, refund, and dispute identifiers and descriptors it records.
- Bank account details for ACH payments. You never give Corply your bank login credentials, and Corply does not request your account balances or transaction history. When you enter a bank account in Payabli's secure form, Payabli may check that it is a valid, open U.S. account that can accept debits. Corply keeps its own record of the ACH debit authorization you accepted, including when you accepted it and the IP address and browser user agent used.
- Corply Pay payment requests. If your company uses Corply Pay to send invoices, payment requests, or reimbursement requests, we process the request details you enter (such as the payer's name, email address, and organization, line items, memo, and expense details), the payer's payment status and receipt, and the software fee, gross, and net amounts of each payment. Payers enter card or bank details only in the processors' secure fields. To receive payments, your company completes the processors' own onboarding (identity, ownership, and payout bank account verification), which Finix and Payabli collect under their own terms and privacy policies; Corply keeps the resulting onboarding status, processor references, and the last four digits of the payout account.
- Corply Cards. If your company uses Corply Cards, we process the cardholder's name and email address, card nickname, type, state, spending limits and controls, the last four digits and expiration of each card, card transaction details (such as amount, status, merchant name, merchant category code, city, and country), and a record of each time a card's full details are viewed. Lithic and the sponsor bank that issues the cards process card data and any account-holder information they require under their own terms and privacy policies. Full card numbers and security codes appear only in Lithic's secure card frame, only on the web, and Corply does not store them.
- Corply Mail: mailbox applicant and USPS Form 1583 details, identity-verification status, mailbox permissions, envelope images, scanned correspondence, sender and recipient details, forwarding addresses and phone numbers, mail-handling requests, shipping records, and authorization evidence. For Stable-backed mailboxes, Stable and its authorized providers physically handle mail and process onboarding evidence; Corply forwards identity-evidence uploads without storing the file bytes. Authorized mailbox users can access mail images and scans, and authorized Corply personnel may access them for the limited purposes described in this policy. Mail arrival and service-status emails link to Corply rather than include correspondence content.
- Usage, device, and security information, including IP address, browser type, device identifiers, session data, pages viewed, product events, error logs, authentication events, and anti-abuse signals.
- AI and automation workflow inputs and outputs, including prompts, extracted facts, summaries, generated drafts, task state, review notes, and operational decisions needed to provide the service.
3 · Google User Data
When you sign in with Google, Corply receives your name, email address, and basic profile information to create and secure your account. Corply may also ask for optional permissions to read your birthday, addresses, and phone numbers from your Google Account. You can decline any of these optional permissions and still use Corply.
How we use it: Corply uses Google user data to sign you in and to prefill your own founder profile, company formation forms, and domain registrant details, so you can review, confirm, or edit those values instead of retyping them. Imported values stay unconfirmed suggestions until you confirm them, and they are shown only to you and to AI assistants you choose to connect to your Corply account. Optional company-document discovery, when available, requires separate consent as described below.
Optional Gmail and Drive discovery: when available, signing in with Google also asks for read-only Gmail access, which you can untick on Google's screen without affecting sign-in, and you can separately authorize read-only access to Gmail and Google Drive during an open company import. You can also connect other Gmail accounts you control, which can differ from your Corply login and are used only for this search, never to sign in. Corply uses this access only to find SAFEs, side letters and other company records for your company imports, searching investment documents first. Gmail searches cover PDF attachments across accessible mail history, including archived mail, spam and trash. Drive searches cover accessible PDFs and Google Docs, including shared drives, but exclude deleted files. Corply reads message content transiently to locate attachments, and keeps filenames, message subjects, sender names, dates, source references and search progress as private search results. It does not retain message bodies as search results, send email, or modify your Gmail or Drive files. Search coverage and access failures are shown in the import; unsupported file types and inaccessible documents require manual upload.
Optional Google mail: where verified scopes and pilot access are enabled, you may separately connect your own Google mailbox for one company. This account can differ from your Corply login. Google verifies the account and you confirm its address before Corply mail actions become available. With your distinct mail consent, Corply can search and read messages and attachments, create and update drafts, send exact emails you explicitly approve, and organize messages and labels. Google's Gmail modify permission covers the entire selected mailbox, including personal and other-company messages; Corply does not receive a provider-enforced company-only subset. Only your signed-in Corply account may use that connection. A company owner, operator, another member or an admin preview does not thereby gain your Gmail access. Requested messages, attachments and draft details are shared with your connected MCP or AI client for the mail actions you authorize. Those selected clients process the data under their own applicable terms and privacy policies. Human mailbox work remains in Gmail; Google continues to host your messages.
Mail credentials and records: Corply encrypts access and refresh credentials on the server, binds the verified Google account and connection generation to your user and company, and retains consent and the minimal draft, review and action records needed to perform and recover the work you authorize. Exact send approval does not authorize a different draft or later message. Google credentials are never returned to your assistant. General mail permission is separate from read-only document discovery, Corply sign-in, Workspace purchasing and Calendar access; a prior document-search grant is not silently expanded into mail permission.
Document review and sharing: search results remain private to your account and your authorized assistant. Only documents you specifically choose are downloaded into your import. Corply uses its AI service providers to read those selected documents and propose company facts for your review; authorized Corply personnel may review these selected documents. Confirming the normal company import can also share those documents with authorized company members. Unselected search results are not shared with your company or Corply reviewers. You can decline document discovery and continue signing in or upload files yourself.
How we store and protect it: imported profile values and private search metadata are stored in Corply's access-controlled database, encrypted in transit and at rest. Corply does not store the short-lived token used solely for profile prefill. If you authorize document discovery, Corply separately encrypts the Google access and refresh credentials needed to resume searches and check for new documents while your import is open; access granted at sign-in is kept the same way. No search runs before you start it from a company import or after you disconnect document search. These credentials are held on the server and never given to your assistant.
How we share it: we do not sell Google user data, use it for advertising, or share it with data brokers. We share it only with service providers that host and operate Corply, and with a workflow participant (such as a domain registrar or state filing provider) only after you confirm the value for a workflow you authorize, or when required by law.
AI and model training: we do not use Google user data to develop, improve, or train generalized or non-personalized AI or machine-learning models, and we do not allow our vendors to do so.
Retention and deletion: unconfirmed profile suggestions are kept until you confirm, replace, or remove them, or delete your account. Disconnecting document search stops that purpose for that account and removes its private search results. Disconnecting mail removes that company-specific mail connection; it does not delete Gmail messages or cancel Google Workspace. Each local disconnect preserves other Google features you have separately authorized. Credentials still needed for those purposes are retained only for their remaining authorization; you can remove all Corply Google permissions in your Google Account settings. Documents already selected for import remain under the normal company-document retention rules and may be removed through the import before confirmation. To delete Google user data, email founders@0lumens.com with the subject line Privacy Request; we delete it within 30 days except where a value you confirmed became part of a signed or filed company record we must retain. You can revoke Corply's access at any time at myaccount.google.com/permissions.
Corply's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
4 · Sources of Information
We collect information directly from you, from Google when you grant optional profile permissions during sign-in, from other users who invite you or act for the same company, from product usage, from documents you upload, from service providers that support approved workflows, and from public or government sources when needed to complete or verify company workflows.
5 · How We Use Information
- Provide, operate, and support the services you request or authorize. Confidential record content is not used for unrelated product development or improvement; aggregate usage metrics used for improvement do not contain confidential record content or identify you or your company.
- Prepare, route, review, submit, track, and store company formation, filing, approval, document, registered-agent, EIN, compliance, payment, and support workflows you request or authorize.
- Maintain company records, audit trails, receipts, evidence, deadlines, and workflow history.
- Authenticate users, administer accounts, manage access, prevent fraud and abuse, debug issues, monitor reliability, and protect security.
- Communicate about account activity, support requests, approvals, filings, payments, purchase acknowledgments, renewal reminders and approvals, billing confirmations, policy changes, security notices, and service updates.
- Analyze product usage and business performance. Where analytics is enabled, product events may be associated with your account identifier, email address, and profile information. We also use aggregated usage reports.
- Comply with legal obligations, enforce our Terms of Use, respond to lawful requests, and protect Corply, users, third parties, and the public.
6 · AI Providers and Model Training
Corply may use AI providers and automation systems to draft, extract, summarize, classify, check, route, and suggest actions. We use those systems to provide the product and operate approved workflows.
We do not sell confidential company records or use customer company data, founder documents, uploaded records, or private workflow content to train AI or machine-learning models. We do not permit our AI vendors to train their models on that content. When we use AI vendors to deliver requested features, we configure and contract for business use cases that prohibit training on customer content. Processing content to extract facts, check documents, or produce requested outputs is distinct from training models.
AI outputs can be incomplete or wrong. Privacy protections do not change your responsibility to review documents, facts, filings, approvals, and instructions before relying on them.
If you connect Corply to an AI agent you choose, that agent's provider processes your conversation and information returned to it under its own terms and your account settings. Corply does not control that provider's independent data-use or model-training settings.
8 · No Sale of Personal Information
We do not sell personal information. We also do not share personal information for cross-context behavioral advertising as those terms are commonly used under U.S. state privacy laws.
10 · Retention
We retain information for as long as needed to provide Corply, maintain company records and audit trails, comply with legal and tax obligations, resolve disputes, enforce agreements, protect security, and operate our business.
For Stable-backed mailboxes, Stable's published policy generally provides 30 days of physical mail storage before secure shredding is scheduled unless forwarding is arranged, and digital scans may be retained indefinitely by Stable. Cancellation does not itself delete scans or arrange forwarding. Corply's copies remain subject to this policy, and deleting a Corply copy does not itself delete an operator copy. You may contact us to request deletion and help coordinating with the operator; independent provider retention and legal obligations may apply.
Company formation and approval records may be retained longer than ordinary account data because founders, companies, investors, banks, accountants, counsel, and diligence reviewers may later need evidence of what was approved, signed, filed, paid, or received.
We retain payment processor identifiers (Stripe, Finix and Payabli), order and authorization evidence, receipts, refund, dispute, and bank-return records, and limited payment-method descriptors as needed for accounting, tax, fraud prevention, customer support, legal claims, and audit obligations. Billing authorization records, including plan cadence and service selections, payment-method purpose assignments, versioned grants, renewal changes, cancellations, Delaware tax notices and revocations when that service is enabled, and ACH debit authorizations, are kept while the authorization is in effect and afterward for as long as payment-network, Nacha, bank, and dispute rules require. Removing a saved payment method does not require deletion of transaction records we must retain, and Corply cannot delete information retained independently by Finix, Payabli, Lithic, a sponsor bank, or Stripe under their own policies or legal obligations.
11 · Security
We use technical, organizational, and administrative safeguards designed to protect information, including access controls, encryption in transit, cloud security controls, logging, and least-privilege operational practices.
Access to confidential records is limited to authorized personnel and providers who need it to deliver or support your requested services, protect security, or meet legal obligations and who are subject to confidentiality obligations. Staff may verify document completeness and consistency, check workflow results, investigate errors, and resolve support requests. These purposes do not authorize unrelated browsing or use of your records as general training or testing material.
If we become aware of unauthorized access to or disclosure of your confidential records in Corply's possession or control, we will notify affected customers without undue delay, explain what we know and the steps being taken, and provide material updates as the investigation progresses, subject to applicable law and lawful restrictions.
No system is perfectly secure. You are responsible for protecting your credentials, limiting access to your account, reviewing invited users, and maintaining your own copies of important company documents.
12 · International Users
Corply is operated from the United States and is built for U.S.-connected company workflows. If you use Corply from outside the United States, you understand that your information may be processed in the United States and other jurisdictions where our providers operate.
13 · Privacy Rights and Choices
Depending on where you live, you may have rights to access, correct, delete, export, or restrict certain personal information, or to object to certain processing. These rights may be limited where information is needed for company records, legal obligations, security, fraud prevention, or completed workflows.
To make a privacy request, email founders@0lumens.com with the subject line Privacy Request and include the email address connected to your Corply account. We may need to verify your identity and authority before acting on a request.
14 · Children
Corply is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided information to Corply, contact us so we can review and delete it where appropriate.
15 · Changes
We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new last updated date. We will notify affected users of significant changes through the product or by email before those changes take effect, except where applicable law requires an earlier change. We will not use previously collected confidential records for a new, incompatible purpose without obtaining any consent required by applicable law.
16 · Contact
For privacy questions or requests, contact founders@0lumens.com.