Privacy Policy

1. Who we are and our role

BuildMetrics is a structural engineering calculation and reporting service at buildmetrics.uk, offered to engineers worldwide. It is operated by Aivolux Technologies (“BuildMetrics”, “we”, “us”), a [type of business — e.g. Sdn Bhd, or sole proprietorship/enterprise registered with SSM] registered in Malaysia under registration number [SSM registration number], whose registered address is [registered address in Malaysia].

We play two different roles, and which one applies decides who you should ask about your data:

• We are the controller (a “data controller” under the PDPA) of the data we need to run your account and our business: your account and profile, sign-in and security records, billing, support enquiries, and how much of Metric and Drive mode an organisation has used.
• We are a processor for the content an organisation puts into BuildMetrics: its projects, reports, calculations, review comments, issued documents, letterhead, team lists and Knowledge Centre answers. The organisation — the engineering firm or sole practitioner whose workspace it is — is the controller of that content, and we handle it only on its instructions, under the data processing terms in our Terms of Service. If your question is about content in an organisation you belong to, start with that organisation; we will help it answer you.

Data Protection Officer. Our Data Protection Officer is [DPO name], who can be reached at [DPO email address]. You can also send privacy questions to support@buildmetrics.uk.

Representatives. Because we offer BuildMetrics to people in the United Kingdom and the European Union, we have appointed representatives there; see section 13 and section 14.

Languages. This notice is published in English and, in section 18, in Bahasa Malaysia. If the two versions differ, the English version prevails.

2. The law we follow

We are established in Malaysia, so the PDPA is our home law. When you use BuildMetrics from the United Kingdom or the European Union, the UK GDPR or the EU GDPR also applies to how we handle your data, and sections 13 and 14 explain what that adds. Wherever you live, we apply the commitments in this policy to you.

The PDPA sets seven Personal Data Protection Principles. This is how we meet each of them:

Principle	What we do
General	We process personal data only for the lawful purposes in section 5, directly related to our service, and no more than we need. We rely on your consent, which you give when you create an account after being shown this notice, or on another ground the PDPA allows — chiefly that the processing is necessary to provide the service you asked for, or to meet a legal obligation.
Notice and Choice	This policy, in English and Bahasa Malaysia, is our written notice. It is linked from the sign-up page so you see it when we first ask for your data. Section 10 sets out your choices.
Disclosure	We disclose personal data only for the purposes in this policy, to the classes of people and providers in section 8, or where the law permits or requires it.
Security	We protect personal data with the measures in section 12, and require our providers to protect it too.
Retention	We keep personal data only as long as section 7 sets out, and then delete it.
Data Integrity	We take reasonable steps to keep personal data accurate, complete, not misleading and up to date. You can update your profile at any time, and ask us to correct anything you cannot change yourself.
Access	You can see and download your account data in the app, and ask us for access to, or correction of, any personal data we hold about you (section 10).

3. What we collect

Your account

• Name and email address; your password, stored only as a one-way hash (bcrypt) that we cannot reverse.
• What you tell us when you join: professional designation (for example CEng MIStructE), main discipline, whether you practise on your own or in a firm, and a company or trading name — all shown on the reports you sign.
• If you sign in with Google: your Google account’s name, email and profile picture, as Google provides them.

Organisation content (we process it for your organisation)

• Projects, design bases, reports, calculation inputs and results, review findings and responses, issued revisions, transmittals and the people they were sent to, letterhead details, project team members and invitations by email.
• The review record: who prepared, checked, approved and issued each report, when, and the content hash they signed off — this is what lets anyone verify an issued document.
• An append-only audit log of actions in each organisation (for example “report submitted”), with the time, the person and the IP address the request came from.

Metric, the Knowledge Centre and Drive mode (BuildMetrics Advanced)

• The questions you ask Metric and where each answer came from; Knowledge Centre entries, with who suggested and who verified them; Metric’s suggestions and whether they were accepted. See section 6.
• Drive mode turns your speech into text inside your own browser (for example Google’s service in Chrome or Apple’s in Safari). We receive only the text, never audio, and we record the minutes used against the plan’s allowance.

Billing (BuildMetrics Advanced)

• Billing name, address, tax registration number (such as a VAT, GST or SST number) and email; the subscription’s status, number of seats and renewal date. Card details are collected and held by Stripe — we never see or store a card number.

Security and technical records

