What it knows about you.

UrActor asks for very little at the door and then holds whatever you choose to write in it. There is no hidden collection running alongside that: if it is not in this chapter, the app is not storing it.

1. 01

   Your sign-in

   An email address and a password, which are the whole of what registration takes. Both are held by Firebase Authentication, Google's sign-in service. Neither is copied into the diary database, and the password is kept only as a hash — it cannot be read back by us or by anyone else.

2. 02

   Your profile

   A username, and a profile photo if you set one. Both are optional to fill in and both are public inside the app — see the next chapter. Alongside them sit your preferences: country, language, light or dark, the streaming services you follow, and which sections your profile shows.

3. 03

   Your diary

   The substance of it. Films and shows you have marked as seen, your ratings and any written opinions, the dates you watched things on, your watchlist, favourites, rewatch counts and episode progress, the lists you build, and the favourite actors, directors and writers UrActor works out from all of it.

4. 04

   Your friends

   Who you are friends with, who you recorded watching something with, and the recommendations friends have sent you. Friendships are mutual: both people have to accept, and either can end one.

UrActor does not ask for your real name, your date of birth, your phone number, your address or any payment details, and it has no way to store them. It is free, so there is nothing to bill.

This is the chapter most apps bury, so it is near the front here. UrActor is partly a social app, and a diary that friends can read is the point of it — but you should know exactly how far that reaches before you write anything you would not want read.

• Your username and profile photo are public to signed-in users. They are how you are found in search and how you appear in a shared list, so any signed-in UrActor user can see them. Choose a username accordingly, and treat a profile photo as something strangers may see.
• A mutual friend can read everything in your diary. Not a summary of it — all of it: what you have seen, your ratings, your written opinions, your calendar, your watchlist, your favourites, your rewatch counts, your episode progress and who you watched things with.
• There is no per-entry privacy control. You cannot mark a single film, a rating or an opinion as hidden from someone who is already your friend. The control you have is over the friendship itself: accept, or do not, and remove a friend at any time.
• Shared lists are readable by other signed-in users, not only by the people you invited to them. That is broader than it should be and is being narrowed; until it is, treat a list as public within the app rather than private to its members.
• Some of what you do writes into other people's accounts. Recording that you watched something with a friend puts an entry naming you into their diary and calendar, and recommending a title puts your username into their notifications. They can delete those from their side.

Nothing here is visible to the open internet. All of it sits behind a sign-in, none of it is indexed by search engines, and there is no public web profile.

Five services outside UrActor are involved in running it. Each is listed with what it actually receives, because "we may share data with third parties" is a sentence that tells you nothing.

Google Firebase

Authentication, database, file storage and server functions. Everything in the chapter above is stored here. Google processes it on our behalf.

TMDB

Film and television metadata, artwork and streaming availability. Receives what you type into search and the identifiers of titles you open. No account identifier is sent, so TMDB cannot tell one user from another.

OMDb

IMDb ratings. Asked by our server rather than by your device, so OMDb sees only a film identifier and never your device or your account.

OpenAI

Recommendations. When you generate them, the titles of everything you have marked as seen are sent to OpenAI to produce the list. Your name, email, username and account identifier are not sent — the titles are.

YouTube

Trailers. Playing one loads it from YouTube, which is a request to Google under YouTube's own terms.

The OpenAI entry deserves saying twice, plainly: if you use the recommendations feature, a list of the films or shows you have watched leaves UrActor and is processed by OpenAI. It is not tied to your identity there, and it happens only when you ask for recommendations — never in the background. If you would rather that never happen, do not generate recommendations.

There is no advertising network, no data broker, no analytics vendor and no marketing tool in that list, because there are none in the app. UrActor's servers run in the United States, so if you use it from elsewhere, your data is transferred there and processed there.

A privacy policy is mostly a list of things a company reserves the right to do. This is the opposite list — things UrActor cannot do, because the code to do them is not in it.

