IBUILD / Privacy

IBUILD Privacy Policy

IBUILD uses one secure account. Project data may remain on the device and be securely synchronized when the user uses connected features.

Updated October 8, 2026

Privacy settings — ibuild.expert

Sign-in and your chosen language remain available. Optional website statistics and error reports are off until you agree. No advertising cookies or Google advertising/analytics tags are used.

Website only: ibuild-privacy-choice-v2 stores your choice for 180 days without an account ID. With your permission, ibuild.analytics.session stores a random ID in sessionStorage for the tab session. Reports go to IBUILD via Supabase and are linked to your signed-in account: usage up to 90 days, diagnostics up to 30 days, with daily cleanup, excluding document and form content. Supabase maintains sign-in; ibuild-language-v1 (up to one year) and verisite-lang remember the requested language. Project caches support requested features. Withdraw here at any time without signing out: future reports stop; data already sent is not deleted by withdrawal. Necessary security logs and native iPhone settings are separate. Data rights: support@ibuild.expert.

14.10.2026 · v2

01

Local and synchronized data

Some data remains in the app's protected local space. Projects, members, photos, documents, and other data used by connected features may be synchronized with the IBUILD account and stored privately in Supabase.

02

Account and connected features

An IBUILD account is required to sign in. Connected features process the email address, name, account identifier, and project, team, professional-profile, marketplace, or service information the user chooses to share.

03

Professional profiles

Information selected for the professional directory, such as name, company, location, description, contact details, and indicative pricing, may be visible to other IBUILD users. The user controls the profile content.

04

Photos, files, and notifications

IBUILD accesses only photos and files explicitly selected by the user. Synchronized content is kept private and is available only to authorized project members. Notifications are optional and may be scheduled locally or delivered by push for project events.

05

Subscriptions

Purchases in the iPhone app are processed by Apple through StoreKit; we do not receive or store payment-card details. The app verifies signed Apple proofs and sends them, together with product and transaction identifiers, the environment and purchase/expiry dates, to the IBUILD backend to verify and associate access rights with the signed-in account. For website subscription requests, we keep the plan, amount, currency, country, reference and request status for invoicing and activation verification.

06

Analytics, diagnostics, and third parties

IBUILD uses no advertising, tracking identifiers, or third-party behavioral analytics SDKs. For authenticated accounts, we record limited feature-use events and Apple MetricKit diagnostics for reliability; these records never include document, photo, chat, or form content. Apple processes purchases under its own privacy policy.

07

Retention, export, and deletion

Local data remains on the device until it is deleted or the app is uninstalled. Synchronized data remains in the account until the project or account is deleted using the available controls. Signing out does not delete the account, and exported backups must be protected separately.

08

Technical data retention

The retention threshold is 90 days for usage events and 30 days for technical diagnostics. Records older than these thresholds are removed by an automated job scheduled daily, not immediately when the threshold is reached.

09

Contact and rights

For privacy, access, or deletion questions, contact support@ibuild.expert. Do not send confidential documents unless they are necessary for a support request.