• Our host’s web server logs: IP address, browser user-agent, the address requested, the time and the response code.
• Failed sign-in attempts (IP address, the email address tried and the time), so we can slow down password guessing.
• Session records (stored as a hash of the token, never the token itself) and password-reset requests (also hashed, valid for one hour).
• A record of the automated reminders and digests we send (which kind, about what, and when); transmittals of issued documents are recorded in the project’s audit log with their recipients.

Support

• What you send us when you contact support, and our replies.

What you must give us, and what is optional

Your name, email address and a password (or a Google sign-in) are needed to open an account, and billing details are needed for an Advanced subscription; without them we cannot provide that part of the service. Everything else in your profile is optional.

We do not ask for sensitive personal data (special category data, such as health, religious beliefs or ethnicity), and we do not use analytics, advertising or tracking tools.

4. How we collect it

• From you — when you sign up, complete onboarding, fill in your profile, or work in a project.
• From your organisation — when a colleague adds you to a project or team, or invites you by email.
• Automatically — security and technical records, the audit log and usage counts are created as you use the service.
• From Google or Stripe — if you sign in with Google, or when Stripe tells us a payment has succeeded or failed.

5. How we use it, and why

The last column gives the lawful basis we rely on for users covered by the UK GDPR or the EU GDPR (the article numbers are the same in both). For everyone, the purposes are the same.

Purpose	Data	Lawful basis (UK and EU GDPR Art. 6)
Run your account and the service: calculations, reports, checking, issuing, verifying documents	Account, organisation content, review record	Contract (6(1)(b)); for organisation content, the organisation’s instructions as its processor
Keep accounts and the service secure: sign-in, rate limiting, detecting misuse, investigating incidents	Security and technical records, audit log	Legitimate interests (6(1)(f)) — protecting users and the service
Keep an engineering record that cannot be quietly altered	Review record, audit log, issued revisions	Contract; legitimate interests of the organisation and the people relying on its documents
Send service emails: password resets, invitations, review requests, transmittals, and the reminders and digests an organisation has switched on	Name, email, report titles and states	Contract; legitimate interests. These are service messages, not marketing
Provide Metric, the Knowledge Centre and Drive mode, and count use against the plan	Your questions and instructions, the report data needed to answer, usage counts	Contract
Take payment and keep tax records	Billing data (via Stripe)	Contract; legal obligation (6(1)(c))
Answer support requests	Name, email, what you send us	Contract; legitimate interests
Meet legal obligations and respond to lawful requests	As the request requires	Legal obligation

We do not send marketing email unless you have asked for it, and every marketing email would let you unsubscribe. We do not sell personal data, and we do not use it for advertising.

6. Metric and the Knowledge Centre (AI)

• What is sent. When you ask Metric something, or ask it to pre-check or draft, we send the question and the part of your organisation’s records needed to answer — report and project titles, calculation inputs and results, standards, and any verified Knowledge Centre answers that apply — to Anthropic, which runs the AI model. Anthropic does not use this content to train its models and keeps it only for a limited period under its commercial terms.
• Answered without AI. A question that matches an answer your organisation has verified in its Knowledge Centre is answered from there, without sending anything to Anthropic. The same question about exactly the same records may be answered from a copy of the previous answer.
• People stay in charge. Metric never enters calculation inputs or results, and never submits, checks, approves or issues a report. Anything it drafts is marked unreviewed until an engineer reviews it. Only an owner or admin can verify a Knowledge Centre answer, and their name stays on it. Metric does not make decisions about you with legal or similarly significant effects.
• Switching it off. An organisation’s owner or admin can switch Metric off for everyone in it, under Organisation → Metric & automations.

7. How long we keep it

Data	Kept for
Your account and profile	Until you delete your account (Profile & security → Delete my account). Your name, email and password are erased at once; work you signed in an organisation then shows “Former user”.
Organisation content	While the organisation uses BuildMetrics. Issued revisions, the review record and the audit log are its engineering record and are not deleted when one person leaves. If an organisation closes its account, we delete its content 90 days later, after giving it the chance to export everything.
Questions asked of Metric	12 months
Copies of Metric’s answers (reused for an identical question)	30 days
Knowledge Centre entries	Until the organisation deletes them; retired answers are kept, unserved, for the record
Failed sign-in attempts	Cleared when you next sign in successfully, and in any case after 30 days
Sessions and password-reset links	Sessions end after 30 days or when you sign out; reset links expire after one hour
Web server logs	Up to 12 months, as kept by our host
Backups	Overwritten on a rolling cycle of up to 30 days; deleted data leaves the backups when that cycle completes
Billing and tax records	[7 years from the end of the year they relate to — confirm with our accountant], as tax and company law requires
Support correspondence	3 years from the last message