• No analytics. There is no analytics SDK in the app. Screens you open, buttons you press and time you spend are not measured, recorded or sent anywhere.
• No crash or performance reporting. No diagnostics are collected from your device.
• No advertising and no advertising identifiers. No ad network, no tracking pixel, no cross-app or cross-site tracking, and no profile built for targeting.
• No selling or sharing for anyone else's purposes. Your data is not sold, rented, traded or handed to a data broker, and it is not used to train anyone's models beyond the recommendation request described above.
• No push notifications, so no device tokens. Notifications from friends live in your account and are shown when you open the app.
• No location, contacts, microphone, device calendar or health data. None of it is requested and none of it could be read.

Permissions, in full. On Android the app declares one: access to the internet. On iOS it declares two — the camera and the photo library — and both exist solely so you can set a profile photo. Neither is asked for until you choose to set one, and declining leaves everything else working.

This website. uractor.com ships no JavaScript at all, sets no cookies, and has no analytics or tracking of any kind. Reading this page tells us nothing about you beyond what any web server necessarily sees in order to send you a file.

Some of it is kept on the device as well, purely so the app opens quickly instead of re-fetching everything each time.

• A metadata cache holding titles, release dates and IMDb ratings for things you have interacted with. It is scoped to your account and deliberately holds none of your own ratings or opinions.
• Cached artwork — the posters and stills already shown to you.

Both are cleared when you sign out and when you delete your account. Neither is transmitted anywhere: they exist to save a network request, not to record anything.

Your data is kept for as long as the account exists, and no longer. There is no inactivity timer that quietly deletes a diary you have not opened in a year, and equally there is no archive kept after you ask for it to go.

You can delete the account from inside the app — Settings, then Delete, confirming with your password — or by email, which needs no app installed and no password remembered. Either way it is immediate and permanent: deletion cannot be undone, and there is no grace period in which to change your mind. The full procedure, step by step, is on the account and data page.

Deleting removes your diary, your calendar, your lists, your settings, your friendships, the sign-in account itself and the caches held on your device. Being straight about the limits of that: a few records are not all reached by the automatic step — the reservation that keeps your username unique, a profile photo already uploaded, and anything you wrote into other people's accounts, such as an entry in a friend's calendar or a notification you sent them. If you want those removed as well, say so in an email and they will be.

Email

larabailen.usa@gmail.com

Send from

The address your UrActor account is registered under

Answered

Within 30 days of the request

Wherever you live, you can ask for a copy of what is held about you, ask for something wrong to be corrected, or ask for all of it to be deleted. If you are in the European Union, the United Kingdom, California or anywhere with comparable law, those rights are yours by statute and this is how to use them.

All of them run through the same address, larabailen.usa@gmail.com, answered within 30 days. Write from the address the account is registered under, since that is what identifies it. Never send a password — it is not needed, and it should not be in an email.

One honest limitation: the app has no export button. A request for a copy of your data is fulfilled by hand, which is why it is an email rather than a download. Correcting most things is faster done yourself — usernames, opinions, ratings and diary entries are all editable in the app.

UrActor is run by one person rather than a company, and holds no data about you beyond what this page describes. There is no data protection officer to escalate to; there is the address above, and your right to complain to your local data protection authority if an answer does not satisfy you.

UrActor is not intended for children under 13, and is not directed at them. It does not knowingly collect anything from a child under 13, and there is no age verification step at sign-up — so if you believe a child has created an account, write to the address above and it will be deleted.

Changes to this policy are published on this page, with the date at the top of it updated. Anything that meaningfully changes what is collected, who it goes to, or how long it is kept will be described here rather than slipped in — and where the change is significant, it will be flagged in the app as well. Continuing to use UrActor after a change means the current version applies.

This policy is versioned in public, along with the site it sits on. If you want to know what it said before, the history is in the repository this page is built from.