Privacy Policy

Effective: November 5, 2026

This policy describes how RyzaLab handles information when you use ryzalab.com (this website). It does not cover our work inside your home or on your networks; that is governed by your client agreement. This page is for transparency, not legal advice.

Who we are

RyzaLab provides residential technology design and integration. We serve clients in the Austin, Texas area and the New York City metro. This website is operated by RyzaLab LLC. Questions about this policy: hello@ryzalab.com.

The interactive demo at demo.ryzalab.com is a separate site with its own experience and storage; this policy applies to ryzalab.com unless we tell you otherwise.

What we collect

We collect information you give us, information our tools generate to run the site, and limited analytics. The main flows:

  • Consultation booking forms (homepage, Austin, and NYC pages): when you submit the booking form, we may receive your name, email, home or space type, area or borough, timeline, and similar answers you select. A hidden honeypot field is ignored. Before you reach Cal.com, those answers are sent to our server and stored in our Notion CRM. Attribution keys from your browser session (see below) may be included in the lead notes.
  • Project Builder (/ryzalab-project-builder): email, project tier, estimated price range, and complexity score you submit are sent to our server and stored in the same Notion CRM.
  • Scheduling through Cal.com: when you book a call, name, email, booking notes (including answers copied from our form), and UTM or campaign parameters may be passed to Cal.com, either through our inline embed or through redirects at /book/free and /book/blueprint. Cal.com processes that information under its own terms and privacy policy.
  • Email: if you email hello@ryzalab.com, we receive whatever you put in the message (and standard email metadata your provider sends).
  • First-party editorial analytics: on Blog posts and some pages, our measure.js script may send anonymous events to /api/event (for example, that a post was viewed, that a booking link was clicked, or that a booking completed in the inline calendar). Events can include a registered content id, page path, sanitized marketing parameters (source, medium, campaign, content token), and a CTA label. They do not include your name, email, or IP address in the event payload our server stores.
  • Booking redirect analytics: when your browser follows /book/free or /book/blueprint, our server may log a separate analytics record with sanitized UTM fields, optional content id, referrer hostname, request path, and a coarse classification of the browser user-agent string. Name, email, and notes are forwarded to Cal.com only, not written to that analytics record.
  • Cloudflare Web Analytics: Cloudflare may inject a cookieless, aggregate page-view beacon on served pages. It does not use advertising cookies on our behalf.
  • Hosting logs: Cloudflare, as our CDN and host, processes request data (such as IP address, URL, timestamp, and user agent) in server and security logs as part of delivering the site.

How we use it

We use the information described above to:

  • Answer your request and schedule consultations.
  • Deliver and secure the site.
  • Understand which pages and campaigns work.
  • Meet legal obligations.
  • Protect the site from abuse (for example, honeypot fields, size limits, and duplicate lead checks).
  • Communicate with you about RyzaLab services you request.

We do not use the analytics described above to build advertising profiles about you across other companies' sites or apps.

Who we share it with

Service providers process information for us on our instructions and for the purposes above. They include:

  • Cloudflare: hosting, CDN, security, Web Analytics, and Analytics Engine storage for sanitized site metrics.
  • Notion: CRM records for leads and Project Builder submissions.
  • GitHub: storage, in a private repository, of the daily aggregate analytics summaries described under Retention.
  • Cal.com: appointment scheduling; may integrate with calendar and video tools (such as Google Calendar or Google Meet) depending on how a meeting is configured.
  • Email providers: delivery and storage for messages to and from hello@ryzalab.com (the specific provider may change over time).

