BuildCurrentBusiness operations softwareLog in
Privacy

Privacy Policy

Effective: September 5, 2026 · Version 2026-09-05-v2.1

BuildCurrent is contractor operations software. This policy explains the information needed to operate company workspaces and how that information is used, protected and handled.

On this page1. Accountability2. Information we handle3. Why we use it4. Service providers & transfers5. Company control6. Security & breaches7. Retention8. Communications9. Privacy requests

1. Accountability

BuildCurrent is operated by Christian Soucy carrying on business as Soucy Roofing in New Brunswick, Canada. Christian Soucy is the Privacy Officer for BuildCurrent and is responsible for privacy accountability for the service.

Privacy questions, access or correction requests, and privacy complaints may be submitted through the BuildCurrent Contact page. Requests are reviewed and answered within a reasonable period and in accordance with applicable law.

2. Information we handle

BuildCurrent may process account and contact information, company settings, customer and lead records, estimates, jobs, schedules, workforce records, time entries, expenses, invoices, payment status, documents, photos, communications, support requests and technical service logs submitted or generated through the platform.

BuildCurrent limits collection to information reasonably needed to provide, secure, support and improve the service, administer subscriptions and supported integrations, meet legal obligations and prevent abuse.

Payment-card entry is handled by supported payment providers such as Stripe. BuildCurrent does not ask users to type full card numbers into the BuildCurrent application.

3. Why we use information

Information is used to provide and secure the service, authenticate users, enforce company and role boundaries, connect records across workflows, deliver requested communications, process supported billing and payment workflows, provide support, prevent abuse, maintain auditability and improve reliability.

BuildCurrent does not sell customer business data or personal information to advertisers.

4. Service providers and cross-border processing

BuildCurrent relies on infrastructure and service providers for functions such as hosting, database and authentication, transactional email, payments, analytics necessary to operate the service, support and optional integrations. These providers receive only the information reasonably needed for the services they perform and are subject to their own contractual, security and privacy obligations.

Providers may process or store information outside New Brunswick or outside Canada. When information is processed in another jurisdiction, it may be subject to the laws and lawful access requirements of that jurisdiction. BuildCurrent remains accountable for personal information under its control and uses contractual and technical safeguards appropriate to the service.

Material service providers may include Supabase for database and authentication services, Vercel for hosting and delivery, Stripe for subscription and payment services, Resend for email delivery, and other providers used for optional integrations or features. The providers used for a particular workspace may change as the service evolves.

5. Company responsibility and control

Each customer company controls the business records its authorized users place in its workspace and is responsible for having appropriate authority to collect and use that information. BuildCurrent applies company-scoped access and permission controls so users work within the organizations they are authorized to access.

Customers should avoid placing unnecessary sensitive information into BuildCurrent and should configure user access according to each person's business role.

6. Security and privacy breaches

BuildCurrent uses authentication, role and permission controls, tenant-scoped data access, database row-level security, auditability and other administrative and technical safeguards appropriate to the service. No internet service can guarantee absolute security.

Suspected privacy or security incidents are assessed, contained and documented. Where an incident creates a real risk of significant harm or otherwise triggers a legal reporting or notification requirement, BuildCurrent will notify affected parties and applicable authorities as required by law and will retain breach records for the period required by applicable law.

7. Retention and deletion

Information is retained only as long as reasonably needed to operate an active workspace, provide contracted post-service access, meet legal or accounting obligations, resolve disputes, prevent fraud or abuse, maintain security and audit records, and complete ordinary backup cycles.

Paid service currently includes a 30-day read-only period after service ends where applicable. Eligible workspace data may then be scheduled for deletion, subject to legal, accounting, fraud-prevention, audit and backup-retention requirements. Backup copies may persist temporarily until ordinary backup rotation completes.

8. Service and marketing communications

BuildCurrent may send transactional or service communications reasonably necessary to operate an account, including authentication, billing, security, support, invoice, receipt and workspace notices.

Promotional or marketing electronic messages are handled separately from mandatory service communications. Where consent is required, BuildCurrent will obtain and record the applicable consent and provide an unsubscribe mechanism. Unsubscribing from marketing does not prevent account, billing, security or other service-required messages.

9. Access, correction and privacy requests

Subject to lawful exceptions, individuals may request access to or correction of personal information under BuildCurrent's control and may ask questions about collection, use, disclosure, retention or deletion. Requests can be submitted through the Contact page.

BuildCurrent may need to verify identity and authority before fulfilling a request. Please do not send passwords, payment-card details or other credentials by email or through a privacy request.

BuildCurrent · Privacy version 2026-09-05-v2.1
HomeTermsSecurityService AgreementContact