Effective 2 September 2026
Previously records moments at your tabletop game and turns them into a recap. That means it handles your voice, and sometimes other people's. This page says exactly what is collected, where it goes, and how to get rid of it.
Previously is operated by Cameron Shaw Stallings, an individual based in North Carolina, USA ("Previously", "we"). The app is offered in the United States. Questions and requests go to support@previouslyrpg.com.
An email address, or the identifier Apple gives us if you sign in with Apple, and a display name. We use these to sign you in and to show who is at a table.
Campaign names, session dates, the characters you build (a name, an appearance, a crest, optional notes on who they are and how to say their name), the people you invite, and the cast and threads the narrator keeps track of.
During a session you can tap a button to record a short voice clip, or type a note. Voice clips are uploaded to our storage and transcribed. Recording only happens after you tap the button. It stops when you tap again, or after one minute at most, and the app never records in the background.
Because a voice clip at a table can capture other people, the app asks each member of a table whether they agree to be recorded, and shows everyone who has agreed. It is your responsibility to record only people who have agreed. Someone who declines can still read recaps and take part; they just cannot record.
The written recap and, when there is one, the narrated audio file, are stored so your table can read and listen to them later. The game master can edit the written text.
If you choose a photo from your library for your character, we store that photo. Nothing is taken from your photo library except what you pick.
Subscriptions are sold through Apple. We never see your card. We receive a record of whether your subscription is active, tied to your account, so we know which tables to unlock.
If you allow notifications, we store a device token so we can tell you when a recap is ready. Turn notifications off in iOS Settings at any time.
No advertising identifiers, no location, no contacts, no analytics or tracking SDKs. We do not sell personal information and never have.
We use a small number of service providers, each of which only receives what it needs for its job:
These providers act under contracts that restrict what they can do with the data. To our knowledge none of them uses your content to train models under our agreements.
We process your data to provide the service you asked for (running tables, making recaps, unlocking what you paid for), to keep the service secure, and, for optional things like notifications and recording, because you agreed. You can withdraw that agreement at any time in the app or in iOS Settings.
As long as your account exists, so your table's chronicle stays whole. Voice clips are kept so a recap can be regenerated if it fails; you can delete a session, which removes its clips, transcript and recap. Deleting your account removes your account data and the content you created. Content you contributed to someone else's table (a recap the whole table shares) stays with that table unless the game master deletes it.
Residents of California and other US states with privacy laws have the rights those laws give them, including to know, delete, and correct, and not to be discriminated against for using them. We do not sell or share personal information for advertising, so there is nothing to opt out of on that front.
Previously is for people aged 13 and over. The app asks your birth date before it lets you in and does not keep it if you are under 13. If you believe a child under 13 has an account, email us and we will remove it.
Data travels encrypted and is stored with providers that encrypt at rest. Access to the database is controlled row by row, so a member of one table cannot read another table's content. No system is perfectly secure; if we learn of a breach affecting you, we will tell you.
If this policy changes in a way that matters, we will say so in the app and update the date at the top. Using Previously after a change means you accept it.
Cameron Shaw Stallings, operator of Previously. support@previouslyrpg.com