Privacy notice

Effective date: 14 October 2026. This is an operational disclosure, not legal advice or a claim of legal review, regulatory certification, or universal compliance.

Who is responsible

UB Nandakumar, operating in India ("we"), is responsible for the Roux website, the demo accounts, and the Roux hosted service, and for business inquiries. The organization that uses the hosted service decides what content its users upload and who may see it. Privacy questions and requests can be sent to ubnandakumar@gmail.com.

Information we handle

• Contact inquiries: name, email, organization if given, selected topic, message, consent, and the correspondence needed to respond.
• Website and service logs: request time, requested path, response status, source network address, user agent, and technical diagnostics needed to operate and protect the website and the hosted service. Logs are not designed to contain form content, passwords, session cookies, two-step verification codes, or tokens.
• Hosted service accounts: for each user, the organization, sign-in name, display name, and account status; the workspace roles, groups, row-security attributes, and administrator or publishing permissions an administrator assigns; a verifier for the password, never the password itself; a digest of any pending activation code; the two-step verification enrollment, sealed at rest; and digests of the unused recovery codes.
• Workspace content: the data users import, and the datasets, measures, charts, dashboards, comments, mention notifications, and publications they create, stored on the hosted server for the organization that uses it.
• Security and audit records: for each request to the hosted service, its time, network address, operation, outcome, and signed-in user, with the datasets and column names it touched but not their values; uploaded file names; for any SQL query, its text with literal values removed and a digest of the full text; for administrator actions, the target user and the names of the fields changed; a history of changes to workspace content, holding the items before and after each change, with bulk row data recorded as a count and a digest; and sign-in and account events. These records are append-only and kept on the hosted server; a copy of each request record also goes to the server's rotating service log.
• Demo sessions: the demo accounts listed on the application's sign-in page share public passwords and open a synthetic sample workspace. A demo session ends after 10 minutes, or after 5 minutes without activity, and nothing a demo account changes is saved. The sample workspace does not describe the visitor.

Sign-in and session data

The hosted service uses Roux native sign-in: an organization, a sign-in name, a password, and, for every account other than the demo accounts, a time-based code from an authenticator app. No third-party identity provider is involved, and no Google account data is received for sign-in.

A signed-in session is held in an opaque, host-only cookie marked Secure, HTTP-only, and SameSite=Lax, with the session state on the server. Sessions other than demo sessions end after 30 minutes without activity or after 12 hours at most, and signing out revokes a session on the server. The marketing website sets no cookie.

Why we use it

We use inquiry information to respond to feedback and to product, licensing, technical, partnership, or acquisition questions and to keep an accountable business record. We use hosted service account data to sign users in, apply two-step verification, and enforce each user's roles and row and column rules. We store and process workspace content only to provide the hosted service to the organization that uses it. We use logs and security and audit records to operate, secure, troubleshoot, and defend the Roux website, the demo accounts, and the Roux hosted service; to detect, investigate, and prevent misuse; and to give the organization a record of access and changes. We do not sell personal information or use it for behavioral advertising.

Service providers and disclosures

The visitor's email provider and our email provider process the message; the Roux website does not receive or store the form itself.

• Hostinger: provides the virtual private server, DNS, and domain services. The website and the hosted service, including account data, workspace content, audit records, and nightly backups, are stored on that server. In the backups, account records and sign-in secrets, such as password verifiers and two-step verification keys, are encrypted so that only a key we hold offline can decrypt them. Backups are not copied off the server; if that changes, this notice will name the location.
• Google: provides the contact mailbox. Google receives email according to the visitor's chosen action and Google's own terms, and receives no sign-in request from Roux.
• Let's Encrypt: provides the public TLS certificate and processes the domain-validation and certificate information needed to issue and renew it.

We disclose personal information only to these service providers as needed to operate the service, when you ask us to share it, when required by law, or when necessary to protect rights and service security. Each provider's processing is governed by its own terms, privacy notice, locations, security controls, and retention practices.

Retention

Inquiry information is kept only as long as reasonably needed to respond, keep necessary business records, protect the service, resolve a dispute, or meet a legal or contractual obligation. Web server access logs rotate daily, and up to 14 rotated files are kept; the elapsed period can vary when a rotation is empty or missed. Security and audit records are kept up to a configured storage limit and are then archived or deleted by us. The service log rotates by size and keeps up to 5 files of 20 MB each. Sessions end as described above.

Workspace content is kept until it is deleted. Deleted items stay in Trash for at least 30 days by default and are then removed from the live service. Copies can remain in the history of changes, which is kept with the security and audit records; in the daily in-app snapshots, of which 7 are kept; and in nightly backups until those are replaced under our backup retention settings. This notice does not promise one fixed deletion period for every record type.

Responsibility boundary

This notice covers the Roux website, the demo accounts, and the Roux hosted service, operated by UB Nandakumar, including the hosted service's accounts, workspace content, and security and audit records. Where a customer runs Roux on its own infrastructure, the customer and its appointed operators determine the data loaded into Roux and remain responsible for lawful collection and use, user administration, infrastructure configuration, retention, backups, notices, and intended-use validation unless a signed agreement assigns a responsibility differently. Infrastructure, DNS, certificate, and email providers remain responsible for their own services under their terms.

Your choices, requests, and complaints

You may choose not to submit the form and may contact us directly. Depending on applicable law and context, you may ask about, correct, delete, restrict, or obtain a copy of information associated with you, object to certain use, withdraw a consent-based request, or raise a complaint by emailing ubnandakumar@gmail.com. Users of the hosted service may also ask their organization's administrator to correct or remove their account. We verify a request proportionately before acting.

International use and safeguards

Internet and service providers may process information outside your location under their applicable terms and safeguards. This notice does not claim a transfer mechanism, data-processing agreement, or provider location that has not been established for the service.

Changes

If this notice changes materially, the revised notice is published here with an updated effective date.