This Privacy Policy describes how Project Lancer, LLC (“Lancer,” “we,” “us,” or “our”) collects, uses, shares, and retains information when you use app.lancer.pro, our APIs, and related services (the “Service”). It is intended to describe actual practices. It is not a substitute for reading our Terms of Service.
1. Who we are and how to contact us
Controller / operator: Project Lancer, LLC (operator of the Service at app.lancer.pro).
Privacy and support contact: info@lancer.pro
2. Information we collect
2.1 Information you provide directly
- Account and profile information — name, email address, password (stored as a one-way hash), optional phone number, country (ISO code), optional city or region, timezone, profile picture, notification preferences, identity-verification status for the account owner, and similar profile fields.
- Organization (workspace) information — account name, account type (freelancer, agency, or client), business type used for tax labeling, members and roles, and related settings. For freelancer and agency accounts, this may include a self-declared tax-document type (for example W-9 or a foreign tax form). Lancer stores the declaration only; it does not collect, store, or file the underlying tax forms.
- Customer Content — projects, tasks, milestones, checklists, clients/customers, invoices and line items, work logs, income and expense records, job posts, applications, proposals, connections, chat messages, uploaded documents and images, and other content you enter into the Service.
- Support and communications — messages you send to us and related correspondence.
2.2 Authentication and session information
We issue access and refresh tokens after login. Tokens may be stored in your browser’s local storage. We also store password-reset and email-verification codes/tokens as needed to operate those flows.
2.3 Financial information via Plaid
If you connect a bank account through Plaid, you authenticate with Plaid (not by giving Lancer your bank username and password). Lancer receives tokens and data from Plaid needed to sync account metadata and transactions, such as institution name, account name/mask/type, and transaction details. Lancer stores Plaid access tokens in encrypted form. When you disconnect a bank connection, we instruct Plaid to remove the item and mark the connection disconnected in our systems; previously synced transaction records may remain until deleted under our retention practices or your account deletion request.
2.4 Payment and subscription information via Stripe
Lancer subscriptions. Payment card details for your Lancer subscription are collected and processed by Stripe. Lancer stores Stripe customer/subscription identifiers, plan and seat metadata, billing status, and related billing history references needed to operate the product. We do not store full payment card numbers on Lancer servers.
Identity verification. If an account owner pays to verify their identity, Stripe Checkout processes that one-time payment. Stripe Identity then collects identity document images, a selfie, and related device/fraud signals. Lancer stores verification status, Stripe session identifiers, timestamps, and a one-way fingerprint used to prevent the same identity from verifying more than one user. We do not store copies of identity documents or selfies on Lancer servers.
Your invoices to your clients. If you connect Stripe Connect, invoice and payment processing for those invoices occurs on your connected Stripe account. Lancer may store connected-account identifiers, encrypted access credentials we need to call Stripe on your behalf, customer and invoice mirrors, and status information. End-client payment methods are handled by Stripe under Stripe’s terms and privacy policy.
2.5 Device, log, and technical information
Like most online services, our hosting and application infrastructure may automatically process IP addresses, timestamps, request metadata, error logs, and similar technical data when you use the Service. We may record IP address and user-agent when you accept the Terms of Service for audit purposes.
2.6 Cookies and similar technologies
The Lancer web app uses browser storage (including localStorage and sessionStorage) for authentication tokens, theme preferences, and certain draft UI state. We do not currently operate a separate first-party advertising analytics SDK in the application. Third-party widgets you use inside the Service—such as Stripe Elements/Checkout, Stripe Identity, and Plaid Link—may set their own cookies or local storage subject to those providers’ policies.
3. How we use information
We use information to:
- Provide, operate, secure, and improve the Service;
- Create and manage user and organization accounts, roles, and invitations;
- Process subscriptions, seats, credits, and related billing;
- Enable invoicing, income/expense tracking, bank transaction review, and related features you use;
- Send transactional email (verification, invitations, password reset, product notices);
- Moderate uploaded images for abuse/safety where those checks are enabled;
- Prevent fraud, abuse, and security incidents;
- Comply with law and enforce our Terms;
- Respond to support requests and communicate about the Service.
We do not sell personal information for money. We do not use Customer Content to build advertising profiles for third-party ads. We do not currently engage in “selling” or “sharing” personal information for cross-context behavioral advertising as those terms are commonly defined under California law. If that changes, we will update this Policy and provide required notices/opt-outs.
4. Who receives information
We share information with service providers that process it on our instructions to run the Service, including:
- Stripe — payments, Checkout, Connect, and Identity;
- Plaid — bank linking and transaction sync;
- SendGrid (or similar) — transactional email;
- MongoDB Atlas — database hosting;
- Amazon Web Services — application hosting, object storage (files), and related cloud services;
- Other subprocessors we engage for infrastructure, security scanning, or support, under appropriate contracts.
We may also disclose information to professional advisors, to successors in a merger or asset transfer, or when required by law, legal process, or to protect rights, safety, and security.
Other Lancer users you invite, message, hire, invoice, or otherwise interact with may see information you choose to share through the Service (for example profiles, proposals, chat, and invoice details).
We use Stripe for identity document verification. Stripe collects identity document images, facial images, ID numbers and addresses as well as advanced fraud signals and information about the devices that connect to its services. Stripe shares this information with us and also uses this information to operate and improve the services it provides, including for fraud detection. You may also choose to allow Stripe to use your data to improve Stripe’s biometric verification technology. You can learn more about Stripe and read its privacy policy at https://stripe.com/privacy.
5. Retention
We retain information for as long as your account remains active and as needed to provide the Service. After account deletion or disconnection of an integration, we may retain residual copies in backups, logs, or archives for a limited period, and we may retain certain records longer when required for legal, tax, fraud-prevention, security, or dispute-resolution purposes. Plaid-synced transactions and Stripe identifiers may persist after a disconnect until purged under these criteria.
Organization account deletion removes the account record through product controls; associated operational data may be deleted, de-identified, or retained under the criteria above. If you need a specific deletion or export request beyond in-product tools, contact info@lancer.pro.
6. Access, correction, and deletion
You may update certain profile and account settings in the product. Account owners may delete an organization account in Settings where that control is available. Partial exports (for example CSV downloads of income/expense lists) may be available in-product. For broader access, correction, or deletion requests, email info@lancer.pro. We may need to verify your identity and the scope of your request. Some data cannot be deleted when we must retain it by law or for legitimate security/billing records.
7. International transfers
Project Lancer, LLC is based in Missouri, United States. We primarily operate infrastructure in the United States (including AWS regions used by the Service). The Service is available to users outside the United States; if you access it from outside the U.S., your information may be processed in the United States and other locations where we or our providers operate. Where required, we use appropriate transfer mechanisms.
8. State privacy rights
Residents of certain U.S. states (including California and others with comprehensive privacy laws) may have rights to request access, deletion, correction, or information about our data practices, and to appeal a denied request, subject to legal exceptions. To exercise these rights, contact info@lancer.pro. We will not discriminate against you for exercising privacy rights available to you.
Because we do not sell personal information or share it for cross-context behavioral advertising in the ordinary operation of the Service as described above, we do not currently offer a “Do Not Sell or Share” opt-out link. If our practices change, we will update this Policy.
9. Children’s privacy
The Service is not directed to children under 18, and we do not knowingly collect personal information from children under 18. If you believe a child has provided information, contact us and we will take appropriate steps.
10. Security practices
Lancer maintains administrative, technical, and organizational safeguards designed to protect information against unauthorized access, loss, misuse, or alteration. Examples of measures we use in the Service include password hashing, encrypted storage of certain third-party access tokens (such as Plaid and Stripe Connect tokens), private object storage for uploaded files, transport over HTTPS for our web and API endpoints, and access controls within the application. Optional malware scanning of uploads may be enabled in some environments.
No method of transmission or storage is completely secure. We cannot guarantee absolute security. You are responsible for protecting your credentials, configuring permissions carefully, and securing devices you use to access the Service.
11. Breach response
If we become aware of a security incident affecting personal information we hold, we will investigate and take steps we consider appropriate under the circumstances, which may include containment, remediation, and notification to affected customers and regulators when required by applicable law. We do not waive legal obligations by describing these practices at a high level.
12. Changes to this Policy
We may update this Privacy Policy from time to time. The version and effective date appear at the top. Material changes may be announced through the Service or by email. Continued use after the effective date means you acknowledge the updated Policy, except where applicable law requires a different form of consent.
13. Contact
Privacy questions and requests: info@lancer.pro
Service: https://app.lancer.pro