Privacy
Last updated 16 November 2026
ROLENGINE is a small app for team chat, tasks, time and calls. This page says what it keeps about you, why, and for how long. Questions: hello@rolengine.com.
ROLENGINE is run by ROLENGINE LLC, 5900 Balcones Drive STE 100, Austin, TX 78731, USA.
What we keep
- Your email address and the name you give. The address is how you sign in; the name is what your teammates see.
- Your workspaces. Which workspaces you belong to, what you are in each (owner, admin, manager or member), and the email addresses you invite.
- Channels and chats. The names the people in a workspace give its channels, and the chats inside its projects. A channel of the workspace stays until the workspace's owner or one of its admins deletes it, with every message in it, or the workspace is deleted. A project's chat is deleted the same way by whoever runs that project. Whoever runs a project can also say how much chat it has: its own chats and a chat for each task, a chat for each task only, or none. That only hides: what was written in a chat or a task that is hidden is kept exactly as it was, with what each person had read in it, and shown again when the project's chat is switched back on. A personal space has no chat. Chats made in a personal project before it had none are kept, shown nowhere, and deleted with that project; in the one personal project that stays, they stay until its person leaves the workspace (below).
- Projects and tasks. The names the people in a workspace give its projects, and its tasks: each task's title, the short code the team gives it, its notes, the line that says where its files are, how far along it is, whose it is, whether it is marked as mattering more, where it stands on the board, who made it and when, when it was completed, and when it was archived. A task can hold steps, a checklist that is part of the task: each step's title, how far along it is, whose it is and where it stands in the list. A project can have steps for new tasks, which every new task made in it gets: their titles, whose each is and their order. They are kept the same way as messages. A task stays until someone who can open its project deletes it, or the workspace is deleted. Deleting a task deletes its conversation: every message written in it, for everyone, and its notes, its steps, its code and the line about its files with it. Anyone who can open its project can also delete one of its steps. A project's steps for new tasks are changed and deleted by whoever runs the project, and deleted with it. Archiving a task deletes nothing. A task is archived when someone who can open its project archives it, or by itself once it has been marked completed for seven days (for a workspace whose data we brought in from another system the number of days can be another). An archived task is off the boards and kept exactly as it was, with its conversation, its notes, its steps and what each person had read in it. Everyone who can open its project can still open it, put it back or delete it. Until it is put back nobody can change it or write in it, and its conversation is not shown: to read what was said in it, or to delete a message of yours in it, put it back first. A shared project stays until the workspace's owner or one of its admins deletes it (or a manager, if the owner or an admin has let managers run projects), which they can do only once no task and no chat is left in it. If you leave a workspace, are removed from it or delete your account, the tasks and steps that were yours in shared projects stay, and stay marked as yours.
- Your personal space. Each person has one private task space in a workspace, made the first time they open it, and only you can open yours from the app. Nobody else in the workspace, not its admins and not its owner, can open it, read what is in it, or see that it exists. It is kept the same way as everything else in the workspace. It has tasks and no chat. What you wrote in the conversation of a task there before it had none is kept, shown nowhere, and deleted with that task. If you made several personal projects before there was a personal space, you keep them all, and you can delete all but one of them once they hold no task: one you delete takes with it the chats made in it before, and every message in those. When you leave the workspace, are removed from it or delete your account, your personal projects are deleted with everything in them: their tasks with their notes, steps and conversations, their steps for new tasks, their chats and every message in those. If that step fails at that moment, it is done the next time anyone does anything in the workspace, and in any case before you can join it again. For 30 days after that they can still be found in the recovery history Cloudflare keeps of each workspace's database (see Your messages).
- Your messages. What you write in a workspace is kept, as you wrote it, so the people in it can read it, together with your name and the time. Kept with each message are the people it names, if any, and who reacted to it with which emoji, and when its reactions last changed; everyone who can read the message sees them. A message stays until you delete it, the workspace's owner or one of its admins deletes it (never in a direct chat), its channel or chat is deleted, someone deletes the task it was written in, the person whose personal project it is in leaves the workspace or deletes that project, or the workspace is deleted. A project whose chat is switched off keeps its messages, hidden. Deleting a message removes it for everyone, with whom it named and the reactions to it. For 30 days after that it can still be found in the recovery history Cloudflare keeps of each workspace's database, which exists to repair faults; then it is gone for good. If you leave a workspace, are removed from it or delete your account, the messages you wrote there stay, and so do your reactions and the messages that name you: delete your messages first if you want them gone.
- Pictures in your messages. A message can carry up to four pictures. Before a picture leaves your Mac, the app's page draws it again, at most 2048 pixels on a side: so what a camera writes into a photo, the place it was taken among the rest, is not sent through this app's page. Kept with each picture are its file's name, its size, who sent it, where and when. Whoever can read the message can see its pictures; nobody else can fetch them. A picture is kept until its message is deleted, by you or by whoever may delete it (the same people as for the message, above), until the place it is in is deleted, or until the workspace is; then nobody can fetch it any more, and the picture itself is removed from our storage soon after: usually right after, and otherwise as people go on using that workspace, 25 pictures each time anyone does anything in it. Pictures stay on your Mac until you send their message; one that left with a message that then did not arrive is removed the same way once a day has passed, or sooner, once twenty newer ones of yours are waiting the same way. Editing a message changes its words only. A picture that someone has already looked at can stay in their browser's own cache, on their computer, after they lose access to the place it is in. A workspace holds at most 100 GB of pictures.
- A task's cover and a project's logo. A task can have one picture, its cover, and a shared project one, its logo. They are drawn again on your Mac before they are sent, as a picture in a message is (a cover at most 1280 pixels on a side, a logo at most 256), and the address they are sent to names the task or the project, never a file. Kept with each are its size, who set it and when it was sent. They are content of the workspace, kept the same way as its pictures: a task's cover can be seen by whoever can open the task, a logo by whoever can open the project. A cover or a logo is kept until someone who may change it replaces or removes it, until its task or project is deleted, or until the workspace is; then nobody can fetch it any more, and the picture itself is removed from our storage soon after, the same way as a picture in a message: usually right after, and otherwise as people go on using that workspace. One that was sent and never set (the page was closed in between) is removed once a day has passed. A cover or a logo that someone has already looked at can stay in their browser's own cache, on their computer, after it is replaced or removed, or after they lose access to its task or project. They count towards the workspace's 100 GB.
- Your photo. You can give your account one photo, which you choose and remove yourself; nobody else can set or remove it. Before it leaves your Mac it is cut to the square in its middle and drawn again at 256 by 256 pixels, so what a camera writes into a photo is not sent through this app's page. It is kept with your account, in the database of accounts, with the time you set it. It is shown only to the people in the workspaces you are in, while you and they are both members; once you leave a workspace, its people see your initial again. It is deleted when you remove it, and with your account when you delete it. Once you remove it, the time you last set one stays with your account, so that a new photo has a new address. Replacing it deletes the one before. A photo of yours that someone has already looked at can stay in their browser's own cache, on their computer, after you replace or remove it, or after one of you leaves the workspace. How often you changed it in the last hour is counted, as a change of name is.
- Your name, after you leave. When you leave a workspace or are removed from it, the name you had that day is kept for that workspace, so what you wrote there still says who wrote it, and a task or a step that was yours still says whose it was. Your email address is not kept with it. The name is erased when you join that workspace again, when the workspace is deleted, and in every workspace at once when you delete your account, however long ago you left. From then on your messages there are shown as from a former member, and the tasks and steps that were yours as a former member's.
- Your direct messages. A direct chat is between you and one other person in the workspace, and is kept the same way as any other message. Nobody can delete a direct chat as a whole: each of you can delete your own messages in it, and it is erased when the workspace is deleted. If you leave the workspace, are removed from it or delete your account, the other person can still read the conversation, under the name kept of you or, once your account is deleted, as from a former member, but can no longer write in it. If you join the same workspace again with the same account, it is the same conversation.
- Parts that are switched off. ROLENGINE is built in parts, and the owner and the admins of a workspace can switch a part off for their team and on again. Which parts are off is kept with the workspace. Switching a part off hides it from everyone in the workspace and deletes nothing: what it held is kept exactly as it was and is there again when the part is switched back on. Until then nobody in the workspace can read, write, change or delete anything in it, their own messages included. It is erased when the workspace is, whether the part is on or off. There are three parts. Chat is the workspace's channels and the direct chats. Work is the projects and the tasks, with the chats inside each project and the conversation inside each task: while Work is off, the projects, the tasks and everything written in them are hidden and kept, and while Chat is off the conversations inside projects go on. Calls is voice calls in the places people write in, and keeps nothing (below). Chat or Work always stays on.
- What you have read. For each channel, direct chat, chat and task, the number of the last message you have seen, so the app can show what is new to you on any Mac. It is removed when you leave the workspace or delete your account; if that step fails, it stays until the workspace itself is deleted.
- When you were last there. While you have a workspace open, the others in it see that you are there. When you close it, the time is kept so they can see when you were last there: one time per workspace, replaced each time. It is removed when you leave the workspace or delete your account; if that step fails, it stays until the workspace itself is deleted.
- Your time. While a workspace has Time switched on: each stretch you time, with what it was on (a task, an activity such as Administration, a paid break or a call), when it began and when it ended, and, when it stopped by itself, why (a break that ran out, a call that dropped, or, only where the workspace has switched that on, because you were gone). Once an entry's end has been moved, by you or by someone who may correct time, we keep who moved it last, when, and the end it had before. Time is the workspace's record of work: your entries stay when you leave the workspace, are removed from it or delete your account, marked as a former member's, until the workspace is deleted.
- Your rate. If the workspace's owner or an admin gives you an hourly rate: the rate and its currency, and, with each stretch of time, the rate you had when it began. What your hours earn is worked out from those. It is an estimate: nobody is paid through ROLENGINE, and these figures are not a contract or a legal record. Your rate is removed when you leave the workspace; the rate kept with time already worked stays with it.
- Activity while a timer ran. Only where a workspace brought its history from the app its team used before: for each stretch of time brought, which seconds that app's Mac app was watching and in which of them a key or the mouse was used, kept as counts. Never which keys, what was typed, where the pointer was or which app was in front: none of that was ever recorded. ROLENGINE itself does not measure this.
- Calls. Nothing said or shown in a call is kept. Sound and pictures go between the Macs of the people in the call, straight where a path can be found and otherwise through a relay that passes them on without keeping them. We keep one line in the conversation saying that a call started, without a name, and, while Time is on, the time you were in it, as time on "Call".
- A sign-in record. One cookie that keeps you signed in while you use the app and for up to 30 days after your last visit, and a second one that lasts ten minutes while you type a sign-in code. Neither is used for advertising or tracking.
- Counters against abuse. How many sign-in codes and invitations were requested for an address, by an account, and from a network (an IP address, its range or its internet provider) in the last hour or day, how many requests an account made inside its workspaces in the last minute, and how often an account changed its name and its photo in the last hour. They are deleted within two days.
- A check that you are a person. When you ask for a sign-in code, Cloudflare Turnstile may look at signals from your browser to tell people from programs. It is not used for advertising.
- Server logs. Cloudflare records each request to the app (time, the address requested, your IP address, approximate location and browser) so faults can be found. These logs are deleted after at most 7 days.
A message you have started writing is kept in your browser, on your Mac, until you send it, sign out, or your sign-in runs out. It is not sent to us before you send it. The same goes for what you have changed in a task's notes and not saved yet: it is kept in your browser until it is saved, until you take the saved notes in its place, or until you sign out or your sign-in runs out. Your browser also keeps which view you last used for each project and which teammate you last opened in Private chat, so the app opens where you were; both are emptied when you sign out or your sign-in runs out.
Calls are not recorded, and nothing of a call is kept: not what is said, not who was in it, not when. While a call is going on, everyone who can open the place it is in sees who is in it and whether each one's microphone is on; a call in a direct chat is seen by its two people only. The sound goes straight between the computers of the people in the call, so each one's app learns the others' network addresses (IP addresses) to reach them. When no direct path exists between two of them, the sound can go through Cloudflare's relay instead, which passes it on as it is: call sound is always encrypted between the computers, so the relay cannot listen. To find those paths, your app tells our server, and through it the others in the call, the network addresses it can be reached at, for as long as the call lasts; they are passed on and never kept. Who is speaking is worked out on each computer from the sound it receives, and never sent. The app uses your microphone only while you are in a call, and only once you have allowed it; you can mute it at any time.
In the Mac app, a direct message a teammate sends you, and a message anywhere else that names you, while you are not looking at that conversation, is shown as a notification by macOS, with their name (and, for a message that names you, where it was written) and the start of the message, the people it names written by their names. It stays on your Mac, in Notification Centre, until you clear it or a newer one about the same conversation takes its place. macOS asks you first whether the app may show notifications at all, and you can switch them off in System Settings.
There are no passwords, no advertising, no analytics trackers, and nothing is sold or shared for marketing.
Emails we send
Two kinds, both from hello@rolengine.com: a sign-in code when an address is typed on the sign-in page, and an invitation when the owner or an admin of a workspace invites an address. An invitation changes nothing unless the invited person signs in and accepts it. If you received an email you did not expect, you can ignore it. One address is sent at most three invitations a day; to stop invitations to your address altogether, write to us and we will block them.
Who can see what
People in a workspace see the names, email addresses and photos of the others in it, what each is there (owner, admin, manager or member), who has it open right now, and when the others last did. They also see the names kept of people who left it. Everyone in a workspace can read every channel of the workspace and every message in it, and see every project shared with the whole team and everything in it: its tasks, archived ones too, with their conversations, notes, steps, codes and the lines about their files, its steps for new tasks, and its chats, including what was written before they joined. A project shared with chosen people, and everything in it, can be seen by the people on its list, by the workspace's owner and admins, and by its managers if the owner or an admin has let managers run projects; the others cannot open it and are shown nothing of it: not its name, not its tasks, not who is on its list. They can work out that such projects exist and how many tasks they hold together, because those tasks count towards the 2,000 a workspace's shared projects hold. A personal space, and everything in it, can be seen by its person and by nobody else in the workspace. Who is on the list of a project shared with chosen people can be seen by everyone who can see the project. A direct chat can be read by its two people and by nobody else in the workspace, not even its owner; the others cannot see that it exists. Nobody else in the workspace can see what you have read. Who is in a call can be seen by everyone who can open the place it is in (above). The owner and the admins also see the addresses that are invited, and they decide which parts of the app are switched on; everyone in the workspace can see which are. Nobody outside a workspace can see that it exists, except the addresses invited to it: they see its name and the email address of whoever invited them. While Time is on, everyone in a workspace sees whether your timer is running and what it is on: a task where they can open it and otherwise only that it is private, an activity, a break or a call by its name. They do not see when you started or how long you have worked. Your hours are seen by you, by the workspace's owner and its admins, and by its managers only where the owner or an admin has let them; whoever sees your time also sees how an entry ended and who moved its end, and, where activity was brought with the time, how much of it had the keyboard or the mouse in use. The owner and the admins, and managers where they have been let, can move the end of your entries, and you are shown that they did and what it was before. Your rate and what your hours earn are seen by you, the owner and the admins, and by managers only where they have been let; the owner or an admin can switch rates and earnings off for everyone.
Where it is stored
The app and its databases run on Cloudflare, which also delivers the emails. Cloudflare processes the data on our behalf. Messages are kept there as text, direct messages included, and so is everything in a project shared with chosen people or a personal space, and what a project's level of chat hides. The pictures in messages, the covers of tasks and the logos of projects are kept there as files, in a store of their own beside the workspace's database; a person's photo is kept in the database of accounts, with their account. None of it is encrypted end to end, so we, who run the service, are technically able to read it. Who can open what is a rule of the app, not a lock we cannot open.
Deleting your data
"Delete account" at the bottom of your workspaces page removes your account, your photo, your memberships, the workspaces you own, the invitations you sent and the name kept of you in any workspace you had left, at once. What a deleted workspace held, its messages included, is erased with it, normally within seconds; if that fails, the app tries again every hour until it is done. Its pictures, covers and logos go the same way: a few thousand at once, and a workspace that holds more over some hours. The recovery history Cloudflare keeps of a workspace's database, and of the database of accounts, runs out within 30 days. Pictures, covers and logos are not in that history: once removed from our storage, they are gone. A photo is in the recovery history of the database of accounts, which runs out within 30 days. Messages you wrote in workspaces owned by others, direct messages included, are not removed with your account; they stay there without your name, and so do your reactions, the messages that name you, and the tasks and steps that were yours in shared projects. Your personal projects there are deleted with everything in them, as when you leave. You can delete any message of yours while you are a member, can open the place it was written in (a project shared with chosen people can stop being open to you), the part it was written in is switched on in that workspace (Chat for a channel or a direct chat, Work for a task or a chat inside a project), and how much chat its project has does not hide it; a message written in an archived task, once that task is put back. You can leave a workspace at any time. For anything else, write to hello@rolengine.com.