Privacy Policy

Your clients. A design may include a client’s name or address, and a letterhead may carry your own. In that content you are the controller and we process it on your behalf; the same protections apply to it as to everything else in your workspace.

Visitors to a published client page need no account and we keep nothing about them. Their IP address passes through our hosting providers’ short-lived server logs, as with any website, and is not stored by us or joined to anything.

Visitors to this website and to the app are seen by one advertising tag, the Meta pixel, described in section 8. It records the pages opened and these steps: a press on a sign-up button, an account created, a checkout begun, a trial started, a plan started, a project uploaded, a render sent and a client page published — with the plan and the price where there is one, and never the contents of a design or an image. Our hosting provider, Vercel, also counts page views for us: the page opened, where the visit came from, the country and the kind of device, with no cookie and no identifier that lasts beyond the day. There are no other analytics scripts and no other trackers.

• To run the Service — sign you in, hold your projects, render your images, produce your documents, serve your client pages and let your members work with you.
• To take payment and to keep the records of it the law requires.
• To keep the account secure — recognise a sign-in from a new device, let an owner see who is signed in, and investigate misuse.
• To tell you about your account and your work — a finished render, a failed import, a receipt, a failed payment, a card about to expire, a warning before history is removed. These are sent because you hold an account; the ones about your work can be switched off, the ones about your account cannot.
• To send tips and news, only if you asked. The box at sign-up starts unchecked. Every such message carries a one-click unsubscribe, and you can change the setting at any time in the app.
• To answer you when you write to us.
• To measure our advertising — to learn which ads on Facebook and Instagram bring people who go on to sign up, through the pixel in section 8, which you can switch off.
• To meet our legal obligations and to establish or defend legal claims.

Beyond that measurement, we do not profile you, make automated decisions about you that have legal or similar effects, or use your content to train models.

We do not sell personal information. One company receives some of it for advertising — Meta Platforms, through the pixel described in sections 1 and 8, and only what those sections list. Everything else is handled by the companies that run the infrastructure the Service is built on, each under a contract that limits them to providing that service to us:

Beyond those, we disclose personal information only to the members of your own workspace as the app is designed to (a member sees the projects and the activity record; an owner also sees who is signed in and from where); to the people you publish a client page to, which shows your letterhead; where the law requires it or a valid legal request compels it, in which case we will tell you unless we are prohibited from doing so; and to a successor if the business is sold or merged, who will be bound by this policy.

We are a United States company and your data is stored in the United States by the providers above, and is accessed by our team to operate the Service and to help you when you ask. If you use the Service from outside the United States, your information is transferred to and kept there. For people in the European Economic Area, the United Kingdom and Switzerland we make that transfer under the EU–US Data Privacy Framework where the provider is certified and otherwise under the standard contractual clauses, with the same protections wherever the information is.

• Account, letterhead and preferences — while the account is open, and until deletion is complete after you close it.
• Uploaded files, models and rendered images — for the history period your plan states, counted from when an image was made or a model’s project was last opened; and at once when you delete the project. The project’s name and record remain so that the gallery can say what was removed rather than show a gap.
• Published client pages — until you delete the link. A live link keeps the model it shows out of the history sweep.
• The activity record — for the life of the workspace, and removed when the workspace is deleted at your request.
• Billing records — for as long as tax and accounting law requires after the transaction.
• Email records — sending history for the life of the account; a bounced or unsubscribed address is kept on a suppression list after the account closes, because that is the only way to keep the promise not to write to it again.

Everything moves over TLS and is encrypted at rest by the providers that store it. Every request to your data runs under your own identity, and the database enforces which workspace it belongs to on every row, so one practice cannot reach another’s. Files are served through short-lived signed addresses rather than public ones. Passwords are never stored, only a hash. The activity record is append-only, so what happened cannot be rewritten. If we discover a breach affecting your personal information we will tell you and any authority we are required to, without undue delay.

Whatever your location, you may ask us to tell you what personal information we hold about you, to correct it, to give you a copy, or to delete it. Much of it you can do yourself:

