How rainydays handles your data

Last updated 23 October 2026

rainydays is a board app for game teams, made and run by RainyLofi. This page says what it keeps about you, why, who else handles it, how long it's kept and what you can ask for. It's short because rainydays keeps little: there are no ads, no trackers, and nothing is loaded from other sites, and the only analytics are counts of how many people use it, never who.

Who's responsible

RainyLofi runs rainydays and decides how its data is used. For questions about your data, or to use any of the rights below, email [email protected].

What rainydays keeps

• Your account: your username, display name and email address (and a new address while you confirm a change), when you joined, and your password, stored only as a scrypt hash that can't be turned back into the password.
• Two-factor sign-in, if you turn it on: the secret your authenticator app shares with rainydays, and your recovery codes, stored as hashes.
• Your profile: your picture if you add one, your bio, and your working status and its note, and when you last changed your names, bio or note and your picture. A picture is cropped, shrunk to 256 pixels and re-saved in your browser before it's sent, which drops any location or camera details stored in the photo.
• Your work: the teams you're in and your role in each, invites, and the boards, groups, items, values, updates (comments) and the reactions to them (which emoji, who and when), activity history and inbox notifications that you and your teammates create, and the instances in Roblox Studio that items are linked to with the rainydays plugin (each one's path of names from the game down, what kind of instance it is, the Roblox ID of the game it was linked in, who linked it and when). If you rearrange your sidebar, the order you put its boards and games in, which only you see, until the board, the game or your account is deleted.
• If you're a guest on a team's boards: which of its boards you're on, who put you on each and when, and, if someone set one, when your access ends and when you were told it was near, until you leave, you're taken off, your access ends, or the board, the team or your account is deleted; and while an invite to be one waits, which boards it's for and when its access would end. A team's members see its guests, the boards each is on and when their access ends. As a guest you see the team's name, colour, icon and description and those boards, with the names and pictures of the people on their cards, and the updates on the cards you're on and who reacted to them (not the others'), but not the team's members, their profiles or whether they're online.
• Team icons, if a team's owners add one: the picture, cropped, shrunk to 256 pixels and re-saved in the browser before it's sent, like a profile picture, and when it was added. Only the team's members and guests, and rainydays' staff, can see it. rainydays also notes when a team's name or description last changed.
• When you last used rainydays: the date (not the time) of the last day you used it while signed in. For the whole service, how many people used it each day, how many were active in the week and month to that day, and how many signed up: counts, never who. rainydays' staff use them to see how it's growing.
• Online status, unless you turn it off: while a rainydays tab of yours is open, whether you're using it, held only in the server's memory; and when you were last seen, saved at most every five minutes. People in your teams see "active now", "tab open" or when you were last seen. Turn it off in Settings, Profile, and they see none of it, and the last-seen time is deleted.
• Where you're signed in: for each device, when you signed in, when it was last used, and the browser's description of itself (its user agent), so you can recognise and sign out devices in Settings, Security.
• Access tokens for the Studio plugin, if you make one: each token's name, its first 12 characters (to know it by), when it was made, when it expires and when it was last used (saved at most every five minutes), so you can recognise and revoke it in Settings, Studio plugin. The token itself is shown once, when it's made, and stored only as a hash, and rainydays emails you to say one was made. The plugin, which runs in Roblox Studio on your computer, sends rainydays what you do with it, as the site does: the changes you make to cards and the updates you post, the instances you link cards to, and which of your inbox notifications you've read. To put the boards linked to the game you have open first, it also sends that game's Roblox ID.
• Notifications: your time zone, which your browser tells rainydays while you use it, so due-date reminders and a daily digest come at your time; whether you get due-date reminders, at what time of day and about which days, and the date the last one was looked at. If you turn them on: which kinds you want by email and which in your browser, and whether emails come as things happen or as a daily digest (with its hour). For each browser you turn them on in: the address its maker's push service gave it, the two keys rainydays uses to encrypt notifications for it, a short name such as "Edge on Windows" (not the browser's full description of itself), and when it was turned on and last used. Notification emails and browser notifications carry what the inbox notification says, so they can include item names, board names and the start of an update from your team's boards.
• Sign-in safety: a count of failed sign-ins on your account, so repeated guessing slows down.
• If you report something to rainydays' moderators: what you reported (a person, an update on a board or an invite), a copy of it as it was then, the reason you picked and anything you wrote, and when; once staff have looked at it, what they did (you're told whether they acted). The person you report isn't told who reported them, and if they're staff, neither are staff below them. One exception: if one of rainydays' staff sent you an invite and you report it, they can tell it was you, as only you could.
• Moderation: if staff suspend your account, since when, until when and the reason you're told; what staff do (such as clearing a profile, removing a picture, an icon or an update, renaming an account or a team, suspending or deleting an account, deleting a team), who did it, to whom, when and why; and which profiles, pictures and team names and descriptions staff have looked at, kept as a short fingerprint of what they saw so that a change shows again. A list of words staff watch for in profiles and team names is kept too.
• Email links: the links rainydays emails you (to confirm an address, reset a password or change your email) are stored only as hashes.
• Roblox games, if your team adds one: the game's public details and icon, its player count, likes and dislikes every 10 minutes, and, with an Open Cloud API key, the latest of its analytics (players over time, daily players, retention, session length, Robux spent, errors per day), its 20 most frequent errors of the day and its published versions. When a team makes an error group into a bug card (or adds one to a card), the link keeps that group's message, stack trace and when it was first seen, and every check after that keeps how often the group happened in the day before it, so the card can say whether its fix held once it ships. Each hour's average and busiest player count is kept too, and so are the game's numbers around each release (the three days before and after it) and the error groups first seen after it. Error messages come from the game's own logs, so they can name a player if the game's scripts put one there. A key is stored encrypted and is never shown again, only its name and its first ten characters, which is how Creator Hub shows it, and the public name of the Roblox account or group it belongs to (its username, or the group's name), which only those who manage the team's games see.
• A game's store: its game passes and developer products as Roblox lists them (each one's name, price, whether it's for sale, whether price tests or regional pricing are on, and its icon), each change seen to a name, a price or whether it's for sale, and each one's price on each day it's for sale.
• Sales, if a team runs them: each sale's name, when it runs, its discount or prices and name tag, who planned it and who ended it early, and for each item the price and name it had when the sale started (and whether it was for sale) and what the sale set.
• Games a team watches: the public details and icon of other Roblox games a team chooses to watch, their player count, likes and dislikes every 10 minutes, each hour's average and busiest player count, and each time Roblox says one was updated. It's only what Roblox shows everyone on a game's page.
• Live events, if a team plans them: each event's name, when it starts and ends, its colour and notes, who planned it, which board items or groups are aimed at it and by whom, and the game's numbers during it and before; for one that repeats, how it repeats and the time zone it was planned in. A game's events on Roblox come in with what Roblox shows players (each one's title, subtitle, description, times, category, who sees it and its thumbnail), and so does what a team writes for an event it puts on Roblox. The game's images, to pick a thumbnail from, are kept as copies, and so is an image someone uploads for one, with who uploaded it.
• Game alerts: when rainydays saw a team's game in trouble (its players falling far below normal, a spike in errors, the game unlisted or made private, or its API key stopping), when that started and ended, and the numbers it saw then. Also whether you chose to get a team's alerts or not (without a choice, admins and owners get them and members don't).
• Releases: each published version of a team's game, whether the team calls it an update (and the name it gives one), which of the team's board items went out in it, which were found in it (a bug that came in with it: set on the item, or worked out from when its error was first seen), and when an item was finished, so the next release can take it. Also the updates a team plans for a game (a name, the day it's meant to go out, who planned it, and the release it became once it's out), and which items or groups are aimed at one, and by whom.
• Weekly reports, if a team turns them on: each report as it was made: the team's games' numbers for the week, their releases and items, their most frequent errors, which bug cards' fixes held or not, and survey results.
• Discord, if a team adds a channel: the channel's webhook (the address rainydays posts to), stored encrypted, of which only its name and last four characters are shown.
• Player surveys, if a team runs them: the answers people give on a survey form: their picks and anything they type. The form doesn't ask who you are and needs no account, and rainydays doesn't store your IP address or anything else about you with your answers. The web server's log (see Server logs below) notes for 14 days that answers were sent from your IP address, and when, but not what they were. Please don't type your name, username or anything personal into it.

Apart from the web server's log, kept 14 days (see Server logs below), rainydays doesn't store IP addresses. It also uses yours to limit how many sign-ups, sign-ins, codes, password resets and survey answers can come from one network. That count is held in memory, never written to disk, and dropped about an hour after the last attempt. Counts kept the same way, by token and by account rather than by address, limit how many requests the Studio plugin can make with each access token and how many tokens you can make in an hour.

People in your teams see your name, username, picture, bio, working status and online status, and what you do on the team's boards. A team's owners choose what each role in it can see of the team's games, such as their analytics and Robux.

rainydays' staff are RainyLofi and the moderators RainyLofi chooses. To keep spam and abuse off rainydays, they can see every account's username, display name, picture, bio and status note, when it joined and last used rainydays, whether its address is confirmed and two-factor sign-in is on, failed sign-ins, its teams and roles, the teams it's a guest of, how many cards, updates and personal boards it has made and how many invites it has sent that are still waiting, and teams' names, descriptions, icons, members and how much is in them. The site's admins also see email addresses, where accounts are signed in, and each account's access tokens for the Studio plugin (their names, first 12 characters, and when each was made, expires and was last used, never the tokens themselves). Staff see something on a team's boards only when someone reports an update there, and then only that update, with the names of its card and board.

Why

• To run the service you signed up for (the contract between us): your account, your boards and teams, the Studio plugin's access tokens if you make them, and the emails you need, such as confirming your address, resetting your password, team invites and telling you an access token was made.
• To send the notifications you turn on (your consent, which you can take back at any time in Settings, Notifications): emailing them or sending them to your browsers.
• To keep accounts safe (a legitimate interest, protecting your account and everyone else's from misuse): limiting attempts, recording where you're signed in and when each access token was last used, and counting failed sign-ins.
• To keep rainydays free of spam and abuse (a legitimate interest, protecting the people who use it): reports, what staff look at and do, suspensions and the staff's log.
• To keep rainydays secure and working (a legitimate interest, protecting the service and the people who use it): the web server's log of requests, used to spot attacks and abuse and to track down problems.
• To see how rainydays is used (a legitimate interest, running and growing the service): the day you last used it, and the daily counts, which say how many people and never who.
• For surveys and reports (the legitimate interest of the team that runs them, in hearing what its players think of each update): keeping survey answers and weekly reports for as long as listed below, and limiting how many answers can come from one network.

rainydays doesn't use your data for advertising or profiling, and doesn't sell it. Its only analytics are the daily counts above.

Who else handles it

• DigitalOcean hosts the server and its database, in the United States (New Jersey).
• Cloudflare sits in front of the site. Every request passes through its network, which provides the secure connection and blocks attacks, so it sees your IP address and the requests your browser makes (and the Studio plugin, if you use it), as it does for every site it serves. It also asks your browser to report back to it if a connection to the site fails.
• Zoho Mail sends rainydays' emails from its EU data centres, so your email address and each message pass through it, including any notification emails you turn on.
• Your browser's push service, if you turn on browser notifications: Google's (for Chrome and most other browsers), Mozilla's (Firefox), Apple's (Safari) or Microsoft's (Edge on Windows) carries each one to your device. A notification is encrypted for your browser alone, so the service can't read it, but it does see that rainydays sent your device something, when, and how big it was.
• Roblox answers rainydays' server when a team has added a game: it's asked about the game, its game passes and developer products, the games the team watches, and the account or group a key belongs to (by its Roblox ID), and sees the team's API key. It's asked about the game's events on Roblox too. For a sale a team schedules, it's asked to change those items' prices and names (and to put one that's off sale on sale for it), and to put them back when the sale ends; for an event a team puts on Roblox, to make it, change it or delete it there, and to take an image someone uploads for it as one of the game's images. Those are the only things rainydays changes on Roblox. Your browser never contacts Roblox from rainydays, and nothing about you is sent. The rainydays plugin for Roblox Studio talks only to rainydays: Studio, on your computer, sends its requests to rainydays, and rainydays passes nothing from them on to Roblox.
• status.io, which hosts Roblox's status page, is asked every few minutes how Roblox is doing and which incidents it has reported, so game pages can say when Roblox itself has trouble. Nothing about you or your team is sent.
• Discord receives what rainydays posts to a team's channels: the weekly report (the team's games' numbers, releases, item names, how many bug fixes held, and survey results: counts, scores and the most mentioned words, never the answers themselves) to the channel the team picks for it, a game's alerts (what looks wrong and its numbers, and when it's over) to the channel the team picks for those, and a survey's link (with the game's name, the update's name and version, and item names only if the team turns that on) to its community's channel. Nothing about you is sent.

DigitalOcean and Cloudflare are US companies, so your data is transferred outside the UK and the EU.

How long it's kept

• Your account, profile and work: until you delete your account. A sign-up whose email address is never confirmed is removed after 7 days.
• Invites: until they're accepted, declined or withdrawn, and at most 14 days. One goes sooner if whoever sent it leaves the team or can no longer invite people.
• Where you're signed in: until you sign out there, or 30 days after that device was last used.
• Access tokens for the Studio plugin: until you revoke one, you change or reset your password, rainydays' staff sign you out everywhere or suspend your account, or you delete your account. One that expires (after the 7, 30, 90 or 365 days you chose) stops working then, stays in your list as expired for 30 days, and is then deleted. An item's links to instances in Studio stay with it until someone unlinks them, or the item is deleted.
• Email links: a password reset link works for an hour and the others for 48 hours. Each is deleted a day after it expires.
• Notifications: read ones are deleted after 30 days, and each inbox keeps only its newest 200. Your choices (what's emailed and sent to your browser, and your reminder time) and your time zone stay until you change them or delete your account.
• Online status: the in-memory part only while your tabs check in, and gone when the server restarts. The last-seen time is replaced each time you're seen, and deleted when you turn online status off or delete your account.
• Browsers with notifications on: a browser gets them only while you're signed in on it. They stop when that sign-in ends (you sign out there or from another device, it expires, or you change your password), and the browser's entry is deleted when you turn them off there or remove it in Settings, you sign out on it, someone else signs in on it, its push service says it has stopped, a month after its sign-in ended, or after half a year without being opened.
• Team icons: until a team owner removes or replaces it, or the team is deleted.
• Roblox games: player counts, likes and dislikes for 15 days, and their hourly averages for 120 days; analytics, errors and versions only as their latest copy, replaced as they update, apart from how often each error group on a bug card happened, kept 45 days. Releases, with their numbers, stay with the game; so do planned updates, until a team deletes one (an item's or a group's aim at one goes with either); the error groups new in a release are kept 180 days. Live events stay until a team deletes them, or with the game (one deleted on Roblox stays here, with its numbers); an item's or a group's aim at one goes with either, or with the occurrence of a repeating one it's at, when "this and the ones after it" makes it again in a new rhythm. A game's images are kept while the game lists them or one of its events uses them, and a month after. Roblox's incidents are kept 180 days. A store's changes and its items' prices by day are kept 400 days, and so is a sale once it's over. A watched game's player counts are kept 15 days, their hourly averages 120 days and its update times 180 days; all of it goes when a team stops watching it, or with the team. A game's data and a key are deleted when a team admin removes them, or with the team. A bug made from an error is a board item like any other, its first update the error's details; the error groups on it go with it, or when someone takes them off it, while whether its fix held (and how often its errors were seen the day that was judged) stays with the card.
• Game alerts: 90 days after each one ends, or with the game. Your choice of a team's alerts stays until you change it or leave the team.
• Weekly reports: half a year. Discord webhooks: until a team admin removes them, or with the team.
• Survey answers: a year after their survey closes, or sooner if the team deletes the survey or the game. The survey's results (counts, scores and the most mentioned words) stay with the game.
• Server logs: the web server keeps a log of each request it serves for 14 days: your IP address, the time, the address asked for (with anything after a "?" in it, such as words searched for, or the Roblox ID of the game open in the Studio plugin), the answer it gave and its size, the page that led there if your browser says, and your browser's (or Roblox Studio's) description of itself. The plugin's access token travels in a header the log doesn't record. It also keeps an error log for 14 days, which records Cloudflare's addresses rather than yours, and when something fails the server notes the error in its system log, without your IP address or anything you sent. Only RainyLofi, who runs the server, can read these logs.
• When you last used rainydays: replaced each day you use it, and deleted with your account. The daily counts aren't about anyone, and are kept.
• Moderation: a report until staff close it, then a year; a suspension until it ends or is lifted; the staff's log two years; a "looked at" mark until staff look again or what it's about is deleted.
• Upgrade backups: before the database is upgraded, a copy is saved on the same server in case the upgrade has to be undone.

When you delete your account, your account, profile, picture, personal boards, sign-ins, access tokens, email links, time zone and notification choices (with the browsers they go to) are deleted straight away, and so is any team you were the only member of. What you added to a team's boards stays with the team: items keep their content, your updates stay but are no longer linked to you (your reactions to updates are deleted), instances you linked items to stay linked without saying who linked them, and activity lines and teammates' notifications keep your name as it was written. Reports about you and the staff's log keep what they say, your username included, for as long as listed above; reports you made keep what you wrote, but no longer say who made them.

Your rights

You can see and correct most of your data yourself in Settings, and delete your account there under Account. You can also email to ask for a copy of your data, to have it corrected or deleted, or to restrict or object to how it's used. If you're unhappy with the answer, you can complain to the data protection authority where you live; in the UK that's the Information Commissioner's Office.

Cookies and storage

rainydays sets one cookie, __Host-rd_session, which keeps you signed in. It's strictly necessary, scripts can't read it, it's only sent over HTTPS, and it lasts 30 days from when you sign in.

Your browser also keeps a few choices on your device: your theme, table or kanban for each board, which groups, sub-items and sidebar sections are open, and whether finished items are shown. While you sign in it briefly remembers the page to return to. While you're signed in, it notes that you are, so rainydays.work opens your work rather than the home page; signing out clears it. If you view a team as another role, that tab remembers which until you stop or close it; rainydays doesn't keep it. If you answer a survey, it remembers that you did, so the form thanks you rather than asking again. None of this leaves your device.

If you turn on browser notifications, your browser also keeps rainydays' small notification script (a service worker), which only shows them and opens the page one is about, and the push subscription it was given. Turning them off, or signing out, removes the subscription.

If you use the Studio plugin with "Remember on this computer" ticked (as it starts), your access token is saved in Roblox Studio's plugin settings on your computer, so you stay signed in when Studio opens again. Studio keeps those settings as plain text, where other plugins on that computer can read them, so untick it on a computer you share: then the plugin keeps the token only until Studio closes. Signing out in the plugin forgets it.

There are no analytics, advertising or third-party cookies, so there's no cookie banner to click.

Changes

When this page changes, the date at the top changes with it.