YardReframe Privacy Policy
How YardReframe handles account details, private garden photos, payments and deletion.
Who we are
YardReframe is a self-service garden concept tool operated by ALPHADEV LLC. Contact hello@yardreframe.com for privacy, access or deletion requests. This policy covers YardReframe, including its restricted technical staging environment. Staging payments use Stripe Test mode and do not move real money.
Information used to deliver the service
We process your email address, account name, password hash and session information to provide and secure your account. We process the photo you choose, its design brief and selected settings, generated concepts, and task status to create and deliver your project. Upload only photos you have permission to use. Avoid people, addresses, vehicle plates, or other sensitive details where possible.
When you submit the sign-in or registration form, the browser may keep a device-local copy of the selected photo and unfinished settings, matched to a hash of the email you entered. This copy can restore the draft for24hours after a reload or email verification on the same browser with that email. It is removed after the photo is saved online or you sign out; expired copies are cleared when you next visit. Closing the browser alone does not erase local storage. Clearing this site's browser data removes the local copy. If local storage is unavailable, keep the original page open. Saved server drafts and projects follow the separate retention rules below. Color preferences and checkout-attempt references can also be stored locally.
We keep order identifiers, purchased allowance, credit activity, delivery/download-response counts and refund status for account service and billing integrity. A successful download response is not proof that you saved the file. Stripe collects payment details on its hosted checkout; we do not collect full card numbers in our application. Technical services can process IP addresses, browser/request metadata and security logs to deliver traffic, limit abuse and diagnose failures. Do not send passwords or card details to support.
Processors and photo access
Operational alerts use aggregate service counters, incident timestamps and budget-reservation thresholds. They do not include your photos, design brief, account email, payment details or signed photo links. If an operator notification channel is configured, only those aggregate alerts are sent to it. Acknowledged alert receipts are cleaned up after90days; unresolved delivery receipts are retained until investigated or delivered. Budget reservations are not a measurement of the provider's settled bill.
Cloudflare provides hosting, private object/database storage and transactional email delivery. Stripe processes payments and refunds. When you explicitly generate, Replicate processes your photo through a time-limited retrieval link together with your prompt/settings using the official FLUX Kontext Pro model and returns generated media. We copy accepted results into our own project storage. A signed image link can be used by someone who possesses it until it expires or access is revoked; do not share it as a permanent public URL.
We do not publish your project in a public gallery or use your photos for marketing without separate permission. We do not use your photos to train our own general-purpose models. Replicate's API documentation states that prediction inputs, outputs, files and logs are removed after an hour by default; website-run predictions have different retention, and our integration uses the API. Its selected model listing states that inputs and outputs are not used for training. These are provider-published statements, not an independent audit or a promise that every infrastructure/backup copy is immediately erased. Earlier restricted technical tests used fal; old jobs can still be queried through their original provider without submitting a new generation. See Replicate retention, selected model terms, Replicate privacy, fal retention for legacy tests, Cloudflare privacy and Stripe privacy.
Retention and deletion
Unused saved drafts expire after 24 hours. A generated project is available for up to 90 days from creation, unless you delete it earlier or its purchase is refunded. The app displays project expiry. A source photo shared with an active project is retained while that project still needs it. Purchased generation allowance and photo storage are separate: deleting or expiring a project does not restore used allowance or cancel a purchase. Download files you want to keep before expiry.
Deleting a project or account revokes application access to its affected photos and queues removal from active object storage, with retries and a seven-day cleanup target. Account deletion also signs you out and removes account-owned application records. Minimal provider-budget reservation and abuse-prevention records can remain so deletion cannot reset cumulative exposure; these records do not contain your photo, design brief, password or card details. If you need billing help, contact support before deleting your account. Financial records held by Stripe, security records and infrastructure backup/recovery copies can remain subject to their own operational or legal retention. We do not promise immediate erasure from backups or processor systems. If removal fails or you need help, contact us so we can investigate outstanding cleanup work.
Choices and rights
You can review/download your projects, delete a project, or request account deletion from account settings. You can request access, correction or deletion at the address above; we may verify account ownership first. Applicable data-protection rights depend on where you live. Photos and account information may be processed in countries where our processors operate. We use necessary authentication and security storage; we do not run a public photo feed or automatically enroll buyers in a newsletter. We will update this page when our processing changes and provide notice of material changes where required.