RenoBriqoWorkspace sign in1. Who is responsible
SPD IT Solutions operates RenoBriqo. This policy describes how we handle personal information to provide the app, administer subscriptions, secure access and respond to requests. A company using RenoBriqo also has its own responsibilities for the customer, worker and project information it collects and puts into its workspace. For information held on a company's behalf, contact that company's workspace owner first; you may also contact us using the request form. Our internal platform dashboard relates to RenoBriqo only, even when payment or email infrastructure is shared with other SPD IT Solutions services.
2. Information the service processes
Account information can include username, full name, email address, profile photo, role and account status. Workspace records can contain business and billing contacts, project addresses and contacts, site photographs and scans, measurements, layouts, work scopes, quotations, tasks, expenses, mileage, warranties and service requests that users choose to submit. Billing records include Stripe customer, subscription, product, price and invoice identifiers, plan, currency, payment status and invoice links. Technical information can include session identifiers, security events, request paths, account identifiers, timestamps and network information needed to operate and protect the service. Support requests contain the contact details and message you provide. Do not submit unnecessary sensitive personal information.
3. Why information is used
We use account and workspace data to authenticate users, enforce roles, save and display records, produce requested outputs and support collaboration. We use billing data to administer subscriptions, verify payments, apply limits, issue or display invoice records and resolve billing issues. We use security information to detect abuse, limit sign-in attempts, send and verify login codes and investigate incidents. We use contact requests to respond and verify a requester's authority. We use business-level usage and app-specific financial totals to operate RenoBriqo. We do not use this release to serve behavioural advertising or sell workspace personal information.
4. Permission, choices and public information
Workspace owners must explain their collection and use to the people whose information they submit and obtain any necessary permissions or other lawful authority. The app's necessary processing supports account access and the services requested; optional activities should not be confused with consent to receive marketing. Uploading a photo, enabling AI or publishing a catalogue is a separate action with its own consequences. Review outputs before sharing: a public catalogue, downloaded document or emailed quotation can be read and copied by its recipients. Do not publish private contacts or project photos inadvertently. You can change profile details and available preferences, and you may withdraw optional consent; this can affect the corresponding optional feature.
5. Who can receive information
Authorized users within a company can access records according to their role and project permissions. Platform operators receive company, usage, billing, security and support information necessary to administer the service. Service providers can process limited information needed for their function: the hosting infrastructure for stored data and requests, Stripe for subscriptions and payment processing, Microsoft Graph/Exchange for administrator verification emails, and OpenAI when an enabled AI preview is explicitly requested. Your selected suppliers or other integration providers can receive information necessary for a requested import or integration. Providers are subject to their own terms and applicable contractual safeguards. Information may also be disclosed to meet legal duties, respond to lawful process, protect rights and security, or complete a business transfer with appropriate safeguards and notice.
6. Payments and email verification
Stripe hosts card entry and payment management. RenoBriqo stores billing references and status, not full card numbers or security codes. Stripe may handle payment data for its own compliance and fraud-prevention responsibilities as explained in its privacy terms. Administrator security emails contain a single-use code and sign-in context and are sent through the configured Microsoft Graph sender. They are transactional security messages, not marketing. The app stores a protected verification value, expiry and attempt count rather than a reusable plaintext code. A successful mail API response means that delivery was accepted for processing; mailbox filtering and provider outages may affect receipt.
7. Optional AI processing
When an authorized user requests an AI preview, the image and instructions needed for that request are sent to the configured AI provider. Do not include unnecessary faces, documents, addresses or other identifying details. AI previews are disabled in the public demo and ordinarily in free trials. Generated images may be inaccurate and do not replace professional judgment. Provider retention and processing practices depend on the configured account and service terms; this policy does not promise zero retention or a particular training setting unless separately confirmed. Disabling AI prevents new preview requests but does not itself remove outputs or requests already processed.
8. Locations and cross-border processing
Data is hosted in the deployment's configured cloud environment. Providers and support personnel may process information in Canada or other countries, including the United States, depending on the hosting region, email tenant and provider configuration. Information processed outside your jurisdiction can be subject to the laws and lawful access requirements there. We do not promise Canada-only residency for this deployment. Ask through the contact form if residency or a processor agreement is required before uploading regulated data.
9. Safeguards and access controls
The app uses authenticated sessions, company and role boundaries, restricted platform access, protected credential configuration and secure transport in a properly configured production deployment. Verification codes expire and have attempt and resend limits. Access and billing events can be logged for security and support. These measures reduce risk but cannot eliminate it, and process/directory separation on one server is not a substitute for a dedicated hostile-code sandbox. Protect your mailbox and devices, limit who you invite and report suspected exposure promptly. We assess incidents and provide notifications where required by applicable law.
10. Retention and deletion
We retain information for as long as reasonably necessary for the service, legitimate security/support purposes and applicable legal, tax, accounting or dispute obligations. Cancelling or losing editing access does not automatically erase project records. Retention can differ among active content, invoices, event journals, support requests and backups. We review deletion requests, verify authority and explain any legal or technical limitation; a backup or transaction record may be retained where justified and protected from ordinary use. Contact us before closing an account if an export or deletion review is needed. No specific immediate purge or restoration guarantee is made.
11. Your rights and requests
Depending on applicable law, you may request access to or correction of your information, information about our practices, withdrawal of optional consent or deletion where available. We will verify identity and, for company records, authority before disclosing or changing data. Submit a request using the form linked below; include a contact email and workspace code, but do not send passwords, complete card numbers or another person's sensitive records. We respond within applicable legal time limits and explain a lawful refusal or extension where required. You may raise an unresolved concern with the Office of the Privacy Commissioner of Canada or the privacy authority with jurisdiction.
12. Cookies, children and policy updates
Necessary session cookies and browser storage support sign-in, company selection, security and preferences. The Cookie Notice describes the current controls. No optional advertising or analytics tracker is enabled by this release. The service is intended for adult business users; do not knowingly create accounts for children or upload children's information without the required authority. We identify the effective policy version and communicate material changes as appropriate. A broader new use that requires consent will not be justified merely by silently changing this page.
Contact SPD IT Solutions
Send a support or privacy request. You can also contact your company workspace owner about its project records.