Last updated: October 9, 2026 · RendrPro
1. Scope and contact
This Policy explains how RendrPro handles information in our public website and lighting design platform. RendrPro operates from Texas, United States. For questions or privacy requests, email admin@rendrpro.com.
The platform supports personal and company workspaces. If your employer, contractor or another organization controls a workspace, that organization also makes decisions about the customer and project information it submits. Contact that organization about its practices; you can also contact us for assistance with information processed by RendrPro.
2. Information you provide
Contractor applications include your name, company, business email, phone, optional website, qualification answers and consent to review and follow-up. We store applications in Supabase and send a notification through our configured email service to admin@rendrpro.com. Applications do not automatically create accounts.
Account and organization information includes your name, email, authentication and verification information, company name, logo, workspace membership and authorized role. Supabase supports our authentication system and processes sign-in credentials and session information. Do not send passwords or recovery codes in support messages.
Workspace content includes property and customer photographs, project names and details, customer information you enter, saved product placements and design settings, render requests, correction instructions, generated images, versions and presentation choices. Photos and project details can identify people or properties even when you do not intend them to. Submit only information you are authorized to use.
Support, feedback, feature requests and product requests include the message, request type, contact information you supply and our handling of the request. Emailing support also shares your sender details and message through your email service. Account records can include plan status, credit allocations, usage and transaction references needed to administer access.
3. Technical and usage information
Vercel Web Analytics records page visits and general device, browser and location statistics without advertising cookies. RendrPro removes query strings, fragments and project identifiers from page URLs before reporting; public proposal, authentication and account-setup routes are excluded. Vercel processes request metadata to produce these statistics under its privacy notice.
Operating the platform involves request and security logs, device/browser and network information, timestamps, account and workspace identifiers, render job status, error information, provider request identifiers and credit activity. Our hosting and infrastructure providers may process IP addresses and technical logs even where our application analytics does not store a raw IP address.
When enabled, first-party acquisition measurement records public page visits, walkthrough clicks, booking-modal openings and accepted bookings reported by Cal.com. A click is not counted as a booking. Booking identifiers are used in same-tab storage to avoid duplicate confirmations, but booking names, emails, times and identifiers are not sent in acquisition events. Historical events may include pricing visits and signup activity. These events do not prove account creation or completed product work.
4. How we use information
We use information to register and authenticate users, enforce workspace permissions, store and organize projects, render and correct images, apply account features and credits, provide downloads and presentations, and respond to support and privacy requests.
We also use relevant information to diagnose failures, recover unfinished output storage, prevent abuse, investigate security issues, maintain service reliability, understand website acquisition and improve the product. We may retain or disclose information when necessary to meet applicable legal obligations or respond to valid legal process.
5. Image processing and AI services
When you request an AI rendering or correction, relevant property images, design instructions and supporting image inputs are processed by the rendering worker and OpenAI. These inputs are necessary to perform the operation; the images do not stay solely in your browser. Generated outputs and associated job records are stored for the workspace's rendering, version and presentation features.
The worker uses temporary output files and private intermediate images for recovery and eligible corrections, including clean intermediates for watermarked outputs. Temporary provider-file deletion is attempted when the operation's state permits it, but cleanup can fail or be delayed. Provider retention depends on the service, processing requirements and configured account controls. We do not promise zero retention, immediate deletion from every provider system or that every submitted file has the same retention treatment.
6. Service providers and authorized access
Opening the booking calendar loads Cal.com, which processes scheduling details, contact information and technical data under its own privacy practices. Choosing to load the overview video connects to YouTube’s privacy-enhanced player; YouTube may process device, playback and network information and use browser storage under its policies. You can choose not to load these services and contact us by email instead.
The current architecture uses Supabase for authentication, database and private media storage; Vercel for the web application; Render for worker hosting and persistent worker storage; and OpenAI for AI image processing. These providers process information relevant to their functions. Our email service processes messages sent to support. Where a configured payment flow is used, its provider processes the payment information submitted there and the platform receives the account and transaction references needed to administer entitlements.
Authorized members and managers can access information within the workspace permissions provided to them. Authorized platform administrators can access information needed to administer the service, investigate problems and respond to requests. Private media is protected through application authorization and storage access controls; that is not a promise that no authorized administrator or service provider can process it.
Your own downloads, emails, screenshots and presentations can disclose content to the recipients you choose. We do not control copies you or your organization share outside the platform. External websites linked from RendrPro have their own practices.
The current RendrPro platform does not sell personal information or transmit acquisition events to targeted-advertising networks. Processing by the infrastructure and AI providers described here is still necessary to operate the service.
7. Cookies and browser storage
Authentication cookies maintain sign-in sessions. Other necessary cookies support workspace selection, invitation setup and authorized administration views. Blocking or clearing these can sign you out or prevent features from working.
The website retains filtered first- and latest-touch campaign labels from UTM parameters in same-tab session storage to understand how visitors arrive. Only bounded campaign-label characters are accepted; the acquisition payload excludes raw query strings, email addresses, customer photos and arbitrary free text. Closing the tab normally ends this session storage, subject to your browser's session-restoration behavior.
When first-party acquisition collection is enabled, a signed visitor cookie lasts up to 24 hours without extending its original lifetime for each event. It links the limited website events described here, rather than identifying a verified account. The ingestion service uses a daily hashed network identifier to limit abuse; it does not store a raw IP address in the acquisition records. The current integration does not install third-party advertising pixels or cross-site advertising analytics.
8. Your choices and requests
You can update supported account details in Settings, use available project deletion controls, manage browser storage and cookies, and choose what information to upload or include in support messages. Our acquisition observer does not send its events or write campaign session storage when the browser reports Do Not Track. Essential authentication, security and operational processing still occurs.
Depending on the law that applies to you, you may have rights to request access, correction, deletion or a portable copy of personal information, or to object to or opt out of certain processing. Send requests to admin@rendrpro.com with enough context to locate the information. We may need to verify your identity and authority, and consider other people's rights, workspace ownership and legal retention obligations. Do not send identity documents unless we explain a necessary verification method.
If you disagree with a privacy-request decision, reply to admin@rendrpro.com and ask for a review or appeal. You may also contact the appropriate regulator, including the Texas Attorney General where applicable. We do not claim that every privacy statute applies to every user or that an email request always requires deletion of another organization's records.
9. Retention and deletion
Account, organization, project, design, rendering and credit records remain available for their service and administrative purposes until they are deleted through supported processes or otherwise removed. There is no single automatic expiration period for all of these records. Closing access, deleting a user and deleting a company project can have different effects. Account deletion is handled through authorized administration rather than a self-service account-delete button. The account-deletion workflow retains required financial, audit and complimentary-allocation history and does not automatically delete a company merely because one user is deleted.
Authorized project deletion attempts to remove stored photo and render files before deleting the project records. Work with an active rendering operation cannot be deleted through that flow until the operation is resolved. Errors can leave cleanup incomplete. Private worker archives associated with deleted jobs or versions are checked for cleanup while the worker is running; this depends on successful checks and is not an instant-deletion guarantee.
When acquisition collection is enabled, events older than 90 days are pruned in limited batches during ingestion. Older records may remain during inactivity or until cleanup catches up. Rate-limit entries older than 24 hours are similarly cleaned during ingestion. Applications, support and feedback do not have an automatic fixed deletion deadline in the current implementation; contact us about a specific request.
Backups, security logs, transaction or credit records, legal requirements, dispute handling and provider systems can require different retention. Removing a visible project does not necessarily erase every related record or external copy immediately. We evaluate deletion requests in light of these purposes and applicable requirements.
10. Security
The application uses authenticated access, workspace authorization, private media storage and limited-access administrative functions. Public feedback and acquisition endpoints validate input and apply rate limits. We use these controls to reduce unauthorized access and abuse, but no network, storage system or security control guarantees absolute security.
Use a strong password and secure your email account and devices. Do not upload unnecessary sensitive information, and contact support promptly about suspected unauthorized access or disclosure.
11. Processing locations
RendrPro is based in Texas, United States and uses cloud services. Information may be processed in the United States and other locations used by the relevant providers. Your location does not guarantee that every copy of your information is stored in that location. Contact us before submitting information subject to requirements the platform may not support.
12. Children's privacy
RendrPro is intended for professional lighting and business use and is not directed to children under 13. If you believe a child has provided personal information to the service, contact admin@rendrpro.com so we can investigate and take appropriate action. Do not include unnecessary images of children or other personal details in property photographs.
13. Business transfers
Information may be disclosed or transferred in connection with a proposed or completed merger, acquisition, financing, sale of business assets, reorganization or similar transaction, subject to applicable law and appropriate confidentiality protections. Information remains subject to applicable privacy obligations; a transaction does not remove your non-waivable rights.
14. Updates to this Policy
We may update this Policy to reflect product, provider, data-handling or legal changes. The date on this page shows the latest version. We will provide additional notice when required by applicable law. New advertising integrations or materially different data uses require an updated disclosure and any applicable choices before they are introduced.
Google Maps features
RendrPro includes Google address suggestions and optional Street View. Use of these features and their content is subject to the current Google Maps End User Additional Terms of Service and Google Privacy Policy.
Address searches are sent to Google. Selecting a suggestion saves the confirmed address and Place ID with your project; coordinate caches are cleared after 28 days. Street View loads only when you request it. Saved property views contain camera settings and a panorama identifier; Google serves the imagery directly, and RendrPro does not send it to AI providers. Google receives technical information needed to deliver its features, including your network address and search or location requests.
Provider information
Learn more about the providers supporting RendrPro: Supabase, Vercel, Render, and OpenAI API data controls. Their notices and applicable service agreements describe their own processing; they do not replace this Policy.