Privacy Policy

ROBA OS · Draft stub · Last updated 2026-10-07 (JST) · Not counsel-reviewed

1. Who we are

iudot Inc. provides ROBA OS. This Policy covers marketing / waitlist pages, Hosted accounts, and sales / support / billing contacts for Private.

2. Scope

B2B company-works software. Not a consumer social network or counseling service. Private VPS deployments process most Customer Content on Customer-controlled infrastructure; this Policy still covers sales, support, and billing data you give us.

3. Information we collect

• Account: name, email, password (hashed), workspace name, role, invites.
• Customer Content (Hosted): tasks, logs, inbox items, references, peer remarks, files, and similar.
• Payment: card/tax details typically collected by Paddle (planned MoR); we receive limited billing metadata, not full card numbers.
• Technical: IP, user-agent, timestamps, feature use, error logs; session cookie (HttpOnly, SameSite=Lax, Secure on HTTPS).
• Optional AI assist (if enabled later): prompts and page context sent to a model provider — off by default on day-one Hosted unless we turn it on and name the subprocessor here.

4. How we use it

Provide and secure the Service; authenticate and enforce roles; process payments; support; comply with law; aggregated product improvement. We do not sell personal information. We do not use Customer Content to train public foundation models for unrelated third parties as a product feature of early-access ROBA OS.

5. Sharing

Paddle / payment processors; infrastructure and email vendors under contract; advisors under confidentiality; authorities when required; a successor in a corporate transaction with notice where required. Workspace members see content by role.

6. International transfers

iudot is organized in Labuan, Malaysia. Hosting and vendors may process in other countries. Hosting region for production Hosted: [TBD when locked].

7. Retention

Account and Customer Content while the workspace is active, then a commercially reasonable deletion window (unless law or backups require longer). Billing records as required for tax. Security logs for a limited operational period. Remote chat server logs (if that feature is on): about 180 days, no secrets.

8. Security

Reasonable measures for early-access B2B software (access control, hashed passwords, isolated data roots). No method is 100% secure. Customer must not upload regulated counseling / clinical content the Service is not designed to hold.

9. Your choices

Access, correction, deletion, or export requests: email support@iudot.co. Workspace Owners control much of Customer Content in-product. Early access may fulfill some requests manually.

10. Children

Not directed to children under 16 (or higher age required locally).

11. Changes / contact

We may update this Policy for early access. Material changes posted on the site or sent to Owners. Continued use after the effective date constitutes acceptance where permitted.