Privacy Policy

Roomdo. Updated 27 October 2026. Effective from version 3.2.1.

Roomdo is a visual planner. You can use it without an account. Your tasks, notes, photos and rooms then stay on your device and, if you turn iCloud on, in your own private iCloud. Three parts of Roomdo send data to us or to other companies: the optional Roomdo account with shared rooms, optional AI objects, and purchase processing and optional usage analytics. Each is described below.

In short

Your planner on your device and in iCloud

Task names, dates, reminders, notes, checklists, attached photos, room names and backgrounds, and generated objects are stored in the app’s protected storage on your device. If iCloud is on, they sync through your Apple account’s private iCloud database. We have no access to your iCloud data.

Roomdo account (optional)

You can sign in with Apple to keep your rooms on all your devices and to share rooms. Roomdo never asks Apple for your email. On the first sign-in it asks Apple for your name: you can edit it on Apple’s screen, and Apple shares it only that one time. Roomdo keeps only the first name. Our server receives and stores:

When you create an account, the tasks already on that device are copied into it. Signing in to an existing account opens that account’s rooms. Signing out brings back what the device had before you signed in. While you are signed in, the account’s rooms sync through our server, not through iCloud.

The copy and your name are encrypted at rest with AES-256-GCM. The key is kept on our server, because the server has to read your data in order to sync and merge it. That means this is not end-to-end encryption. Session tokens are stored only as hashes. Invitation codes are stored as hashes plus an encrypted copy, so each of your devices can show the same current link. We don’t browse your planner. Our admin tools show counts, token balances and the shared object library, not your tasks or names.

Shared rooms

With an account, you can share a single room: open the room’s settings, choose Shared access, then Invite. This creates a link that works for 7 days and lets up to 10 people join. New link turns off the earlier links straight away. Everyone in the room can see and change all of it: tasks, steps, notes, photos, objects, the name and the background. Your other rooms, purchases and tokens stay private.

The link opens a page on our server in Kazakhstan. The page only offers to open Roomdo or get it from the App Store; opening it doesn’t use up the invitation. If you send the link in a messenger, the messenger may load this page to show a preview.

Everyone in a shared room sees its member list. Members appear by the name they added in Roomdo, or as “Owner” or “Member 1”, “Member 2” and so on if they haven’t added one. Each member also gets a small picture: a colour with the first letter of the name, or an object. The app draws it from the random account identifier. No photos are used.

The owner can remove members or stop sharing, and any member can leave. Whatever was already downloaded to a device stays there as a private copy. Anything you added to someone else’s room stays in that room after you leave.

AI objects (optional)

Before your first request, the app asks your permission. Roomdo 3.0 asks again even if you agreed in an earlier version, because it now sends more than the task title. When you create an object, these are sent over HTTPS to our server in Kazakhstan:

If our library has no matching object, our server asks OpenAI to draw a new one. Notes, photos, checklists and your other tasks are never part of the request. The description and style are also saved with the task, so you can generate it again later.

Please keep names, addresses and other personal or sensitive details out of titles and descriptions you send. OpenAI processes requests under its privacy policy and API data controls.

Our server keeps the title and description only while the request is running. After it succeeds or fails, both are deleted from the job record. What remains is a keyed hash of the title, description and style, so a matching request can get existing artwork. Hashes are never published or shown as a list of your tasks.

Generated images go into a shared library. Other people who make the same request may receive them. The library never shares your task title, description, notes, photos or identity. We store a delivery history linked to an app-specific identifier, so we don’t send you the same variant twice and charge each request only once. Deleting a task doesn’t remove its image from the shared library.

Purchases and tokens

Apple processes payments, and we never receive card details. To grant and restore tokens, our server checks Apple-signed app and purchase transactions. It stores app-specific identifiers, transaction IDs, product and subscription status, token grants, the balance and spending history. We use these records to deliver purchases, restore balances, handle refunds and prevent duplicate charges or abuse. These records are tied to your App Store purchase, not to your Roomdo account. They contain neither your Apple account email nor your password.

Analytics and ad attribution

From version 3.2.1, usage analytics is on by default, without a separate prompt; you can turn it off at any time in Settings → Usage analytics. Turning it off does not limit planner, account, AI-object or purchase features; it stops new usage events and clears unsent events waiting on the device. It does not immediately delete events already received by our server; those expire under the retention limits below, and you can contact us to request deletion.

