Privacy Policy

This Privacy Policy explains how Keelstone Financial (“Keelstone”, “we”, “us”) would handle personal information across this website and the associated demo dashboard. Because Keelstone is a fictional company and this is a demonstration application, the policy is sample text written to mirror how a real financial-operations platform documents its practices.

Do not submit real personal or financial data through this site. Use placeholder values. Anything you do enter is handled as described in the Data retention section below.

In the course of running this demo, the application may receive:

• Information you provide. Form submissions such as the contact, demo-request, newsletter, and job-application forms, plus any invoices or payments you create inside the dashboard.
• Account and session data. When you sign in with the demo credentials, we create a short-lived session identified by a cookie. See our Cookie Policy.
• Technical request data. Standard information your browser sends with each request, used only to serve the page.

The demo does not ask for and does not knowingly process real government identifiers, bank account numbers, card numbers, or other sensitive financial information.

Information submitted to the demo is used solely to make the demo function — for example, to display an invoice you just created, to return a confirmation reference, or to keep you signed in while you explore the dashboard. We do not use it for advertising, profiling, or automated decision-making, and we do not sell it.

Where the EU General Data Protection Regulation applies, a real operator would rely on legal bases such as performance of a contract, legitimate interests, consent, and compliance with legal obligations. As a fictional demo, Keelstone asserts no such bases and undertakes no processing beyond the in-memory handling described here.

This site uses a single strictly-necessary cookie to maintain your signed-in session in the demo dashboard. It does not use analytics, advertising, or cross-site tracking cookies. Full details are in the Cookie Policy.

We do not share demo data with third parties. There are no advertising networks, data brokers, or analytics processors connected to this application. A real platform would disclose any sub-processors, regulators, and circumstances such as corporate transactions here.

This is the important part. Information you submit through the demo — form entries, sessions, and any invoices or payments you create — is held only in the server’s volatile memory. It is not written to a database and is permanently discarded whenever the demo server restarts. We do not back it up, export it, or reuse it for any purpose beyond making the demo work during your visit.

The demo follows reasonable web hygiene (for example, session cookies are HTTP-only). However, it is an illustrative application and should not be treated as a secure system of record. Never store real or sensitive information in it.

Depending on where you live, privacy laws such as the GDPR and the California Consumer Privacy Act grant rights to access, correct, delete, port, or restrict the processing of your personal information, and to object or withdraw consent.

In this demo those rights are effectively automatic: because data lives only in memory and is erased on restart, no durable record of you is retained. There is nothing for us to sell, and nothing to delete beyond the current session.

A real operator would describe safeguards (such as standard contractual clauses) for transferring data across borders. This demo performs no such transfers; data does not leave the process serving the page.

Keelstone is a business-to-business demo and is not directed to children. We do not knowingly collect information from anyone under 16.

We may update this sample policy as the demo evolves. The “last updated” date at the top reflects the most recent revision. Material changes to a real policy would be communicated to affected users.

Questions about this policy can be sent through our contact form. In a real deployment, a privacy team at privacy@keelstone.example would respond; here, your message is simply recorded in memory.