iqueda.devBack to home ↗

PRIVACY & PERSONAL AUTOMATION

Privacy Policy

Effective date: September 30, 2026

This policy covers iqueda.dev and Hermes Agent / Hermes Agent Iqueda, Jonathan Iqueda's personal productivity automations, including their Codex-based execution. The website is a public portfolio; connected-account automations are operated for the account owner's personal use, not as a public account-registration service. Contact: jonathan@iqueda.dev.

1. Website information

The portfolio does not ask visitors to sign in or provide Google account access. Hosting and delivery providers, including Railway and Cloudflare, may process connection and security information such as IP addresses, request paths, browser information and timestamps to operate and protect the site. These providers apply their own retention and privacy practices.

The site does not include advertising trackers or third-party analytics scripts. A locally stored theme preference may remember your light or dark display choice. Clicking an email, WhatsApp, social-profile or linked-product link takes you to a separate service whose privacy policy applies.

2. Google permissions and information accessed

Google access is granted through Google's OAuth consent screen. Depending on the authorized feature, personal automations may access:

OAuth permissions allow access; they do not themselves authorize unrelated actions. Messages, modifications and other external actions remain subject to the account owner's instructions and workflow approvals. Public website visitors are not required to grant these permissions.

3. How connected information is used

Connected information is used to carry out the owner's requested productivity features: preparing agendas and briefings, finding and summarizing information, managing approved calendar or email actions, updating selected spreadsheets and monitoring authorized workflows. Scheduled jobs may run without the owner being present, within their configured scope.

Google user data is not sold, used for advertising, provided to data brokers or used to assess creditworthiness. The application's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

4. Processing and sharing

Only information needed for an authorized task may be processed by the configured service providers. These can include Google for connected APIs, AI providers such as OpenAI or Anthropic for requested reasoning and summaries, hosting providers for deployed components, and Telegram for reports delivered to the configured destination. Provider involvement depends on the active workflow; connected data is not published on this portfolio.

AI processing is for the requested features, not an independent advertising or data-resale purpose. Providers' account settings and terms govern their processing and retention. Human access is limited to the operator's authorized use and necessary support, security or legal purposes. Information may also be disclosed where required by law or to protect security.

5. Storage, security and retention

OAuth access and refresh tokens are stored privately on the operator's systems. Refresh tokens renew access without asking for consent on each request. Revoking a grant or Google's account and application policies can still require renewed authorization. Credentials are not intentionally included in public pages, source-control commits or reports.

Workflow state, selected data, generated reports and diagnostic logs may be stored on the operator's devices or configured services as needed to provide the requested features, investigate failures and maintain continuity. Retention depends on the workflow and its providers; this policy does not promise a single automatic deletion interval. HTTPS, restricted credential-file permissions and limited publication of public assets help protect information, but no system guarantees absolute security.

6. Your controls and deletion requests

The account owner can pause automations, change their permissions or destinations, and revoke Google access through Google Account connections. Revocation prevents future access under that grant; it does not automatically delete previously generated files or reports.

To request access, correction or deletion of information held by the operator, contact jonathan@iqueda.dev. Requests are reviewed and carried out after appropriate identity checks, subject to technical constraints and applicable retention obligations. Copies sent to another service may also require action through that service.

7. Changes and contact

The effective date will be updated when this policy changes. Material changes to connected-data use will be disclosed and additional consent obtained when required. Questions about this policy can be sent to jonathan@iqueda.dev.