Legal
Privacy Policy
We may update this document from time to time. When we do, we revise the version and effective date shown above.
Data controller
This policy explains what personal data AigentHub processes, why, and the rights you have. We aim to collect only what the Platform actually needs to work.
The data controller is Entornodev Multimedia SLU (VAT B04953618), Calle Gobernador José Vera Maestre, No. 34, 03600 Elda, Spain. For any privacy question or to exercise your rights, contact hello@aigenthub.dev.
What data we process
Depending on how you use the Platform, we process:
Account & authentication
- Your email address and a securely hashed password, managed by our authentication provider so you can sign in.
Profile
- Information you choose to add: display name, username, bio, an external avatar URL, country, and links you provide (website, X, GitHub, LinkedIn). This profile information is public on the Platform.
Content you create
- Agent Organizations and their details, and activity such as follows, forks, and listings.
Payments, subscriptions & payouts
- If you subscribe to Pro or buy or sell on the marketplace, we store references and status needed to run those services — such as a Stripe customer identifier, subscription status, purchase records, amounts, currency, the platform-fee split, and (for creators) the status of your Stripe Connect account. Card details are handled by Stripe; we do not store full card numbers.
Notifications & email
- Transactional emails we send (for example, welcome, purchase, sale, payout, publish, and fork notifications). To deliver them reliably, the relevant details are briefly queued in an internal email outbox and then sent through our email provider.
Connected services & agent runs
- If you connect a service (for example Google, GitHub or Slack), the credential it issues — stored encrypted — together with the account name and the permissions it reports. How Google data is handled is described in Google User Data.
- When you run an agent organization, the task you give it, the results each step produces, and the artifacts it creates. These can include information obtained from the services you connected.
Why we process it, and our legal bases
- To provide the Platform — creating and securing your account, showing your profile and content, and enabling core features. Legal basis: performance of a contract.
- To process payments, subscriptions, and payouts — checkout, Pro membership, marketplace purchases, and creator payouts. Legal basis: performance of a contract, and compliance with legal (for example, accounting) obligations.
- To run the agent organizations you choose, with the services you connect — fetching information from them when an organization you run needs it and, only where you allowed it, taking an action on them. Legal basis: performance of a contract.
- To send transactional emails tied to your activity. Legal basis: performance of a contract and our legitimate interest in keeping you informed about your account.
- To keep the Platform secure and prevent abuse. Legal basis: our legitimate interest.
- Cookies and similar storage — see the Cookie Policy. Strictly-necessary storage relies on our legitimate interest / contract; any future non-essential cookies would rely on your consent.
Google User Data
This section explains how AigentHub accesses, uses, stores, shares and protects data from your Google Account when you connect a Google service. How that data is protected is described in detail in Data security and protection.
What we access
AigentHub accesses Google data only when you connect a Google service yourself, through Google’s own sign-in, and only within the permissions you approve on Google’s consent screen. Each Google service is a separate connection with its own permissions:
- YouTube Analytics — your channel’s analytics reports, your channel’s name, and the titles of your videos. Read-only.
- Google Drive — only the files you explicitly select with Google’s file picker. AigentHub cannot see or search the rest of your Drive.
- Google Calendar — the events on calendars you own, and your free and busy times. Read-only.
- Gmail, where available — searching and reading your messages and, only if you choose read-and-write access when you connect it, creating drafts and sending messages.
AigentHub never asks Google for permission to delete your email, files, events or videos.
How we use it
Google data is used only to provide features you use and can see. When an agent organization you run — started by you, or on a schedule you set — needs information from a connected Google service, AigentHub fetches it at that moment and uses it to produce that run’s results for you. When you connect a service, we also use it to identify the account you connected and, for Drive, to confirm the files you selected.
We do not use Google data for advertising, we do not sell it, and we do not use it to develop, improve or train generalized artificial intelligence or machine-learning models.
AI providers you choose
To produce a run’s results, AigentHub sends the Google data a step needs — for example, the text of a document an organization reads — to the AI model provider you selected for your runs (currently OpenAI), using the API key you supplied. It is sent only to perform that step. That provider processes it under your own agreement with it. AigentHub does not send your Google data to any other AI provider.
People reading your data
AigentHub staff do not read your Google data unless you ask us to (for example, when you request support and agree to it), it is necessary for security purposes such as investigating abuse, or it is required by law.
What we store
- Credentials. The access and refresh tokens Google issues, encrypted (AES-256-GCM) on our servers and decrypted only on the server, for a single request. They are never shown to you or to anyone else. When you open Google’s file picker to select Drive files, a short-lived access token that reaches only the files shared with AigentHub is passed to your own browser so the picker can show your Drive; it is not stored there.
- Connection details. The Google account address or YouTube channel, the permissions granted, and the connection’s status.
- Selected Drive files. Each file’s ID, name and type. Selecting a file does not copy its contents; they are read only when an organization needs them.
- Run history. The results each step of a run produces, and the artifacts it creates, can include information taken from your Google data — for example, a summary of a document. They are kept in your run history, which is visible to you; platform administrators can access it to operate and secure the service, under the commitment above.
- Activity log. For each call to a Google service we record which capability was used, when, whether it succeeded, counts and identifiers (such as file or message IDs), and fingerprints of the request and the result — not the contents of your emails, files or events.
Disconnecting and deletion
- You can disconnect a Google service at any time in Connections. We immediately delete its encrypted tokens, your selected files and its authorizations for your organizations from our database.
- We also ask Google to revoke AigentHub’s access. Google revokes access for every Google service connected through AigentHub on that Google account at once, so if another of your AigentHub Google connections may still be using the same authorization, we leave it active on Google and tell you; it ends when you disconnect those too. If Google cannot be reached, we tell you, and you can try again or remove the connection from AigentHub only.
- You can always remove AigentHub’s access yourself in your Google Account’s third-party connections.
- Removing a file from your selection stops every organization from using it immediately. Google’s own record that you opened the file with AigentHub remains until AigentHub’s access is revoked.
- Disconnecting does not delete past run history. It is kept while your account exists and is deleted with the draft organization it belongs to; you can ask us to delete it, or your whole account, at hello@aigenthub.dev.
Limited Use
AigentHub’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and, for Google Workspace APIs, to the Google Workspace API User Data and Developer Policy.
YouTube
AigentHub uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service, and Google’s processing is governed by the Google Privacy Policy. You can also revoke AigentHub’s access to your YouTube data on Google’s security settings page.
Data security and protection
We protect personal data — including Google user data and the credentials of the services you connect — with the technical and organizational measures below. They are the measures AigentHub actually uses today. No method of transmitting or storing data is completely secure, so we cannot promise absolute security, but we work to keep your data protected and to limit who and what can reach it.
Encryption in transit
The Platform is served over HTTPS, and requests to its plain HTTP address are redirected to HTTPS. Our servers connect to Google’s APIs, to our database provider and to the other services you connect over encrypted (HTTPS/TLS) connections.
Encryption of credentials
The tokens and keys that connected services issue to AigentHub — including Google access and refresh tokens — are encrypted with AES-256-GCM, an authenticated encryption method, before they are stored. The encryption key is kept in our server configuration, separately from the database, so the stored credentials cannot be read from the database alone. Credentials are decrypted only on our servers, for the single request that needs them, and are never shown to you, to other users or to the creators of any organization.
Credentials are out of reach of the browser
Stored credentials sit in a separate table that no signed-in session can query — not even your own. Only one server-side component can read them, and it checks that the connection belongs to the person the request is for before it does. The one exception is Google’s file picker, described in Google User Data: it receives a short-lived access token limited to the Drive files you share with AigentHub, in your own browser only.
Isolation between users
Access to data in our database is enforced by row-level security policies: your connections, the Drive files you selected and your run history can be read only by your own account (run history is also visible to platform administrators, as described below). Server-side actions check again that a connection is yours before using it.
Creators never receive your credentials or data
Organizations you run use your own connections. The people who created or published those organizations never receive your credentials, your Google data or your run history, and forking or buying an organization never copies a connection.
Least privilege
- We ask Google only for the permissions each feature needs, one Google service at a time: Drive is limited to the files you select, and Calendar and YouTube Analytics are read-only.
- If Google returns an authorization with more or fewer permissions than we asked for, we refuse it and store nothing.
- The Google sign-in flow is protected against request forgery with a signed, single-use state that expires after ten minutes and is tied to your session.
Minimal records
Our activity log for connected services records identifiers and fingerprints of each request and result, not the contents of your emails, files or events. Selecting a Drive file stores only its ID, name and type.
Restricted internal access
Access to our production systems and to administrator functions is limited to authorized personnel. Administrator roles are assigned on the server and cannot be granted by users to themselves. Administrators can view run history to operate and secure the service, under the commitment in Google User Data not to read your Google data except with your agreement, for security, or when required by law.
Revocation and deletion
You can disconnect a service at any time, which deletes its stored credentials and asks Google to revoke AigentHub’s access as described in Google User Data. How long other data is kept is described in How long we keep it.
If something goes wrong
If we become aware of a personal data breach, we will notify the competent supervisory authority and the people affected where applicable data-protection law requires it. You can report a security concern to hello@aigenthub.dev.
Service providers
We rely on a small number of service providers who process data on our behalf under appropriate agreements:
- Authentication & database hosting — to store your account and Platform data.
- Stripe and Stripe Connect — to process payments, manage subscriptions, and pay creators.
- Email delivery — to send the transactional emails described above.
- Application hosting — to serve the Platform.
- The AI model provider you choose (currently OpenAI), with your own API key — to process the steps of the organizations you run, including information from connected services when a step needs it. Your agreement with that provider governs how it handles the data.
- Google, when you connect a Google service — to authorize access and to provide the data described in Google User Data.
We keep this list current as our providers are confirmed, and update this policy accordingly.
International transfers
Some of our providers may process data outside your country or the European Economic Area. Where that happens, we rely on the safeguards required by applicable data-protection law (such as adequacy decisions or standard contractual clauses). We will update this section as our providers and the applicable safeguards are confirmed.
How long we keep it
We keep personal data for as long as your account is active and for as long as needed for the purposes described here — for example, to comply with legal, accounting, and tax obligations relating to payments. When data is no longer needed, we delete or anonymize it.
- Connections and their encrypted credentials — until you disconnect them.
- Selected Drive files (ID, name and type) — until you remove them or disconnect Drive.
- Run history — while your account exists. It is deleted with the draft organization it belongs to, or when your account is deleted at your request. We do not yet apply an automatic retention period to run history; we will state it here once we do.
Your rights
You can exercise the following rights by contacting hello@aigenthub.dev:
- access to your data;
- rectification of inaccurate data;
- erasure (“right to be forgotten”);
- restriction of, or objection to, processing;
- data portability;
- withdrawal of consent, where processing is based on consent.
You can also disconnect any connected service yourself, at any time, in Connections — see Google User Data for what that does for Google services.
If you are in Spain, you also have the right to lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos, aepd.es), or with your local supervisory authority.