Roomdo usage analytics: unless you turn it off in Settings, the app sends limited usage events to our own HTTPS server in Kazakhstan. Events include predefined actions such as introduction steps, showing or closing the Plus offer, choosing a plan, purchase or restore outcomes, tasks and rooms being created or completed, notification choices, and whether an AI object succeeded or failed. Event details use permitted categories, bounded counts and yes/no flags, together with event time, app version and build, interface language, and a coarse installation-age category. From version 3.2.1 they also include: creating a shared-room invitation or joining a shared room, signing in to or deleting a Roomdo account, exporting data, the number of photos added to a task, changes of appearance and of moving overdue tasks to today, the iOS version and how long the app stayed open. Task titles, notes, room names, photos and account identifiers are never sent. They do not contain free-form diagnostic messages.

The app generates new random installation, session and event identifiers for this usage service. It does not reuse identifiers or import queued events from the former analytics client. Before storage, our server replaces the identifiers with keyed hashes. These are pseudonymous device-level identifiers: events from the same installation can be associated with one another. They are not IDFA or IDFV. The app does not send its RevenueCat identifier or Roomdo account identifier to this usage-event service, and usage events are not joined to purchase-customer or account identifiers.

What is never sent to this usage service: task titles, task or room identifiers, notes, checklist text, room names, member names, photos, generated images, AI prompts or descriptions, filenames, imported URLs, purchase transaction identifiers or anything you type. The separate account-sync and AI-object services continue to process the content needed for those optional features, as described above.

RevenueCat continues to process subscription status, purchases and Apple Ads attribution. It receives a random customer ID created by the app and purchase information. From version 3.2.1, the app no longer sends planner, introduction or Plus-offer usage markers to RevenueCat. Apple StoreKit and the existing purchase/token service remain responsible for granting and restoring purchases.

RevenueCat also sends purchase and subscription lifecycle notifications to our server. Our financial ledger keeps the product, event type and time, trial, renewal, cancellation and refund information, amounts and estimated proceeds. Customer, event and transaction identifiers are protected with keyed hashes; raw notification payloads and raw customer or transaction identifiers are not retained in that ledger. These financial records are separate from optional usage analytics. Turning usage analytics off does not turn off purchase processing or these financial notifications.

To tell installs from our Apple Ads campaigns apart from other installs, RevenueCat obtains a Standard AdServices attribution token from Apple and asks which campaign, if any, led to the install. The new Roomdo usage client does not collect or send advertising attribution tokens. Apple Ads attribution does not use IDFA and is not used to track you across other companies’ apps or websites.

Earlier app versions used a separate usage analytics service and sent some progress markers to RevenueCat. Updating stops those usage integrations in the app. This release does not import their historical data or queued events into the new optional usage stream. It does not itself delete data already collected by earlier versions; contact us about access or deletion.

Notifications and permissions

Reminders and other notifications are created on your device. Nothing is sent through a push server. You give notification permission when the app asks, and you can withdraw it in system settings. You pick photos with Apple’s system picker, so the app only sees the photos you choose. Saving an image to Photos asks for add-only access.

Who processes your data

Our server: Yandex Cloud, Kazakhstan

Roomdo accounts, member names, shared rooms and their invitation pages, AI object requests, the object library, token balances, purchase checks, optional usage analytics, financial records and this policy. Everything runs on one virtual machine in Yandex Cloud’s Kazakhstan region. Connections use HTTPS. Like any web server, ours sees your IP address when the app connects or a page opens. We don’t use it to identify or locate you. It is kept as a keyed hash for a few minutes to limit abuse, and it can appear in server error logs, which are rotated with up to 14 days of retained logs. Routine usage-event access logging is disabled; the usage database does not store raw network addresses.

Apple

iCloud sync, Sign in with Apple, App Store payments and Apple Ads attribution. See Apple’s privacy policy.

OpenAI: United States

Draws new object images from the title, description and style.

RevenueCat: United States

Subscription status and purchase analytics. See RevenueCat’s privacy policy.

These companies may process data outside your country, mainly in the United States.

How long we keep data

Your choices and deleting data

What we don’t do

Children

The app is not directed at children under 13 and does not knowingly collect any data about them.

Changes

If this policy changes, the new version will appear on this page.

Contact

Questions about privacy: saverinkz@yandex.ru