Each item below is something Rigfolio actually stores, with the reason it exists. If a purpose does not apply to you, the data is not collected.

• Email address. To sign you in, to confirm your address, and to send you account mail: a download is ready, a buyer is waiting on you, a listing was approved or removed.
• Handle, display name, bio, avatar, banner, roles, skills, rate, and availability. Because they are your public profile. You chose to put them there and anybody can see them.
• Discord ID and username, if you sign in with Discord. To authenticate you, and, if you choose, as the contact method on your profile.
• Roblox user ID and username, if you verify your Roblox account. To show the verification mark, and to check game pass ownership when you buy something priced in Robux.
• Listing content and uploaded files. To host what you sell, show the previews, and deliver the files to buyers who have access. We also compute and store a sha256 hash of each file, which is shown publicly so a buyer can see the contents have not been swapped.
• Entitlement records. One row per listing you have access to, saying how you got it. This is what makes your downloads work and what lets a seller see their sales. For the Robux route the row includes your Roblox user ID, the game pass ID, and the response Roblox gave when we asked whether you own it. For the seller’s-own-page route it includes the fact that you stated you paid, the time you stated it, and the seller’s confirmation or refusal and their reason.
• Saved assets, reports, and disputes you create, with their text, so they can be acted on.
• Technical logs, including your IP address. Used for rate limiting and abuse prevention: the counters that stop one account or one address hammering sign in, filing hundreds of reports, or scraping free downloads. Counters are keyed to your account ID and to your IP address, and are deleted after two days. Our hosting provider keeps its own request logs, described in section 4.

No payment information of any kind, ever. There is none to collect.

Rigfolio has no payment processor. There is no card number, no bank detail, no billing address, no billing name, and no transaction record held here, because no payment ever passes through this site. When you pay a seller it happens entirely on Roblox or on the seller’s own payment page, under that service’s privacy policy and not this one. What we hold is the fact that access was granted and how.

We also do not collect: your real name, unless you type it into your display name or bio; your address; your phone number; your date of birth; any government identifier; or any record of what you do on other websites. We do not track you across sites and we do not buy or receive data about you from anyone.

Two, and here they are by name.

• The session cookie, set by Supabase Auth. It is what keeps you signed in. It is strictly necessary: without it there is no way to know a download belongs to you.
• A theme preference, stored in your browser’s local storage rather than in a cookie, holding the single word light or dark if you picked one. It never leaves your browser and we never see it.

There are no analytics on this site. No Google Analytics, no Plausible, no Vercel Analytics, no pixel, no session recorder, no advertising tag.

That is why there is no cookie banner: there is nothing to ask you to consent to. If analytics are ever added, this section will name the tool and say exactly what it collects, and in places where consent is required it will be asked for before anything loads.

Three processors, and what each one actually handles.

• Supabase. The database, authentication, and file storage. Everything in section 1 is stored there. Your password is stored by Supabase Auth as a hash and we never see it.
• Resend. Transactional email. Resend receives your email address and the content of the message being sent to you. It is not used for marketing, and there is no marketing email on this site to unsubscribe from.
• Vercel. Hosting. Vercel handles every request to the site and keeps its own request logs, which include IP addresses, as any web host does.

Two things leave the site that are worth naming separately, because they are not processors:

• Roblox. If you buy something priced in Robux, our server sends a request to Roblox’s public inventory endpoint containing your Roblox user ID and the game pass ID, in order to ask whether you own the pass. That is the whole request. It carries nothing else about you, and your Rigfolio account is not named in it.
• A seller’s payment link. Clicking one takes you to a third party we have no control over and no relationship with. What happens there is between you and them, under their policy.

We do not sell personal data, and we never will.

Public, visible to anybody with the link, including search engines once indexing is on:

• Your profile: handle, display name, bio, avatar, banner, roles, skills, rate, availability.
• Whether you have verified a Roblox account, and which Roblox account it is.
• Your portfolio items, including any links you added.
• Your contact method and its value, if you added one. Treat that field as public.
• Your payment links, if you added any.
• Your listings: title, summary, description, previews, file names, sizes, hashes, price, license.
• Your seller statistics: total downloads granted, live listing count, upheld report count, upheld dispute count, and for the seller’s-own-page route your median confirmation time once there are at least five confirmations to compute it from.

Not public:

• Your email address.
• What you have bought. Your library is yours alone.
• Your saved assets.
• The content of a report you file. The reporter is never shown to the person reported.
• Your claim codes.
• Your actual earnings, which we do not know, because we never see a payment.