Third-party content your browser loads directly includes Google Fonts (font files from Google's CDN on styled pages) and, on some Blog posts, YouTube's privacy-enhanced player (youtube-nocookie.com) only after you press play. Those services receive standard connection data such as your IP address and operate under their own privacy policies.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising.

Cookies and similar technologies

ryzalab.com does not set first-party cookies. It does not use localStorage for visitors; the one exception is a flag (rzl_internal) that exists only in the browsers of our own team, set when they open a private link, so we can leave their visits out of our counts. We use sessionStorage in your browser tab only for campaign attribution (ryz_attrib2) and to avoid double-counting a page view; it clears when the tab closes. The separate demo site (demo.ryzalab.com) may use browser storage for the demo.

We do not use Google Analytics or similar third-party marketing tags in the published site code.

Third parties: Cal.com may set its own cookies or storage when you open the booking embed or visit cal.com. Cloudflare Web Analytics is designed to work without cookie-based tracking on visitors. Embedded YouTube may set cookies if you play a video.

Retention

CRM records and email. We keep CRM lead records and email correspondence for as long as necessary to respond to you, provide services, and meet legal, accounting, or reporting requirements. To decide how long that is, we consider the amount, nature, and sensitivity of the information, the potential risk of harm from unauthorized use or disclosure, the purposes for which we process it, and applicable legal requirements. We will delete them if you ask (see Your choices and rights), except where we need to keep a record for legal or accounting reasons. Notion, which holds the CRM records, says pages you delete stay in its trash for 30 days and are then kept in its backups for another 30 days before they become inaccessible (Notion help: duplicate, delete, and restore content). Our email provider may change over time, and its own retention settings apply to messages.

Cloudflare. Analytics data is kept in Cloudflare for operational reporting, only for the period Cloudflare retains it. Cloudflare currently states about six months for Web Analytics, which counts page views and visits, and three months for the site events and booking redirects we record in Analytics Engine, its storage for counts and events. Site events include actions on our pages and status changes for Cal.com bookings (for example booked, cancelled, rescheduled, paid, no-show, or meeting ended).

Daily summaries. A daily process saves a summary for each day (one file per calendar day, in UTC) to a private GitHub repository. Each summary holds only aggregate counts: page views and visits by page, referring website, device type, and country; site events by type, by campaign source and medium (the tags on a link that show where a visit came from), and by offer shown on the site; and booking redirects by kind, by campaign source, medium, and name, and by referring website. The summaries hold no email addresses, IP addresses, full URLs, or user-agent strings. We keep these daily summaries without a fixed end date so we can compare traffic over time.

Traffic classes. Each count is also split into four traffic classes where the data allows: visitor, internal (our own or test traffic), bot or automated, and unknown. Page views and booking redirects are never counted as visitor, because that data does not show whether a person is behind them; they are internal, bot or automated, or unknown. Only site events that carry our marker for outside traffic are counted as visitor.

Raw copies. The same daily process also copies the individual site event records (including the Cal.com booking status records above) and booking redirect records from Analytics Engine into private files attached to that process's runs in the same private GitHub repository (GitHub Actions artifacts), where each copy is kept for 90 days. In these copies, each record's identifier and any session or booking identifier are replaced with one-way codes made with a secret key; text a visitor can influence, such as campaign tags and referring websites, is kept only when it matches a known list or a fixed format; and anything that looks like an email address, phone number, or IP address is replaced with a placeholder, so it is not kept in readable form. The copies hold no user-agent strings.

Server logs. The site's server code writes error messages to Cloudflare's live log view, which Cloudflare says does not store logs (Cloudflare Pages Functions logging). For any other server logs that Cloudflare may keep as our hosting provider, the retention period is set by Cloudflare under its own settings and policies, not by us.

Your choices and rights

As our voluntary commitment to any visitor, you can ask us to access, correct, or delete your information, or to stop contacting you, by emailing hello@ryzalab.com. We aim to respond within 45 days. Some state privacy laws (for example Texas) give residents specific rights; where a law applies to us, we will honour it.

You can clear sessionStorage for ryzalab.com in your browser settings.

Security

RyzaLab maintains reasonable administrative, technical, and physical safeguards appropriate to the size of the business and the sensitivity of the information. No method of transmission or storage is completely secure. For how we think about security in installed smart home systems, see Security and Privacy on this site.

Children

This website is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us information, contact us and we will delete it.

Our LinkedIn Page

We may connect the RyzaLab LinkedIn Company Page to an internal reporting tool through LinkedIn's Community Management API. That tool reads aggregate statistics for our own Page and posts, such as impressions, clicks, page views, and follower counts. It does not collect or store the names, profiles, or comments of LinkedIn members who view or interact with our Page. We keep these aggregate reports for no longer than one year. Information you share on LinkedIn itself is governed by LinkedIn's privacy policy.

Smart home client data

Configurations, credentials, device data, and network access for your home are handled under your RyzaLab client agreement and project documentation, not under this website policy.

Changes

We may update this policy when our practices or the site change. We will post the revised version on this page and update the effective date when we publish.

Contact

RyzaLab LLC
Email: hello@ryzalab.com
Phone: (512) 351-4372