8. Who we share it with

Inside BuildMetrics, organisation content is visible only to members of that organisation and to people added to a particular project — for example an outside checker. An issued document can be verified by anyone you give its issue hash to.

We use these providers (sub-processors), each under a written contract that requires them to protect the data and use it only to provide their service to us:

Provider	What for	Where
Hostinger	Web hosting, database and backups	[data centre country — confirm with Hostinger]
Resend	Sending service emails	United States
Stripe	Payments, invoices and tax (Advanced)	Ireland and United States
Anthropic	The AI model behind Metric (Advanced, only when used)	United States
Google	Optional “Sign in with Google”	United States

We give an organisation at least 30 days’ notice, by email to its owners, before adding or replacing a sub-processor that handles its content, so it can object.

We may also disclose data where the law requires or permits it (for example a court order, or a request from a regulator), to protect the safety of people or the security of the service, or to a buyer of our business, who would be bound by this policy. We do not disclose personal data for any other purpose without your consent.

9. International transfers

We are based in Malaysia and our providers work in other countries, so your data may be processed outside the country where you live — in particular Resend, Stripe, Anthropic and Google may process it in the United States, and our host processes it where its data centre is (section 8).

• Transfers out of Malaysia. We transfer personal data out of Malaysia only where the PDPA allows it: for example where the destination has a law substantially similar to the PDPA or ensures an adequate level of protection, or where another condition in the PDPA applies, such as the transfer being necessary to provide the service you asked for. We take account of the Personal Data Protection Commissioner’s guidance on cross-border transfers, keep a record of the transfers we make, and bind each provider by contract to protect the data at least as well as this policy does.
• Data of users in the UK and the EU. The extra safeguards we use are described in section 13 and section 14.

Ask us for a copy of the relevant safeguards.

10. Your rights and choices

Wherever you live, you can ask us to:

• give you access to the personal data we hold about you, and a copy of it (you can download your account data yourself under Profile & security → Download my data);
• correct it if it is inaccurate, incomplete, misleading or out of date;
• delete it (you can delete your account yourself), unless we must keep it by law or it forms part of an organisation’s engineering record;
• move the data you gave us to another service, or have it sent directly to another controller, in a structured, machine-readable format, where that is technically feasible and the formats are compatible (the data portability right introduced in the PDPA by the 2024 amendment);
• stop or limit how we use it — including stopping any direct marketing — and withdraw your consent at any time, in writing. Withdrawing consent does not affect what we did before, and if you withdraw consent to data we need to run your account, we will no longer be able to provide the service to you.

Users in the UK and the EU have further rights, set out in section 13 and section 14.

How to ask. Email support@buildmetrics.uk or our Data Protection Officer at [DPO email address]. We answer within 21 days of receiving your request (within one month for users in the UK and the EU, if that is longer), free of charge, and may ask you to confirm your identity first. If we cannot do what you ask, we will tell you why. For organisation content we act on the organisation’s instructions and will pass your request to it.

Your choices. You decide whether to sign in with Google, what optional details go in your profile, and whether to keep your account. An organisation’s owner or admin decides whether Metric and automated reminders are switched on. We never send you marketing email unless you ask for it.

11. Cookies and browser storage

BuildMetrics sets no cookies and uses no analytics, advertising or tracking. The app keeps a few items in your browser’s storage that are strictly necessary for the service you asked for. Rules such as PECR (regulation 6) in the UK and the ePrivacy Directive in the EU permit strictly necessary storage without a consent banner:

Stored	Why	Until
Sign-in session (a token, your name and email)	Keeps you signed in	You sign out, or after 30 days
Your last organisation	Opens the app where you left off	You clear your browser data
What you have already seen in a report	Shows what changed since you last opened it	You clear your browser data
Where you were heading before onboarding	Takes you there afterwards	You close the tab

If you choose Sign in with Google or pay with Stripe, those services set their own cookies on their own sites under their own policies.

12. How we protect it, and data breaches

We use practical technical and organisational measures appropriate to the risk, as the PDPA Security Principle and Article 32 of the UK and EU GDPR require, including:

