This policy explains how RunwayCal Technologies Pvt. Ltd. ("RunwayCal", "we", "us", or "our") handles personal information when people visit our website, use the RunwayCal application, contact us, or interact with related services.
1. Operator and scope
RunwayCal Technologies Pvt. Ltd. operates the RunwayCal website and application. This policy covers information handled through those services, product support, product and partnership enquiries, and related service communications.
It does not replace the privacy terms of a connected provider, a third-party website, or the organization that invited you to a RunwayCal workspace. Those parties may make their own decisions about how they use information.
2. Information we handle
Account, workspace, and business information
This may include your name, work email address, organization or company details, access role, account and workspace settings, authentication and session information, and information needed to provide or administer your account.
Financial and planning information
Depending on the features you use, RunwayCal may handle information about cash, Treasury accounts, revenue and receipts, deals and collections, teams and payroll inputs, tools and other costs, commitments, budgets, scenarios, tax obligations, locations, planning assumptions, and calculated outputs. Recorded, planned, expected, and hypothetical information can have different meanings inside the product.
Uploads, imports, and source records
We handle supported files and structured imports you choose to provide, together with file metadata, validation results, suggested mappings, source identifiers, and the records you approve. The supported workflow and retained context depend on the import method.
Billing and subscription information
Payment details are processed by the payment provider. RunwayCal receives subscription, plan, entitlement, transaction status, and related billing metadata needed to administer access and answer billing questions. We do not need the full card number to manage a workspace subscription.
Communications and enquiries
If you contact support, request a demo, subscribe to updates, apply to become a partner, or send another enquiry, we handle the contact details, message, form fields, and correspondence you provide.
3. Uploads and AI-assisted extraction
When a supported AI-assisted upload feature is used, RunwayCal can process the document to suggest structured financial items. A suggested extraction does not become an approved financial record until the user reviews and approves it. The source file, extracted fields, review state, and resulting record may be handled separately.
This policy does not make a universal promise that customer data is used to train general-purpose models or that it is never used for that purpose. The applicable processor arrangements and product terms determine that boundary. Contact us if you need the terms that apply to a particular workspace or processing path.
4. Integrations and connected providers
If you connect a supported provider, RunwayCal handles the authorization or connection details, tokens where applicable, connection health, provider identifiers, and supported provider data needed for that connection. OAuth, API-key, webhook, refresh, import, review, approval, and notification behavior varies by provider.
Some connections read supported records and wait for a user to approve what enters RunwayCal. Others handle events, balances, or notifications within a narrower documented boundary. Connecting one provider does not establish a universal bank feed, automatic reconciliation, or write-back to every external system. You can review current provider-specific behavior on the Integrations and documentation pages.
5. Technical data, cookies, and analytics
When the website or application is used, our infrastructure may receive technical information such as IP address, browser and device type, requested route, date and time, session or security identifiers, referrer, diagnostic events, and error or service logs. The exact data depends on the service surface and request.
Browser storage and cookies may be used for authentication, session continuity, security, preferences, and other service operation. The current website is configured with Vercel Analytics to understand aggregate usage and performance. Newsletter subscription requests use Resend when that delivery service is configured. These services receive only the information required for their role and operate under their own terms as service providers.
6. How information is used
We use information where needed to:
- provide the website, application, and financial planning features you choose to use;
- create, authenticate, administer, and secure accounts and workspaces;
- process requested uploads, imports, calculations, integrations, reports, and exports;
- manage plan access, subscription status, billing administration, and service communications;
- respond to support, product, partnership, privacy, and security enquiries;
- detect misuse, investigate errors, maintain reliability, and protect the service; and
- understand and improve service usability and performance in a measured way.
RunwayCal does not use an expected receipt or hypothetical scenario as proof that money has been received. Product calculations and approvals follow their documented financial and workflow boundaries.
7. Legal bases where applicable
Where data-protection law requires a legal basis, the basis depends on the context. It may include:
- Contract: to provide a requested account, workspace, subscription, support interaction, or other service.
- Legitimate interests: to operate, secure, troubleshoot, and improve the service, communicate with business users, and protect legal rights, balanced against the rights of the individual.
- Consent: where we ask for a choice, such as an optional communication or connection that relies on consent.
- Legal obligation: where records or disclosures are required by applicable law.
These descriptions do not claim that one privacy law applies to every user or that RunwayCal is certified under a particular legal regime.
9. International processing
RunwayCal and its service providers may process information in countries other than the country where a user or customer is located. Privacy and data-protection rules can differ between those places. Where applicable law requires a transfer safeguard, RunwayCal uses the mechanism appropriate to the relevant provider relationship and processing context. This policy does not promise a single data-residency location for every service.
10. Retention, account closure, and deletion
We retain information for as long as reasonably needed to provide the service, maintain an active workspace, meet the purpose for which it was collected, support security and dispute handling, and satisfy applicable legal or accounting requirements. Different categories can require different periods; this policy does not promise one universal schedule.
A user or customer may request account closure or deletion. We will assess the request against workspace authority, backups, security needs, legal obligations, and records we must retain. Deletion from an active interface may not remove every protected backup or legally required record immediately.
11. Security
RunwayCal uses technical and organizational measures intended to protect the confidentiality, integrity, and availability of the service and the information it handles. Measures are reviewed in the context of the system and the risks involved. No online service can guarantee absolute security.
This policy does not claim SOC 2, ISO 27001, penetration-testing schedules, zero-trust certification, a particular residency regime, or controls that have not been independently verified. Current public security information is available on the Security page.
12. Your rights and communication choices
Where applicable under the law that applies to you, you may have rights to request access, correction, deletion, export or portability, restriction, or objection; to withdraw consent where processing relies on consent; and to complain to an appropriate data-protection authority. Rights can depend on jurisdiction, the nature of the information, and whether RunwayCal or a customer organization controls the relevant use.
We may need to verify identity and authority before completing a request. Service and security communications may still be necessary for an active account. Optional marketing email should provide an unsubscribe route, or you can ask us to stop sending it.
13. Business workspaces and customer roles
A business customer decides who may use its workspace and what business information its users add. Depending on the context, RunwayCal may decide how information is used for its own website, account administration, security, and service operations, or process workspace information to provide the service requested by the customer organization.
If you use RunwayCal through an employer, client, or other organization, that organization may be the best first contact for a request about its workspace records, access decisions, or instructions to RunwayCal.
14. Children, connected services, and external links
RunwayCal is a business financial planning service and is not designed or directed for use by children. If you believe a child has provided personal information through the service, contact us so the situation can be assessed under the applicable law.
Connected providers, payment services, and external websites have their own privacy practices. Following a link or authorizing a provider means that party may receive information directly from you or from RunwayCal within the scope you approve. Review the third party's terms and privacy information before using it.
15. Changes to this policy and contact
We may update this policy when the service, processing practices, or legal requirements change. The date at the top shows the latest update. When a change is material, we may provide an additional notice through the website, application, or an appropriate communication channel.
For a privacy question or request, email support@runwaycal.com. Please do not send passwords, full payment-card details, or unnecessary sensitive information by email.
No registered office address, data-protection officer, or regional representative is published in this policy because those details have not been verified for this release.