QCA

Legal

Privacy Policy

Draft prepared:  ·  qcacos.com

DRAFT — Pending Founder Approval. This document is prepared for founder review and has not been formally adopted as binding policy. Sections marked with a notice are subject to change before publication. Do not rely on this document as a statement of current practice until it is approved and dated as effective.

Scope

This policy applies to the QCA Portfolio Communications system — the component of QCA's engineering engagement platform that sends and receives email through the [email protected] Gmail account. It describes what email data is accessed, how it is used, where it is stored, and how it is protected.

This policy covers communications between QCA and clients enrolled in QCA's custom engineering service. It does not cover the trading, intelligence, or terminal products.

Gmail API Use

The QCA Portfolio system accesses the Gmail API using OAuth 2.0 authorization granted to the [email protected] account. Two scopes are authorized:

  • gmail.send — used to send project updates, milestone notifications, decision requests, reminders, and escalation notices to engineering clients.
  • gmail.modify — used to read unread inbox messages, process client replies, and mark messages as read after they are ingested.

No other Gmail scopes are requested or used. The system does not access email drafts, sent mail history prior to the current engagement, contacts, calendar, or any Google service other than Gmail.

Information Accessed

For each email sent or received through the portfolio system, the following fields are read and stored:

  • Sender and recipient email addresses
  • Email subject line
  • Plain-text email body
  • Message-ID and In-Reply-To headers (used for conversation threading)
  • Delivery timestamp

Email attachments, HTML formatting, CC/BCC fields, and account-level metadata (labels, starred state, filters) are not accessed or stored.

How Information Is Used

Email content is used exclusively to manage active engineering engagements. Specific uses are:

  • Sending structured progress updates and notifications to the client contact on record
  • Classifying inbound client replies as approvals, clarification requests, scope-change requests, or general replies
  • Matching inbound messages to the correct engagement record using email threading headers or sender address
  • Routing scope-change requests and unresolved clarifications to the project management queue for human review

Email data is not used for advertising, profiling, training machine learning models, analytics unrelated to the specific engagement, or any purpose beyond managing the engineering project the communication relates to.

Storage and Security

Communication records are persisted to a JSON file (portfolio_comms.json) on Railway, the managed hosting platform that operates the QCA system. Records are not replicated to external databases, third-party analytics services, or advertising networks.

Access to stored records requires authentication. The QCA system runs behind HTTPS with TLS enforced at the platform level. Communication with the Gmail API is made exclusively over HTTPS.

Backups

The /data/ directory on Railway — which includes portfolio_comms.json — is backed up daily to an encrypted Backblaze B2 object storage bucket using Restic. Backup snapshots are encrypted with a passphrase and are not accessible without it.

Important: As of this draft, no automated snapshot expiry or pruning policy has been configured. Encrypted backup snapshots accumulate indefinitely until manually pruned. This means that even after a client's active communication records are deleted from the live system, encrypted copies of those records may persist in backup storage for an indefinite period.

A formal backup retention policy (including automated pruning) is under consideration. This section will be updated when a policy is implemented and operational.

Retention

The standard retention period described below is proposed and has not yet been formally adopted or implemented as enforceable policy. It is presented here for founder review. Do not treat it as a binding commitment.

Communication records in the active system are retained for the duration of the engineering engagement and for a period reasonably necessary for project documentation, dispute resolution, and legal compliance obligations.

Proposed standard (pending approval): Active communication records will be deleted within 24 months after formal engagement closure, unless a longer retention period is required by applicable law, an active dispute, a contractual obligation, or a regulatory requirement.

Regardless of active-record deletion, encrypted backup snapshots containing communication records may persist beyond this period until a backup retention policy is implemented and applied. See Backups above.

Legal and contractual exceptions — including records subject to litigation hold, tax records, or other statutory requirements — are retained for the minimum period required by applicable law and then deleted.

Deletion Requests

Clients may request deletion of their communication records before the standard retention period expires. Requests are processed manually by the founder. Upon a validated request:

  • Active records in the live system will be deleted.
  • Encrypted backup snapshots containing the records may persist until the next scheduled or manual prune operation, as described in Backups above. The timeline for backup removal cannot be guaranteed until an automated pruning policy is in place.
  • Records subject to a legal hold or statutory retention obligation will not be deleted until the hold is lifted or the legal obligation expires.

Sharing

Email content and communication records are not sold, rented, or transferred to any third party. They are not disclosed to advertising networks, data brokers, or analytics providers. The only external systems that process the data are Gmail (as sender/recipient) and Railway (as the hosting platform). Backblaze B2 stores encrypted backup snapshots but cannot decrypt them.

Your Rights

Clients enrolled in a QCA engineering engagement may request:

  • A copy of the communication records associated with their engagement
  • Deletion of their communication records (subject to legal and backup limitations above)
  • Correction of inaccurate information in their engagement record

To make a request, contact [email protected] with the subject line Privacy Request.

Google API Limited Use Disclosure

QCA's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy , including the Limited Use requirements.

Specifically: Gmail data accessed through the Google API is used only to deliver the engineering communication service described above. It is not used to serve advertising, is not used to determine creditworthiness, is not shared with or transferred to any third party except as described in this policy, is not used for any purpose that a reasonable person would consider not in keeping with providing the service, and is not made available for any human reading of the data except where necessary to deliver the service, investigate a security incident, or comply with applicable law.

Changes to This Policy

Material changes to this policy will be reflected with an updated effective date. The current version will always be available at qcacos.com/privacy.

Contact

Privacy questions and data requests: [email protected]