Terms & Privacy

Beta service provided as-is

Farpy is a public beta render service. We provide render processing tools and related download and receipt services as-is. Render jobs may fail, and we do not guarantee that every upload will render successfully.

You own your uploads

You keep ownership of the files you upload and the frames produced from those files. You give Farpy permission to store, process, render, and return those files only as needed to provide the service.

Prohibited content

• Do not upload illegal content.
• Do not upload exploitative content or content involving minors.
• Do not upload malware, stolen data, or files intended to attack the service.
• Do not use Farpy to violate another person's rights.

Payment and refund policy

Render prices are shown before checkout. Payment is handled by Stripe. Failed renders should not finalize a charge without a receipt for completed output. If a payment or render result looks wrong, contact us so we can review the job and correct the charge where appropriate.

Temporary file retention

Farpy retains uploaded files and rendered outputs according to operational policies for rendering, delivery, support, storage management, abuse prevention, or maintenance.

No uptime guarantee in beta

Farpy may be unavailable during maintenance, capacity limits, infrastructure problems, or abuse prevention. We may reject uploads, pause work, or fail jobs when needed to protect the service.

The short version

Farpy public beta processes uploaded files to quote and run renders, returns output and receipts through token-gated links, and keeps account email only when you sign in for balance or history. Render files are retained according to Farpy operational policies.

What we collect

Uploaded .blend or .orbx files, generated render outputs, receipt metadata, job status records, account email for signed-in users, payment records from Stripe, Google Analytics 4 page-view analytics, optional Farpy Firehose/custom page-view telemetry when configured, and basic technical logs needed to operate the service.

How we use it

We use uploads to create jobs, run renders, produce output, generate receipts, process payment, prevent abuse, understand page traffic, and debug service issues.

Files

Download and receipt access is controlled by per-job tokens. Uploaded files and rendered outputs are never sold and never used to train AI.

Payments

Payment is handled by Stripe. Farpy does not store full card numbers. Receipts record the job, output hash, amount, and payment status.

Retention

Uploads and outputs are retained only as needed for rendering, download, support, and abuse prevention. Receipts and payment records may be retained where required for financial or legal reasons. Page-view analytics use sanitized URLs and do not intentionally include render, download, or receipt tokens. Technical logs may include IP address, user agent, timestamps, request paths, and operational events.