Your client's kitchen stays your client's kitchen.
Uploading a client’s project to anyone’s cloud is an act of trust, and trust built on vague reassurance is worthless. Here is what happens to your files, plainly — each point a commitment the Terms and Privacy Policy make in binding language.

- Uploads, textures and logos stay your property
- Rendered images and documents are yours, commercially, no credit
- Client pages show your letterhead, not ours (Pro and Max)
- Trained on — no AI training, stated in Terms and Privacy
- Sold, tracked or used for advertising
- Used to promote RenderFactor
- Written back to your 2020 project
Ownership: inputs and outputs, both yours
What you put in is yours — uploads, textures, logos. What comes out is yours too: rendered images, documents and client pages belong to you, usable commercially, with no credit required. The licence you grant RenderFactor is exactly what is needed to run the service for you — store, convert, render, show to the people you share with — and nothing more.
What is never done with your content
- Never trained on. Your designs and images are not used to train AI models — stated in both the Terms and the Privacy Policy.
- Never sold, never advertising. Your content is never sold and never used to advertise anything to anyone. The site and the app carry one advertising tag, a Meta pixel that measures our own ads by the pages opened and the plan steps taken; it never sees a design, an image or a document, is never on a client page, and the Privacy Policy says how to switch it off.
- Never shown off. Your work is not used to promote RenderFactor.
- Never written back. The service reads your export; it never touches the 2020 project it came from.
Where the files live, and who can reach them
Files are stored with Cloudflare and Supabase in the United States, encrypted in transit and at rest by the providers that hold them, and served through short-lived signed addresses rather than public ones. Access is scoped to your own workspace — the people you have invited — and enforced row by row in the database, not by application etiquette. A client opening a published link sees that design and nothing else, and visitors to a published page are not tracked.
- 30 / 90 / 365days of retention by plan, warning email first
- At oncedeleting a project removes its files immediately
- 30 daysto complete account deletion — one email
- TLS + at restencrypted in transit and where it is stored
Retention and deletion
- On a schedule you know. Renders and idle models age out per plan — 30 days on Starter, 90 on Pro, 12 months on Max — with a warning email before anything is removed.
- At once, when you say so. Deleting a project removes its files immediately. Deleting a published link kills its URL.
- Completely, when you leave. One email to support@renderfactor.com from the owner deletes the workspace, its content and its accounts within 30 days. If a subscription simply ends, nothing is deleted for 30 days and everything remains downloadable.
Who you are dealing with
RenderFactor is owned and operated by RenderFactor LLC, a Wyoming limited liability company — independent of, and not affiliated with, 2020 Technologies or Cyncly. Support is by email at support@renderfactor.com. The Privacy Policy, Terms of Service and billing and refund terms are short, in plain English, and written to be read.

Bring your next 2020 project.
Free for 14 days on your own kitchen: render it at every quality and hand a client a live link before you have paid anything. Cancel in one click.
Start free