Privacy, in plain language.

What we collect and why

When you sign in or send a brief, we receive account identifiers, your name and email, business details, the project description, and information you choose to share. The portal also keeps proposals, approvals, messages, delivery notes, and payment references. These records help us assess requests, deliver agreed work, communicate with you, and resolve billing or project questions.

Hosting and service providers may keep technical records such as IP addresses, request times, and error logs for operation and security. This website does not include advertising trackers or an analytics SDK.

Who processes the information

• Google Firebase: website hosting and account authentication.
• Supabase: private project records and the portal API.
• OpenAI: project context used to prepare private working drafts.
• Resend: email addresses and project-update notifications.
• Stripe: payment processing. Card details are entered into Stripe Checkout; our portal records payment references and amounts.

Thomas can access project records to provide the service. Portal access is restricted to the submitting account and Thomas. Our service providers process information to support their functions; this is not a promise that no service provider can access data. We do not sell project information or use it for advertising.

Providers may process information in more than one country. The current project database is hosted in Canada. Their own privacy and retention practices also apply: Google, Supabase, OpenAI, Resend, and Stripe.

AI preparation and human review

Parts of your brief, recent project messages, accepted scope, and delivery notes may be sent to OpenAI to draft questions, scope, development plans, updates, or handover notes. Drafts remain private until Thomas reviews and uses them. AI does not accept proposals, approve delivery, or independently make changes to your systems.

Please use sample data in initial briefs. Do not submit passwords, API keys, payment-card data, health information, or sensitive personal records. If your project needs special confidentiality arrangements, email Thomas before submitting its details so the approach can be agreed first.

Browser storage and the demo

Firebase uses browser storage to maintain sign-in. You can sign out or clear your browser's site data to remove that local session. The public demo uses fictional examples and keeps its interactive state in memory; reloading resets it. It does not submit its sample records to the project database.

The separate live integration example saves only three fixed fictional contacts and their tasks in dedicated database tables. These examples are shared across visitors; the form does not accept personal information or send email.

Retention and requests

We retain records while they are needed for your inquiry, project, agreed support, accounting, or a dispute. Deletion is reviewed by Thomas rather than happening automatically when a project closes. Unneeded information can be removed following that review; provider logs and backups may remain for their normal retention periods.

To request a copy, correction, or deletion of your account or project information, contact thomasvallee311@gmail.com. We will verify your identity before disclosing or changing private records and explain any information that must be retained. Deleting a browser session does not delete your project records.

Contact and changes

Privacy questions or suspected unauthorized access can be reported to thomasvallee311@gmail.com. Updates to this notice will appear here with a new date; material changes affecting an active project will be communicated to that client.