Privacy policy

Who this notice covers

This notice applies to people who visit rubblepass.com, submit the contact form, request a validation conversation, or use an account in the RubblePass prototype. If an organization provides access to a future workspace, that organization may also determine why and how project data is processed.

Information we receive

• Contact information you provide, such as name, work email, company and message.
• Prototype account information, such as name, email, role, organization membership and account status.
• Project content entered by authorized users, which may include material observations, photos, documents, comments, reviews and custody records.
• Basic technical and security information generated when the service is used, such as session data, request timing and operational logs. The exact logging configuration may change as the prototype develops.

Why we use information

• Respond to enquiries and discuss a requested pilot or validation workflow.
• Provide, secure, troubleshoot and improve the prototype.
• Authenticate users, enforce workspace access and retain accountable review history.
• Comply with applicable legal obligations and protect people, data and the service from misuse.

Data minimization and project content

Do not upload personal data, exact private locations, confidential documents or hazardous-material information unless it is necessary for an agreed workflow and you are authorized to share it. Project owners should define access, lawful basis, retention and disclosure rules before live data is used. Public demo records are fictional.

How information is shared

Information may be available to authorized members of the relevant workspace and to service providers that host or support RubblePass. It may also be disclosed when required by law, to protect rights or safety, or as part of an organizational transaction subject to appropriate safeguards. RubblePass does not sell personal information.

• Current infrastructure providers include hosting, database and code-deployment services required to operate the website.
• Sensitive project or location information should not be made public by default and should be shared only with permissioned participants.
• Before optional AI is enabled on live content, the applicable provider, purpose, data flow and retention setting should be documented for the project.

Retention and deletion

We retain contact enquiries and prototype account or project records only as long as reasonably needed for the purpose, security, audit, legal obligations and agreed validation. Specific retention periods are not yet standardized for all prototype workflows. A pilot agreement should set them before live customer data is used.

Security and access

We use role-based application access, authenticated sessions and established hosting services as current safeguards. No internet service is perfectly secure. Prototype users must protect their credentials, avoid unnecessary sensitive data and report suspected access issues promptly. The Trust page describes the current control position without implying independent certification.

Your choices and rights

Depending on where you live and the applicable law, you may have rights to access, correct, delete, restrict or object to certain processing, and to receive information about how your data is used. Use the contact page to make a request. We may need to verify identity and authority before acting.

International processing and changes

The providers used to operate RubblePass may process information in more than one country. Any live engagement should identify relevant hosting locations and transfer safeguards. We may update this notice as the product and legal basis develop; the date above will show the latest public revision.