Quick & Dirty Fixes.ai Service-owned Gmail automation

Public service identity

Quick & Dirty Fixes.ai is an operator-managed email automation service.

Customers use the service by sending ordinary email to a service-owned Gmail inbox. The application processes messages received by that service mailbox and sends response emails from the same service-owned Gmail mailbox.

This website exists to explain the service identity, OAuth boundary, and Gmail usage for reviewers, support contacts, and future customers.

1. What Quick & Dirty Fixes.ai is

Quick & Dirty Fixes.ai is an email-in, email-out application operated through a service-owned Gmail mailbox. It is not a customer Gmail connector and it is not a multi-tenant Gmail authorization platform.

2. How it works

The current documented application flow is:

Customer Email
  → Service-Owned Gmail Inbox
  → web
  → router
  → task service
  → delivery
  → response email
  1. A customer sends an ordinary email to the Quick & Dirty Fixes.ai service mailbox.
  2. The service-owned Gmail inbox receives the message.
  3. The web service reads and prepares the inbound service-mailbox message for processing.
  4. The router service routes the request to the appropriate internal task service.
  5. The task service prepares a response.
  6. The delivery service sends the response email from the service-owned Gmail mailbox.

3. What customers do

  • Customers send normal email to the service-owned Gmail inbox.
  • Customers may include request content needed for the task they are asking the service to perform.
  • Customers receive response email from the service-owned Gmail mailbox.

4. What customers do not do

  • Customers do not complete Gmail OAuth onboarding.
  • Customers do not connect Gmail accounts.
  • Customers do not authorize Google accounts for this service.
  • Customers do not grant Gmail scopes.
  • Customers do not provide Google refresh tokens.
  • Customers do not expose their Gmail mailboxes to Quick & Dirty Fixes.ai through OAuth.

5. Service-owned Gmail model

Quick & Dirty Fixes.ai uses a service-owned Gmail mailbox as the email boundary for the application. The service mailbox receives customer emails, and the application uses OAuth authorized by the service/operator mailbox owner to process messages in that service mailbox and send responses from that same service mailbox.

OAuth access belongs to the service mailbox model. It does not belong to customer Gmail accounts.

6. Why Gmail access exists

The application uses Gmail access for two service-mailbox functions: inbound processing and outbound delivery.

Inbound processing

The application needs Gmail access to detect new service-mailbox activity, resolve mailbox history, read inbound service-mailbox messages, handle attachments when present, and prepare requests for internal processing.

Outbound delivery

The application needs Gmail send access to deliver response emails from the service-owned Gmail mailbox after internal processing is complete.

7. Contact information

For service and OAuth publication support, contact:

See the contact page for concise support contact information.