• See and correct your name, studio, letterhead and email settings in the app’s Settings.
• Take a copy of your images and documents by downloading them from any project; the original export is the folder you uploaded.
• Stop marketing email with the unsubscribe link in any message or the switches in Settings → Email. Messages about your own account continue while you hold one.
• Delete a project from the app, which removes its files at once.
• Delete your account and workspace by emailing support@renderfactor.com from the owner’s address. We will confirm it is you, then delete the workspace, its content and its accounts within 30 days, keeping only what we are legally required to keep, as listed above.

For anything else — access to what we hold, correction, erasure, restriction, portability, an objection to processing, or withdrawing a consent — or if you are a member rather than the owner, write to the same address. We answer within 30 days and do not treat you differently for asking. If you are unhappy with our answer you may complain to the Federal Trade Commission (reportfraud.ftc.gov) or to the privacy authority where you live.

The app sets the cookies its sign-in provider needs to keep you signed in; they are strictly necessary and carry no tracking. This website sets none of its own except the one below, which records that you asked to be left out.

Both this website and the app load one third-party script, the Meta pixel, to measure the advertising we buy on Facebook and Instagram: which ad brought somebody here, and whether they went on to sign up, start a trial or start a plan. It sets Meta’s cookies on renderfactor.com (_fbp, and _fbc when you arrived from an ad; both expire after 90 days) and sends Meta the pages you open and the events listed in section 1 — and, once you are signed in to the app, a hashed form of your email address, so that somebody who saw an ad on a phone and signed up at a desk is counted once. Meta receives that under its own data policy and may use it to build audiences for us and for measurement of its own. The pixel is not loaded on a published client page or on any customer’s own domain, and it never sees a design, an image or a document.

Both also load Vercel Web Analytics, our hosting provider’s page-view counter. It sets no cookie and keeps no identifier: one visit is told from another for a single day by a hash of the request that is then discarded, and what we see is counts — which pages, from which link, from which country and kind of device. Like the pixel, it is not loaded on a published client page or on a customer’s own domain.

To switch it off: turn on Global Privacy Control or “Do Not Track” in your browser — we honour either signal on every page and treat it as a request to opt out — or press the button below, which sets a cookie (rf_ads, one year) on renderfactor.com that keeps the pixel off in this browser, on the site and in the app. Neither affects your account.

The Service is for businesses and professionals and is not directed at anyone under 18. We do not knowingly collect personal information from anyone under 16; if you believe we have, tell us and we will delete it.

Whether or not the California Consumer Privacy Act applies to a business of our size, we give every California resident the rights it describes: to know what we collect and why (this policy), to access it, to correct it, to delete it, and not to be discriminated against for asking. We do not sell personal information. Sending page and event data to Meta through the pixel in section 8 may count as “sharing” for cross-context behavioural advertising under that Act, and you may opt out of it: the button and the browser signals in section 8 are the opt-out, and we treat a Global Privacy Control signal as a valid request. We did no such sharing before 7 September 2026. The categories we collect are listed in What we collect; the sources, purposes and recipients are in the sections after it. To exercise a right, write to support@renderfactor.com; an authorised agent may do so with your written permission.

Where a law such as the EU or UK GDPR applies to information about you, we process it on these bases: performing our contract with you for everything it takes to run your account, render your work and bill you; our legitimate interests in keeping the Service secure, keeping an accurate record of what happened in a workspace, and answering you, none of which override your own interests; our legitimate interest in knowing whether the advertising we pay for works, which section 8 lets you object to at any time; your consent for tips and news, which you may withdraw at any time; and our legal obligations for billing records. If the law where you live gives you rights beyond those set out above, write to us and we will honour them.

When we change it, the date at the top changes with it. For a change that affects what we collect or what we do with it, we will email the workspace owner before it takes effect.

RenderFactor LLC, a Wyoming limited liability company, 30 N Gould St #68054, Sheridan, WY 82801, USA. Privacy questions and requests: support@renderfactor.com.