Legal
Privacy
Last updated: November 2026
What Brikar collects
To operate the builder we store the identity data returned by Google sign-in (subject ID, verified email, display name and avatar), the profile name and bio you choose, your projects and specification revisions, run metadata (stage, progress, timing, retries), and artifact metadata such as file count, checksum and size.
Generated source
Generated source files are stored in private artifact storage and are available only to the account that owns the project. Brikar does not publish your project or preview publicly. The static preview is owner-checked and served with a restrictive sandbox policy.
Payments
Pro upgrades are arranged manually through WhatsApp. When you message us, our team confirms the plan and processes the payment (19,000 IQD for 30 days) outside the Brikar app. Brikar does not receive or store your card number, PIN, or bank credentials. Any payment service used handles the transaction under its own terms and privacy policy.
Providers and logs
Prompts and generated output may be sent to the configured generation provider. Operational logs record request paths, status codes, timing, request IDs and safe run metadata. Session cookies, provider keys and full source files are not written to logs.
Retention and deletion
Projects and run records are retained while the account is active. To request account or project deletion before a self-service control is available, email hello@brikar.app. The operator will confirm the request and remove associated artifacts.
Contact
Questions about this notice: brikar.app. Security reports should include reproduction steps and must not target data you do not own.