Data And Security

Is my data secure?

Using AWS Could Security, Better Building secures your data via a network architected to protect your personal information, identities, applications, and devices is provided. Better Building Support can access your private project or design data upon written request. We choose not to share any data or resell data in any form. Backups are performed daily, so the risk of data loss is very low.

Can Better Building see my project Information?

Only if you want us to. In a support capacity, we may ask to access your project information to check a design or offer further support. In these cases, we obtain your verbal consent and can access your project. Otherwise, your project data is well, your project data! Read more about our Privacy Policy.

Does Better Building support all browsers?

Our primary testing is undertaken within Chromium-based browsers. The Chromium codebase is widely used. Google Chrome, Microsoft Edge, Samsung Internet, Opera, and many other browsers are based on the code. Firefox and Safari are generally less supported but unlikely to cause significant performance or general experience issues.

Will my internet connection impact the use of Better Building?

If you are accessing Better Building from a remote location with slow connection speeds or are connecting to your phone for Wi-Fi, you may experience a reduction in performance. This would be no different for any other website. Otherwise, our Sydney-based servers are fast and secure and should ensure a great experience while working within your browser!

What does Better Building do with my data?

While Better Building is a big supporter of correct specification and has many suppliers on our platform, your data related to your projects and design remains with you. We review broad analytics from time to time, such as how many walls have steel framing vs timber or the average thickness of a wall, but this is always anonymised. We do not sell data to any entity or intend to do so. Read more about our Privacy Policy.

Can i have access to a Private Platform?

100%. For larger clients with geographically distributed teams, and particularly for those with projects exposed to high privacy requirements such as government contracts, a private platform is sometimes the most appropriate solution.

A private platform is essentially a white-labeled version of the platform, delivered specifically for individual organisations. This private platform maintains all the security benefits present in the standard platform, but additionally benefits from complete data isolation. As the provider, we cannot access the data on your private platform instance. This ensures absolute data sovereignty but also means we cannot provide direct hands-on support when you are using the platform.

That said, if you require the highest level of privacy for your projects and want full administration control across the platform, a private platform may be ideal for your needs. You will have the opportunity to customize the platform's branding and formatting to match your organisation's standards and specific reporting requirements.

What is AWS Fargate and how does our platform use it?

AWS Fargate is a serverless compute engine for containers. Our platform uses Fargate to run processing workloads without managing underlying servers. When you submit a job, Fargate automatically provisions the compute resources needed, runs your task, and scales down when complete. This means you only pay for the resources actually used during processing.

Where is my data processed and stored?

All processing occurs within AWS data centres. Your data is encrypted both in transit (via SSL/TLS) and at rest. Processing containers are ephemeral, meaning they are created for your specific job and terminated once complete. No data persists on the compute infrastructure after your task finishes.

How does serverless infrastructure affect processing times?

Fargate may introduce a brief startup delay (typically 30–60 seconds) when launching new containers, known as 'cold start' time. Once running, performance is consistent and predictable. For time-sensitive workloads, our platform maintains warm capacity to minimise delays during peak usage periods.

What happens if a processing job fails?

Fargate tasks include built-in health monitoring and retry logic. If a container fails unexpectedly, the platform automatically attempts to restart the job. You will be notified of any persistent failures, and no credits or usage will be charged for unsuccessful tasks.

How does this affect platform availability?

Our Fargate deployment spans multiple AWS Availability Zones, providing redundancy and high availability. If one zone experiences issues, workloads automatically shift to healthy zones. This architecture supports uptime targets exceeding 99.9%.

Is my data isolated from other users?

Absolutely. Each processing task runs in its own isolated container with dedicated compute resources. Containers cannot access other users' data or processes. This isolation is a core security feature of the Fargate architecture.

Can I run long-running or resource-intensive jobs?

Yes. Fargate supports tasks running for extended periods and can provision containers with substantial CPU and memory allocations. For particularly intensive workloads, you may notice this reflected in credit usage or processing costs, as resources are allocated based on job requirements.

Does using Fargate mean my data leaves my region?

No. Our Fargate deployment is region-specific. Processing occurs within the AWS region where your data is stored. Data does not transfer across regions unless you explicitly configure cross-region features (where available).

What are the benefits of serverless infrastructure for users?

Serverless infrastructure offers several advantages: you benefit from automatic scaling without capacity planning, pay only for actual compute time used, receive consistent performance regardless of platform-wide demand, and gain improved reliability through managed infrastructure. You also benefit from regular security patches and updates applied by AWS without service interruption.

Are there any limitations I should be aware of?

Fargate tasks have maximum runtime limits (configurable up to several hours for most workloads) and memory/CPU ceilings. For most standard use cases, these limits are unlikely to affect you. If you have particularly demanding requirements, contact support to discuss options including private platform deployments.

How does this relate to platform security certifications?

AWS Fargate inherits the security certifications of the underlying AWS infrastructure, including SOC 1/2/3, ISO 27001, and others. Our platform implements additional security controls on top of this foundation, including encryption, access controls, and audit logging.

Last updated

Was this helpful?