• HTTPS everywhere, with HTTP Strict Transport Security; a Content Security Policy and other browser security headers.
• Passwords of at least 10 characters, checked against common choices and hashed with bcrypt; session and reset tokens stored only as hashes; sessions that end after 30 days, or 7 days unused, and on every other device when you change your password; repeated failed sign-ins locked out per account.
• Email addresses confirmed before they can join a team, check or approve; nobody added to an organisation, or to a project from outside it, without accepting.
• Access by role: people see only their own organisations and the projects they are added to, and every request is checked on the server. The person who wrote a report cannot check it, and only an approver can approve it.
• Tamper evidence: the audit log is hash-chained, issued revisions cannot be edited, and each issued document carries a hash anyone can verify.
• Secrets such as API keys kept in server configuration outside the code; production data never used for development or testing.
• Rolling backups; dependencies and security headers reviewed before each release; a security test of the service before launch.
• Access to production limited to the people who run the service, who are bound to confidentiality.

If something goes wrong. If we have reason to believe a personal data breach has occurred, we will:

• notify Malaysia’s Personal Data Protection Commissioner as soon as practicable, and within 72 hours where the Commissioner’s data breach notification guideline requires it;
• tell the people affected without unnecessary delay where the breach causes, or is likely to cause, them significant harm (the Commissioner’s guideline expects this within seven days of notifying the Commissioner), with what happened and what they can do to protect themselves;
• for users in the UK or the EU, also report it to the Information Commissioner’s Office or the relevant EU supervisory authority within 72 hours of becoming aware of it, unless it is unlikely to put anyone’s rights at risk, and tell the people affected without undue delay when the risk to them is high (UK and EU GDPR Articles 33 and 34);
• where the data is an organisation’s content, tell the organisation without undue delay so it can meet its own duties; and keep a record of every breach and what we did about it.

Found a vulnerability? Please email security@buildmetrics.uk (see also security.txt). Our security testing rules explain what you may test in good faith.

No system is perfectly secure; keep your password to yourself, use a unique one, and tell us at once if you think your account has been misused.

13. Users in the United Kingdom (UK GDPR)

If you are in the United Kingdom, the UK GDPR and the Data Protection Act 2018 apply to our handling of your personal data, in addition to the rest of this policy.

Our UK representative

We are not established in the UK, so under Article 27 of the UK GDPR we have appointed [UK representative — name] as our representative, who can be contacted at [UK representative — postal address and email] about any matter concerning your personal data.

Lawful bases

The lawful basis for each use of your data is in the table in section 5. Where we rely on legitimate interests, we have balanced them against your rights; ask us for details.

Your rights

You have the right to:

• access your personal data and receive a copy;
• rectification of inaccurate or incomplete data;
• erasure, where we have no overriding reason to keep it;
• restriction of how we use it, for example while a correction is checked;
• data portability for data you gave us under contract or consent;
• object to our use of it on the basis of legitimate interests, and to direct marketing at any time;
• not be subject to decisions based solely on automated processing that have legal or similarly significant effects on you (we make none); and
• complain to the Information Commissioner’s Office: ico.org.uk/make-a-complaint, helpline 0303 123 1113.

We answer within one month, which we may extend by up to two further months for complex requests, telling you why.

International transfers

Malaysia, where we are established, and the United States are not generally covered by UK adequacy regulations. When personal data of UK users is transferred outside the UK, we protect it as UK GDPR Chapter V requires: by the UK Extension to the EU–US Data Privacy Framework (the “UK–US data bridge”) where a US provider is certified under it, or otherwise by the International Data Transfer Agreement or the International Data Transfer Addendum to the European Commission’s Standard Contractual Clauses, together with a transfer risk assessment. Where an organisation in the UK uses BuildMetrics and we process its content as its processor, we will sign the appropriate UK transfer terms with it on request.

Marketing

We would only send marketing email with your consent or as PECR regulation 22 otherwise allows, and every message would let you unsubscribe.

14. Users in the European Union (EU GDPR)

If you are in the European Union or the wider European Economic Area, the EU GDPR applies to our handling of your personal data, in addition to the rest of this policy.

Our EU representative

We are not established in the EU, so under Article 27 of the EU GDPR we have appointed [EU representative — name] as our representative, who can be contacted at [EU representative — postal address and email] about any matter concerning your personal data.

Lawful bases

The lawful basis for each use of your data is in the table in section 5. Where we rely on legitimate interests, we have balanced them against your rights; ask us for details.

Your rights

You have the right to access, rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interests and to direct marketing at any time — as described for UK users in section 13 — and not to be subject to decisions based solely on automated processing with legal or similarly significant effects (we make none). We answer within one month, which we may extend by up to two further months for complex requests, telling you why.

You can complain to the data protection supervisory authority in the EU or EEA country where you live, where you work or where you believe the problem arose. The European Data Protection Board lists them at edpb.europa.eu.

