Last updated: 6 September 2026
These draft terms describe the intended hosted RecurLens beta rules. The application currently links to them but does not record a versioned acceptance. If you self-host RecurLens, you are responsible for the terms that apply to your own users and deployment.
RecurLens helps individuals, freelancers, and small teams track recurring subscriptions, costs, renewal dates, owners, budgets, reminders, and CSV import/export data. RecurLens is a tracking and planning tool, not accounting, tax, procurement, legal, or financial advice.
The hosted service is an invite-only beta with free-tier infrastructure, possible cold starts, manual rather than continuous backup operations, and no production service-level guarantee. CSV export is not a complete account or recovery backup.
You are responsible for maintaining the confidentiality of your credentials and for activity under your account. You must provide accurate account information and keep your workspace membership and invite sharing limited to people authorized to view the relevant subscription data.
Hosted RecurLens accounts are limited to people aged 18 or older because supporting minors would require child/parental-consent practices that are not currently defined for the hosted service. If you self-host RecurLens, you are responsible for setting the age policy and any practices required for your deployment.
Workspace owners are responsible for managing member roles, revoking invites when needed, and confirming that shared data does not include confidential information that should not be placed in RecurLens.
Delete account requires password verification and is unavailable while an owned workspace has other members. Successful deletion leaves workspaces owned by others, soft-deletes owned workspaces and the local account, and attempts to delete the authentication account; retained and backup copies may remain under the operator's as-yet-unpublished schedule.
You may not use RecurLens to violate laws, infringe rights, upload malicious content, probe or bypass security controls, enumerate invite tokens, abuse rate limits, interfere with the service, or access workspaces without authorization.
We may suspend or terminate accounts, workspaces, or access that create security risk, operational harm, legal risk, or violate these terms.
You retain ownership of the subscription and workspace data you enter. You grant us the limited rights needed to host, process, back up, secure, display, export, and transmit that data as required to operate RecurLens.
You are responsible for ensuring that you have permission to upload or share any workspace, vendor, owner, note, or CSV data you add to the service.
Self-hosted operators are responsible for their own infrastructure, security, backups, user support, legal notices, and compliance. These hosted-service terms do not replace the terms that apply to an operator's own deployment.
RecurLens is provided on an as-is and as-available basis. We do not guarantee uninterrupted service, error-free operation, complete data recovery, reminder delivery, or that tracked spend totals will match invoices, exchange rates, accounting systems, or bank statements.
You should verify renewal dates, cancellation windows, budgets, invoices, and financial decisions independently before relying on them.
The intended limitation, subject to qualified legal review and applicable law, is that RecurLens maintainers and operators would not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, lost profits, lost savings, lost data, business interruption, missed cancellations, renewal charges, or unauthorized access caused by your invite sharing or credential handling.
The hosted RecurLens beta is operated by an individual based in Kurnool, Andhra Pradesh, India. These terms may change as the product and operating facts are finalized, and questions can be sent to recurlens@gmail.com. The operator's legal identity, governing-law decision, change-notice process, and final liability terms are not yet published, so these are not final service terms and are not launch-ready.
The operator should obtain qualified legal review before relying on these terms for the hosted service.