Legal

Privacy Policy

The privacy practices governing Janomate. Ops software for cleaning contractors — dispatch, QA, invoicing, and renewals in one place. This is a placeholder document covering the standard sections of a consumer-facing Privacy Policy.

1. Privacy at a glance

Placeholder — the policy overview belongs here. Replace with the finalized opening paragraph that sets the scope of Janomateʼs privacy commitments: which entity acts as the data controller (typically the operating company), what this policy covers (the website, the dashboard, the mobile apps, and any sub-products), and what it does not cover (third-party sites linked from the service, sub-processors that publish their own policies). State at a high level what categories of data Janomate collects, why, and that the full details are expanded in the sections below.

2. Data we collect

Placeholder — the data collection clause belongs here. Replace with finalized language itemizing each category of data Janomate collects, with the lawful basis for doing so. Cover the standard categories: account data (name, email, phone, role), billing data (handled by Stripe — never store a full card number), operational data (facility addresses, cleaner rosters, job records), content the user uploads (QA photos, checklist notes, signed invoices), device and log data (IP, user agent, timestamps), and any data collected passively through cookies or analytics. For each, give the purpose and the retention window.

3. How we use your data

Placeholder — the data-use clause belongs here. Replace with finalized language linking each category of data to the specific purposes for which Janomate processes it: operating and securing the service, matching contractors to jobs, processing payments, sending transactional and product emails, improving the service through aggregated analytics, and meeting legal obligations. Make it explicit that Janomate does not sell user data, does not use it for advertising profiling, and does not train third-party AI models on it without consent. Call out any automated decision-making (e.g. dispatch routing) and the userʼs right to a human review.

4. Third-party sharing & sub-processors

Placeholder — the third-party sharing clause belongs here. Replace with finalized language describing each category of recipient that may receive user data: cloud hosting and infrastructure (e.g. the database and object storage providers), authentication vendors, the payment processor (Stripe — call out that they receive billing data only), email delivery, observability and error reporting, and any analytics vendor. For each, name the category, the data shared, the purpose, and link to the recipientʼs own privacy policy. State that Janomate maintains a current sub-processor list and will notify users of material changes per the policy below.

5. Cookies & analytics

Placeholder — the cookies clause belongs here. Replace with finalized language describing each cookie or analogous storage Janomate sets, grouped by purpose: strictly necessary (session, security), preferences (theme, locale), and analytics (aggregated, privacy-respecting — never cross-site advertising). For each, state the name, the purpose, the duration, and whether a user can refuse it. If Janomate uses a banner or consent management platform, describe how the user updates their choices. Confirm that no advertising cookies are set and that no user data is shared with ad networks.

6. Data retention & your rights

Placeholder — the retention and rights clause belongs here. Replace with finalized language stating how long Janomate retains each category of data (commonly: account data for the life of the account plus a defined tail for tax and legal reasons; operational data per a retention schedule; backups on a rolling window). Itemize the rights available to the user under applicable law — access, correction, deletion, portability, restriction of processing, objection, and the right to lodge a complaint with a supervisory authority — along with how to exercise them and the response window Janomate commits to.

7. Children's privacy

Placeholder — the children's privacy clause belongs here. Replace with a brief statement that Janomate is not directed to children under 13 (or the higher age defined by your jurisdiction, commonly 16 in the EU), that Janomate does not knowingly collect personal data from children, and that a parent or guardian who believes a child has provided data should contact Janomate at the address below so the data can be deleted.

8. Updates to this policy

Placeholder — the policy-change clause belongs here. Replace with finalized language describing how Janomate will notify users of material changes to this Privacy Policy (commonly by email and an in-app banner, with a stated minimum notice window — 30 days is typical), where the prior versions of the policy will be kept so users can compare versions, what happens to users who continue to use the service after the effective date, and that the Terms of Serviceʼs change-notice provisions apply where they conflict.

9. Contact

Placeholder — the privacy contact clause belongs here. Replace with finalized language naming the contact email for any privacy questions, data-subject requests, or notices relating to this policy. Include the registered legal name of the operating entity, the data-protection officer (or equivalent) where applicable, and the contact address for service of legal process where required. Direct requests to exercise user rights to the same address; state the response window and what information Janomate needs to verify the requester.

Last updated:

Questions about this policy? Email janomate@polsia.app.