• Profile data, listings, and uploaded files: until you delete them or delete your account.
• Entitlement records: for as long as the account exists, because they are what proves a right to download. A seller’s copy of a sale survives the buyer deleting their account only as an anonymous count, since the row itself is deleted with the buyer.
• Rate limit counters, which hold your IP address: deleted after two days.
• Reports, disputes, and moderation log entries: kept while the account they concern exists, because a repeat-offender rule needs a history to count.
• Hosting and email provider logs: kept by Vercel and Resend under their own retention periods, which we do not control.

You can do most of this yourself, right now, without asking us:

• See and correct everything on your profile from your profile settings.
• See what you have access to in your library.
• Delete your account, your listings, and your portfolio items from your account settings.

For a copy of your data in a portable format, to object to a particular use, to restrict processing, or to ask anything else, email [email protected] from the address on your account. We answer within 30 days.

If you are in the UK or the EU, the UK GDPR and the GDPR give you these rights: access, rectification, erasure, restriction, portability, objection, and the right not to be subject to a decision made purely automatically. Our lawful bases are: contract, for the data needed to run your account and deliver what you bought; legitimate interests, for abuse prevention and rate limiting; and consent, where we ever ask for it. You can complain to your data protection authority, and in the UK that is the Information Commissioner’s Office.

If you are in California, the CCPA gives you the right to know what is collected, to delete it, to correct it, and not to be discriminated against for asking. We do not sell or share personal information as the CCPA defines those words, so there is nothing to opt out of.

Deleting your account from your settings deletes the account itself and, through the database’s own cascading rules, your profile, your listings, your uploaded files, your portfolio items, your saved assets, and your entitlement records.

Two honest consequences, both of which the settings page states before the button:

• You lose access to what you bought. An entitlement is tied to an account, so deleting the account deletes the entitlements with it. If you want to keep your purchases, download the files first, or do not delete the account.
• A file somebody already downloaded cannot be recalled. If you were selling, buyers who downloaded your files still have them. That is how downloads work and no platform can undo it.

A seller’s download count is not reduced when a buyer deletes their account, because it counts grants rather than current accounts. Nothing identifying the deleted buyer remains in it.

Entries in the moderation log about a closed account are kept where they concern a different account that is still open, because otherwise a repeat offender could clear their record by cycling accounts.

You must be at least 13 to have a Rigfolio account. If you are between 13 and 18 you need a parent or guardian’s permission, and only they can accept money.

This matters more here than it does on most sites. Roblox’s own audience skews young, so a Roblox development site will be found by children, and we would rather say this plainly than bury it. We do not knowingly keep an account for anybody under 13.

If you believe an account here belongs to someone under 13, email [email protected] and tell us which one. We will look at it and, if it is, remove it and its data. A parent or guardian can ask us to delete a child’s account and data the same way, and we will not ask them to prove anything beyond enough to identify the account.

We do not ask for a date of birth, so we do not and cannot verify anybody’s age. That is a limit of this site, not a claim about it.

Supabase, Resend, and Vercel all operate infrastructure in several countries, including the United States, so your data may be stored or processed outside where you live. All three offer standard contractual clauses for transfers out of the UK and the EU, and those are the mechanism we rely on.

Which region the database sits in is a deployment choice recorded in the project’s own setup notes rather than here, because it can change without this policy changing.

What we actually do, and nothing we do not:

• Passwords are hashed by Supabase Auth. Nobody at Rigfolio can read your password.
• Row Level Security is on for every table in the database, with explicit policies, so a query cannot return a row the signed-in account has no right to. The tables that decide whether a file can be downloaded have no write policy for a browser session at all: only server code holding a secret key can touch them.
• Asset files sit in a private storage bucket that is not reachable by any public URL. Every download goes through a server route that checks your entitlement and then generates a link that expires in sixty seconds. Links are never emailed or stored.
• Every uploaded file is stored as opaque binary data, so nothing anybody uploads can be served back as a web page from this domain.
• HTTPS everywhere, enforced by the host.

We do not hold any security certification and we do not claim one. This is a small site run by one operator. No site is unbreakable, and if we ever find that your data has been exposed we will email you and say what happened.

Changes are posted here with the date at the top updated. If a change is material we will email the address on your account.

The operator is Rigfolio. For anything in this policy, including a request about your data, email [email protected].