Pete Staley, independent developer of MeetingRT. For privacy questions, email plstaley@gmail.com.
Effective date: 2026-09-26.
What this notice covers
This notice covers visits to the MeetingRT informational website and correspondence with the developer. Visiting these pages does not start meeting processing or collect participant feedback.
Website requests and hosting
Netlify hosts this website. Website requests can include your IP address, requested URL, browser information, request time and response information. Netlify processes request information to deliver the site, monitor performance and support security.
The website's own pages include no analytics, tracking cookies, forms, external embeds or persistent browser storage. This describes the site implementation; it does not mean Netlify keeps no operational records or describe every feature of its hosting and private-access services.
The website's own pages do not track your activity over time across third-party websites and do not change their behavior in response to browser Do Not Track signals. Ordinary hosting requests still occur as described above.
See Netlify’s request-monitoring documentation for customer-site request processing. Netlify’s Privacy Statement describes its own website, account and business activities; it does not replace this notice.
Email correspondence
If you email the developer, your address, message and attachments are used to respond to your inquiry, provide support or address a privacy question or security report. The developer uses a personal Gmail account, through which Google processes this correspondence. The developer is the only person authorized by MeetingRT to access it.
Attachments are kept in Gmail unless downloading is necessary. Downloaded copies are included in the applicable cleanup. Please send only what is needed and avoid credentials, meeting transcripts or unnecessary sensitive information.
Provider processing and locations
Google uses servers around the world, and Netlify uses a global network to deliver websites. Their processing may take place outside your country. MeetingRT does not promise U.S.-only processing or storage. See Google’s Privacy Policy and Netlify’s global delivery documentation.
Retention
Routine support correspondence will be deleted within 90 days after the issue is closed.
Privacy requests and security reports are handled separately. Original correspondence and sensitive attachments will be deleted within 90 days after closure or resolution. A minimal record of the request or incident, action and outcome is retained for 12 months after closure or resolution, then deleted. Personal identifiers are included only when necessary.
These privacy/security periods are the developer's retention defaults, not statements of legally required periods. Any justified longer retention must have a documented reason, scope and next review date. Deletion is manual and includes the developer's mailbox and downloaded copies; it does not set retention for Netlify's operational records, Google's underlying backups or other people's copies.
Provider retention is separate from these developer deadlines. Google’s retention explanation describes delays between product deletion and removal from active and backup systems. The history visible in a Netlify dashboard does not establish when every provider copy is deleted.
Privacy questions and requests
Depending on your location and the laws that apply, you may have rights to access or obtain a copy of personal information, correct it, request deletion, restrict or object to processing, or receive portable data. Where applicable, rights may also include withdrawing consent, opting out of sale or sharing, limiting sensitive-information use, equal treatment when exercising rights, and complaining to a privacy regulator. Conditions and exceptions may apply.
Email plstaley@gmail.com and describe the information or interaction concerned and what you are requesting. Your country or state can help determine which rules apply. Do not include credentials or sensitive documents in an initial request. The developer reviews privacy requests and security reports promptly and tracks them separately from routine support. Identity is verified for privacy requests only as necessary. Retention periods are not a reason to delay assessment of a request.
See Support for contact guidance and the initial response commitment. This support commitment does not replace applicable privacy-request deadlines.
Changes to this notice
The developer will publish the revised notice on this page, update its effective date and prominently announce material changes on the website.