International transfers

Malaysia, where we are established, does not have an adequacy decision from the European Commission. When personal data of EU users is transferred to a country without one, we protect it as EU GDPR Chapter V requires: by the EU–US Data Privacy Framework where a US provider is certified under it, or otherwise by the European Commission’s Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), together with a transfer impact assessment. Where an organisation in the EU uses BuildMetrics and we process its content as its processor, we will sign the Standard Contractual Clauses with it on request.

15. Children

BuildMetrics is a professional service for people aged 18 or over. We do not knowingly collect data from children; if you believe a child has given us personal data, contact us and we will delete it.

16. Changes to this policy

When we change this policy in a way that matters, we tell account holders by email at least 30 days before the change takes effect and update the date at the top. Earlier versions are available on request.

17. Contact and complaints

18. Notis Privasi (Bahasa Malaysia)

Notis ini diberikan menurut Akta Perlindungan Data Peribadi 2010, sebagaimana yang dipinda oleh Akta Perlindungan Data Peribadi (Pindaan) 2024 (“APDP”). Ia menerangkan perkara-perkara utama Dasar Privasi di atas dalam Bahasa Malaysia. Sekiranya terdapat sebarang percanggahan atau ketidakselarasan antara versi Bahasa Inggeris dan versi Bahasa Malaysia, versi Bahasa Inggeris hendaklah diguna pakai.

Siapa kami

BuildMetrics ialah perkhidmatan pengiraan dan pelaporan kejuruteraan struktur di buildmetrics.uk, yang dikendalikan oleh Aivolux Technologies (“kami”), sebuah [jenis perniagaan — cth. Sdn Bhd, atau pemilikan tunggal/perusahaan yang didaftarkan dengan SSM] yang didaftarkan di Malaysia dengan nombor pendaftaran [nombor pendaftaran SSM], beralamat di [alamat berdaftar di Malaysia]. Kami ialah pengawal data bagi data akaun, pengebilan, keselamatan dan sokongan anda. Bagi kandungan yang dimasukkan oleh sesebuah organisasi ke dalam BuildMetrics (projek, laporan, pengiraan dan rekod semakan), organisasi tersebut ialah pengawal data dan kami memprosesnya bagi pihaknya.

Data peribadi yang kami kumpul

• Akaun: nama, alamat e-mel dan kata laluan (disimpan hanya sebagai cincangan sehala yang tidak boleh diterbalikkan); jawatan profesional, disiplin utama dan nama syarikat atau nama perdagangan; jika anda log masuk dengan Google, nama, e-mel dan gambar profil akaun Google anda.
• Kandungan organisasi: projek, laporan, input dan keputusan pengiraan, ulasan semakan, dokumen yang dikeluarkan, penerima transmital, ahli pasukan dan jemputan melalui e-mel, serta log audit tindakan (termasuk masa, orang dan alamat IP).
• Metric dan Drive mode: soalan yang anda ajukan kepada Metric dan jawapannya; bagi Drive mode, kami hanya menerima teks, bukan rakaman audio.
• Pengebilan: nama, alamat, nombor pendaftaran cukai dan e-mel pengebilan. Butiran kad dikumpul dan dipegang oleh Stripe — kami tidak pernah melihat atau menyimpan nombor kad.
• Rekod keselamatan dan teknikal: alamat IP, ejen pengguna pelayar, log pelayan web, cubaan log masuk yang gagal dan rekod sesi.
• Sokongan: apa-apa yang anda hantar kepada kami dan jawapan kami.

Kami tidak meminta data peribadi sensitif, dan tidak menggunakan alat analitik, pengiklanan atau penjejakan.

Data wajib dan sukarela

Nama, alamat e-mel dan kata laluan (atau log masuk Google) adalah wajib untuk membuka akaun, dan butiran pengebilan adalah wajib untuk langganan Advanced. Butiran profil yang lain adalah sukarela. Jika anda tidak memberikan data yang wajib, kami tidak dapat menyediakan perkhidmatan tersebut kepada anda.

Sumber data

Kami memperoleh data peribadi daripada anda sendiri; daripada organisasi anda (apabila rakan sekerja menambah atau menjemput anda ke dalam pasukan atau projek); secara automatik semasa anda menggunakan perkhidmatan; dan daripada Google atau Stripe (jika anda log masuk dengan Google, atau apabila Stripe memaklumkan status pembayaran).

Tujuan kami memproses data anda

