How Tower Rush Module keeps your data inside the prefab workflow

1. Introduction

Tower Rush Module designs modular systems and digital touchpoints that collect only what we need to quote, engineer, and support your project. This document describes categories of information we process, why those categories exist, how long they linger in our systems, and the safeguards that surround them. It is written for visitors, prospective clients, and anyone who fills out a form or exchanges files with our team.

2. Information We Collect

Depending on how you interact with us, we may process:

• Identity and contact fields: Name, company role, and email address that you type into inquiry forms, file shares, or signature blocks. We treat free-text project descriptions as part of this bundle when they describe personnel responsibilities.
• Technical and usage signals: Browser capabilities, session duration, referral pages, coarse device type, and error diagnostics that help us keep forms reliable. We avoid collecting positioning telemetry or routing identifiers beyond what your browser exposes for basic compatibility.

3. How We Use Your Information

Tower Rush Module uses your data to:

• Provide, operate, and maintain our services.
• Improve user experience and offer tailored customer support tied to modular packages you asked about.
• Communicate important updates, technical notices, and administrative messages.
• Ensure compliance with legal obligations and prevent fraudulent activity.

4. Data Retention and Sharing

We retain personal information only as long as necessary to fulfill the purposes outlined in this policy or as required by law. We do not sell your personal data. We may share your information with trusted third-party service providers who assist us in operating our business—hosting, email delivery, CRM pipelines, and document signing—provided they agree to keep your information confidential and process it under instructions that mirror this policy.

5. Security Measures

We implement industry-standard security protocols to protect your data from unauthorized access, alteration, or destruction. Access to production systems is limited to trained staff, segmented by role, and reviewed when projects close. However, no method of transmission over the internet is completely secure, and we cannot guarantee absolute security.

6. Your Rights

You have the right to access, correct, or delete your personal information held by Tower Rush Module, subject to legal exceptions such as audit trails we must preserve. If you wish to exercise any of these rights, contact us using the email address listed in the final section so we can verify your request and respond within a reasonable timeframe.

7. Cookies, storage keys, and analytics hygiene

Our web properties may set first-party cookies to remember form progress, maintain authenticated admin sessions, or store UI preferences such as reduced motion. We may also rely on privacy-preserving analytics that aggregate traffic patterns without building cross-site profiles of named individuals. You can clear cookies through your browser settings; doing so may reset certain conveniences but will not remove records we already stored securely on the server side for active projects.

Third-party embeds—such as hosted PDF viewers or specification widgets—only load when you interact with the surrounding module, and each vendor maintains its own notice. We configure embeds to defer nonessential scripts until you opt in through a click or scroll, which limits passive fingerprinting while keeping specification sheets readable.

8. Model documentation, BIM handoffs, and file retention

When you upload CAD layers, structural sketches, or clash reports, those files may contain metadata such as author tags or revision history embedded by your authoring tool. We strip marketing identifiers where feasible, store originals in encrypted buckets, and generate derivative previews that strip embedded macros. Retention follows the project lifecycle: active builds keep full fidelity until commissioning sign-off, after which we archive compressed packages for the statutory period required for warranty disputes unless you request earlier deletion that does not conflict with our obligations to insurers.

If a subcontractor needs the same package, we issue time-limited download links with watermarking rather than bulk forwarding attachments, which reduces uncontrolled redistribution and gives us an audit trail if files resurface later.

9. Marketing, newsletters, and silent opt-outs

We do not purchase mailing lists or append third-party demographic segments to your profile. If you join a product update list, every message includes a clear unsubscribe control that processes within days, not weeks. Transactional notices—such as safety recalls affecting a module family you purchased—may still reach you because they are tied to contractual performance rather than advertising.

Internal training uses anonymized excerpts from support tickets, but names, company identifiers, and file names are redacted before those excerpts enter curriculum decks.

10. Automated scoring, human review, and escalation

Some intake forms run lightweight rules that flag incomplete structural loads or mismatched unit systems before a human estimator opens the ticket. Those rules are deterministic—not opaque machine-learning credit scores—and every flag can be overridden after conversation with you. No automated decision denies service outright; at most it schedules a clarification call.

If we ever introduce richer statistical models for capacity planning, we will publish an addendum describing logic categories, confidence thresholds, and how to obtain meaningful human intervention before any adverse effect materializes.

11. Contact

Questions about this policy or requests to exercise privacy rights should go to:

• Email: modular@towerrush.com