Privacy policy

Filing slip · privacy policy · effective 12 August 2026. Wire Craft Pro Pte. Ltd. ("we", "us") explains here how we handle personal data when you use wirecraftpro.life, contact the desk by mail or telephone, or enable optional functional map embeds.

Step one: identify the controller — Wire Craft Pro Pte. Ltd., 154 South Bridge Road, #06-03, Singapore 058694. Step two: note contact channels below. Step three: read each section before sending mail that contains personal information.

Data protection queries: [email protected]. General desk mail: [email protected]. Telephone: +65 6928 4173 during Mon–Fri 08:30–20:30 SGT. We respond to privacy mail during the same desk hours unless law requires faster action.

We collect minimal data: messages you send, server logs generated by routine hosting, cookie preferences stored under sg_feed_consent, and functional map interactions when you consent to Maps embeds on reach and footer map sections.

Legal bases under the Personal Data Protection Act include consent for optional cookies and maps, legitimate interests for security logs and spam prevention, and contractual necessity when you engage our desk for agreed editorial services documented in writing.

Server logs may include IP address, user agent string, requested URL, response code and timestamp. Logs rotate on a short retention schedule and are not used for behavioural profiling, advertising segments or automated scoring of individuals.

Mail you send may contain your name, organisation, telephone number, address and attachments. We store mail on encrypted systems hosted in Singapore for as long as the editorial thread requires, then archive or delete according to retention rules below.

We do not sell personal data. We do not purchase contact lists. We do not share mail content with advertisers, data brokers or analytics vendors beyond processors described here under contract.

Processors include our hosting provider and mail infrastructure vendor operating under written agreements requiring confidentiality, access controls and PDPA-aligned safeguards reviewed periodically by the desk planner and privacy contact.

International transfers occur only when you correspond from outside Singapore or when a processor maintains overseas redundancy for disaster recovery. We assess transfer safeguards before permitting cross-border storage of identifiable mail content.

Retention schedule: resolved mail threads — twelve months after closure unless law requires longer; active threads — until resolved; server logs — rolling thirty days; cookie consent records — six months aligned with banner behaviour described in cookies.php.

Your rights under applicable law may include access, correction, withdrawal of consent for optional processing, and complaint to the Personal Data Protection Commission where relevant. Write to [email protected] with requests — we may verify identity before disclosure.

We aim to respond to access and correction requests within thirty days when possible. Complex requests may require additional time; we will acknowledge receipt and note expected completion in reply mail.

Children: this site is not directed at children under thirteen. We do not knowingly collect personal data from children. If you believe a child has sent us mail, contact [email protected] and we will delete identifiable content where appropriate.

Security measures include TLS in transit, role-based access on servers, desk training on mail handling, and visitor log controls in the craft room. No security method is perfect — report concerns promptly to [email protected].

Breach notification: we will notify affected individuals and regulators when required by law and without undue delay after becoming aware of a qualifying personal data breach affecting data we control.

Automated decisions: we do not make solely automated decisions with legal or similarly significant effects about individuals based on site browsing, cookie choices or server log patterns alone.

Third-party maps: Google Maps may set cookies when you enable functional consent. See cookies.php and Google's published policy for details on map provider processing. Rejecting functional consent shows placeholders instead of iframes.

Marketing communications: we do not send bulk marketing mail from this domain. Desk replies relate to threads you initiate. If that practice changes, this policy will update first and optional opt-in will be required.

CCTV and visitor logs in the craft room may record names and visit times for security. Visitor data is kept only as long as needed for access control and is not published on the site.

Employee and contractor data is handled under separate internal notices not published here. Contractors with desk access sign confidentiality undertakings aligned with this policy.

Changes: we update this policy on this page with a revised dateModified field in JSON-LD. Substantive privacy revisions are flagged on the homepage mono strip for seven days and summarised in the cookies notice when consent categories are affected. Continued use after an update constitutes acknowledgement of the revised notice where law permits.

Independent editorial company: Wire Craft Pro describes coverage methods on this site only. We do not promise particular stories, rankings or commercial outcomes. Engagement terms for specific desk work are agreed in writing separately from this privacy notice.

Contact summary: Wire Craft Pro Pte. Ltd., [email protected], 154 South Bridge Road, #06-03, Singapore 058694. Include enough detail in access requests for us to locate your thread without exposing third-party data in reply mail.

Telephone calls to the published desk number may be logged with time and subject summary for follow-up. Call recordings are not made unless you are notified in advance for a specific agreed briefing.

Public interest: we may retain correspondence longer when ongoing editorial threads require continuity or when law mandates retention for disputes. Deletion requests are assessed against those duties before we erase identifiable fields.

Aggregated statistics about site traffic may be computed from server logs without identifying individuals. We do not publish visitor analytics on this domain and do not enable analytics cookies by default.

Data minimisation: mail forms are not used on this site — you choose what to include in outbound mail. Please do not send national identification numbers or financial account numbers; we will delete such content if received inadvertently.

Processor changes: if we change hosting or mail vendors, we update this policy and assess continuity of safeguards before migration. Material processor changes receive a homepage mono strip note when they affect optional map or cookie behaviour.

Questions about this policy that are not answered here should go to [email protected] with subject Privacy policy query. General editorial mail should use [email protected] instead to keep threads sorted correctly.

Lawful access requests from authorities are handled by the privacy contact with legal review when required. We document what was disclosed, to whom and under what authority unless law prohibits notification to the affected individual.

Research or academic requests for aggregated desk methodology may be answered with public pages already on this site. Requests for internal logs or mail content require a lawful basis and identity verification.

Newsletter or mailing lists: we do not operate bulk recurring mail from this domain at present. If that changes, opt-in and unsubscribe will be documented here before collection begins.

Device fingerprinting: we do not use fingerprinting techniques beyond routine server logs described above. Optional analytics, when enabled, is documented in cookies.php and remains off by default.

Sensitive categories: please do not send health, biometric or financial account data unless strictly necessary for a thread you initiate. We delete unnecessary sensitive fields when identified in inbound mail.

Data portability: where applicable, you may request a copy of personal data you provided in structured form. We respond via [email protected] after verifying identity and scoping the request to data we control.

Complaints to regulators: you may contact the Personal Data Protection Commission if you believe processing violates applicable law. We prefer you contact us first so we can resolve concerns when possible.

Version history: substantive privacy revisions retain the prior effective date in desk archives even after this page updates. The dateModified JSON-LD field reflects the latest published version only.

Joint controllers: we do not jointly control personal data with third-party advertisers on this site because advertising cookies are not deployed. Map provider processing is described under third-party maps above.

Direct marketing opt-out is not applicable while we send no marketing mail. Desk replies to your initiated threads are transactional correspondence, not campaigns.

Accuracy of personal data you provide remains your responsibility when you send mail. We will correct our copies when you notify [email protected] with evidence of error.

Desk visitors: sign-in sheets may record name, organisation and visit time for building security. Sheets are kept separately from editorial mail archives and destroyed on a shorter schedule than thread mail.

Anonymous browsing of static pages does not require account creation. We do not operate login portals on wirecraftpro.life at this time.

Vendor assessments for processors repeat annually or after material contract change. Summaries remain internal; readers see outcomes as continued service and updated notices on this page.

De-identification: when we publish desk methodology examples, we redact names and mail addresses from sample threads shown in training — public site text uses generic examples only.

Retention disputes: if you disagree with our retention decision, write to [email protected] with thread references — we explain the legal or editorial basis in reply.

Cookie banner interactions are not linked to editorial mail threads — consent logs and mail archives are stored in separate systems with separate retention rules described in each section above.