• menyediakan dan mengendalikan akaun anda serta perkhidmatan: pengiraan, laporan, semakan, pengeluaran dan pengesahan dokumen;
• menjaga keselamatan akaun dan perkhidmatan, termasuk mengesan penyalahgunaan dan menyiasat insiden;
• menyimpan rekod kejuruteraan yang tidak boleh diubah secara senyap;
• menghantar e-mel perkhidmatan (tetapan semula kata laluan, jemputan, permintaan semakan, transmital, peringatan dan ringkasan);
• menyediakan Metric, Knowledge Centre dan Drive mode — soalan anda dan bahagian rekod yang diperlukan untuk menjawabnya dihantar kepada Anthropic, yang mengendalikan model AI;
• menerima bayaran dan menyimpan rekod cukai;
• menjawab permintaan sokongan; dan
• mematuhi kewajipan undang-undang.

Kami tidak menjual data peribadi, tidak menggunakannya untuk pengiklanan, dan tidak menghantar e-mel pemasaran melainkan anda memintanya.

Kepada siapa kami mendedahkan data

• ahli organisasi anda dan orang yang ditambah ke projek tertentu (contohnya penyemak luar);
• pembekal perkhidmatan kami: Hostinger (pengehosan, pangkalan data dan sandaran), Resend (e-mel perkhidmatan), Stripe (pembayaran), Anthropic (model AI bagi Metric) dan Google (log masuk pilihan), masing-masing di bawah kontrak bertulis yang mewajibkan mereka melindungi data;
• pihak berkuasa atau mahkamah, apabila dikehendaki atau dibenarkan oleh undang-undang; dan
• pembeli perniagaan kami, yang akan terikat dengan notis ini.

Sebahagian pembekal ini memproses data di luar Malaysia, termasuk di Amerika Syarikat. Kami memindahkan data peribadi ke luar Malaysia hanya apabila syarat-syarat di bawah APDP dipenuhi, dan dengan kontrak yang mewajibkan penerima melindunginya.

Tempoh penyimpanan

Kami menyimpan data peribadi hanya selama yang perlu untuk tujuan di atas atau selama yang dikehendaki oleh undang-undang, dan kemudian memadamkannya. Tempoh terperinci dinyatakan dalam seksyen 7 versi Bahasa Inggeris.

Hak anda

Anda berhak untuk:

• meminta akses kepada data peribadi anda dan mendapatkan salinannya (anda juga boleh memuat turun data akaun anda sendiri di Profile & security → Download my data);
• meminta pembetulan data yang tidak tepat, tidak lengkap, mengelirukan atau tidak terkini;
• menarik balik persetujuan anda pada bila-bila masa melalui notis bertulis — namun jika data itu diperlukan untuk mengendalikan akaun anda, kami tidak lagi dapat menyediakan perkhidmatan kepada anda;
• meminta kami berhenti atau mengehadkan pemprosesan data anda, termasuk bagi tujuan pemasaran langsung;
• meminta data yang anda berikan kepada kami dipindahkan kepada pengawal data lain (hak kemudahalihan data), tertakluk kepada kebolehlaksanaan teknikal dan keserasian format data; dan
• memadam akaun anda sendiri di Profile & security → Delete my account.

Untuk membuat permintaan, sila e-mel support@buildmetrics.uk atau Pegawai Perlindungan Data kami. Kami akan menjawab dalam tempoh 21 hari dari tarikh permintaan diterima, tanpa sebarang caj, dan mungkin meminta anda mengesahkan identiti anda terlebih dahulu.

Pilihan anda

Anda boleh memilih sama ada untuk log masuk dengan Google dan butiran pilihan yang dimasukkan ke dalam profil anda, dan anda boleh memadam akaun anda pada bila-bila masa. Pemilik atau pentadbir organisasi boleh mematikan Metric dan peringatan automatik bagi organisasi tersebut.

Keselamatan dan pelanggaran data

Kami melindungi data peribadi dengan langkah keselamatan yang sesuai, termasuk HTTPS, kata laluan yang dicincang, kawalan akses mengikut peranan dan log audit yang tidak boleh diubah. Jika kami mempunyai sebab untuk mempercayai bahawa pelanggaran data peribadi telah berlaku, kami akan memaklumkan Pesuruhjaya Perlindungan Data Peribadi dengan seberapa segera yang praktik, dan memaklumkan anda tanpa kelewatan yang tidak perlu jika pelanggaran itu menyebabkan atau mungkin menyebabkan kemudaratan yang ketara kepada anda.

Hubungi kami