Information we collect
The information processed depends on how you use RevenueLancer and which features your business enables.
- Account and workspace information: names, email addresses, account identifiers, profiles, invitations, business details and access roles supplied during signup or workspace use.
- Workspace and customer records: lead names, contact details, companies, notes, follow-ups, pipeline stages, source records, assignments, custom fields, feedback and communication records entered by your business or received through configured capture tools and integrations. CSV imports may contain these same categories.
- Billing records: selected plans, subscription periods, amounts, currencies, payment references, statuses, invoices and usage or entitlement records. Payments use the available payment processor; RevenueLancer does not ask for complete payment card credentials in workspace forms.
- Contact and support information: the full name, email address and message submitted through our public Contact form, submission timestamps and processing status, and account context you choose to provide in support requests.
- Technical information: request metadata used for security and regional pricing, timestamps, application errors, audit events and integration processing results. Infrastructure providers may also process request and diagnostic information.
How we use information
We process information to operate RevenueLancer, authenticate users, maintain workspaces, provide configured sales workflows and respond to support or Contact requests.
Relevant information is also used to administer subscriptions and payments, send account or operational communications, investigate errors, improve reliability, enforce access restrictions and prevent abuse. Records may be needed for applicable obligations or disputes. This policy does not describe an advertising-tracking or customer-data resale program.
Workspace and customer data
Businesses decide what customer and business information they enter or connect. RevenueLancer processes it to provide the requested service; submitting a record does not transfer ownership of business content to RevenueLancer.
Access is designed to be scoped by business membership and role. Private workspace records are not published as public marketing content or intentionally shared with another business. Authorized support, operational or security processing may require access to relevant records; we do not promise that staff can never access customer data.
Your business is responsible for the authority, notices and permissions needed to provide customer data, maintaining accurate information and granting appropriate access. Avoid unnecessary sensitive information, passwords or payment credentials in notes, imports and support messages.
Roles and account access
Owners administer their workspace. Managers have permitted operational access. Sales access is scoped to permitted records and actions. Viewers are read-only. Assignment, sharing and hierarchy settings also affect visibility.
Workspace administrators are responsible for assigning suitable access and reviewing it when responsibilities change. Removing a member’s access is not the same as deleting historical business records associated with that person.
Integrations and third-party services
Businesses may enable supported Google Ads, Meta Ads, WhatsApp, Email / SMTP and Website Form connections. Connected services can send or receive data necessary for configured features, such as captured lead information, advertising performance, source spend or communications.
Access depends on account permissions and configuration. Providers have their own privacy practices and terms. Disconnecting a provider does not necessarily remove previously imported records or communications. Review the relevant Help guide and provider controls before connecting or disconnecting an account.
Cookies and technical data
RevenueLancer uses authentication cookies to maintain sessions. Browser local storage supports interface preferences such as theme, sidebar state, table or column settings and support-widget state.
Browser settings can clear or limit cookies and local storage. This may sign you out, reset preferences or affect required functionality. RevenueLancer currently does not provide a separate cookie-consent or preference-management panel.
Requests may include network or country metadata used for abuse controls and regional pricing. Infrastructure may generate technical logs. This notice does not claim that a third-party marketing analytics system is installed.
Sharing with service providers
Hosting and infrastructure, database and authentication, transactional email and payment-processing services support RevenueLancer. Information relevant to a function may be processed by the provider supporting it. Businesses can separately authorize advertising and communication providers through integrations.
Contact submissions are stored and may be forwarded to the support mailbox through the configured mail transport. Payment information is exchanged as required to complete and reconcile transactions.
Information may also need to be disclosed under applicable legal requirements or to address security incidents, fraud or disputes.
Data retention
Retention depends on the record and its purpose. Information may remain necessary to provide an active workspace, maintain account and transaction history, investigate abuse, resolve disputes or meet applicable legal and accounting obligations. No single fixed period is stated for all records.
Archiving a lead, disconnecting an integration or removing a member does not automatically erase all related information. Self-service destructive account or workspace deletion is not currently enabled in Settings. Contact us to request deletion or closure; the scope and any records requiring retention need review.
A request does not mean every copy or service-provider record is removed immediately. We will explain the applicable process and limitations rather than promise an unsupported instant purge.
Security
RevenueLancer uses authentication, role-based permissions, business-scoped access controls and server-side handling of sensitive integration credentials to protect information. Businesses should secure accounts, review access and avoid sharing credentials.
No method of transmission or storage can be guaranteed completely secure. Contact support about suspected account or data-security issues.
Your rights and requests
Depending on your location and applicable law, you may be able to request access, correction or deletion of personal information, or restriction of or objection to certain processing. Rights and exceptions depend on the circumstances and applicable law.
Use our Contact page or support address below. We may need to verify your identity and workspace authority. If a business entered your information, that business may also need to handle or authorize the request. No universal deadline or unconditional deletion right is promised here.
International processing
RevenueLancer relies on externally hosted infrastructure and optional connected providers. Processing locations depend on those services and configuration and may differ from your location. We do not promise that all information stays in one country.
Contact us for information about processing locations and transfer arrangements relevant to your use of the service.
Children
RevenueLancer is a business service and is not intended for children. Do not submit children’s information without the authority and safeguards required by applicable law. Contact us if you believe such information has been submitted inappropriately.
Policy changes
We may revise this policy as the service and its practices change. The revision date appears above. Material changes may be communicated through appropriate website, account or other notices; no particular notification channel is guaranteed.
Contact us
RevenueLancer — operated by Nirdesh Kudeshiya. For privacy questions, data requests or formal notices where appropriate, use our Contact form at /contact or email support@revenuelancer.online. Include relevant context, but do not send passwords, access tokens or unnecessary sensitive customer information.
Contact support