Security pack

Vendor security questionnaire

The questions a security review usually asks, answered from Agined's own documents. Each answer links to the document it comes from. If your form asks something not covered here, send it to us.

Read the whitepaper Send us your questionnaire

Operated by Avonao, Inc.Answers describe the service todayNo certification is claimed

Organisation

#	Question	Answer	Source
1.1	Which company provides the service?	Avonao, Inc., a Delaware corporation (entity file number 10121895), publishes Agined and is the contracting company.	/legal/imprint
1.2	Where are legal notices sent?	To the Delaware legal address in the Imprint. The San Francisco mailing address is for general correspondence only and is not treated as the legal address.	/legal/imprint
1.3	Do you have an EU representative or data protection officer?	Yes. NUICORN, Berlin, is the Article 27 GDPR representative and the data protection officer for the European Union.	/legal/privacy-policy
1.4	Who do we contact about security and privacy?	Security: security@agined.com. Privacy: privacy@agined.com. Vulnerability reports can also be sent anonymously through the report form.	/trust
1.5	Do you hold a security certification or attestation report?	This site does not claim one. The compliance posture lists what is in place, what is on request and what is not offered.	/trust#compliance
1.6	Which law governs the agreement?	Delaware law. The parties first try to settle a dispute in good faith for 30 days, after which the courts in New Castle County, Delaware have exclusive jurisdiction.	/legal/terms-of-service

Access control

#	Question	Answer	Source
2.1	How is every request authenticated?	Each request carries a credential that the gateway resolves to a workspace before any action code runs. API keys, personal access tokens and session tokens are stored only as SHA-256 hashes and compared in constant time.	/legal/data-processing-addendum
2.2	Can credentials be scoped, rotated and revoked?	Yes. Keys can be scoped to read, write or manage groups and to specific tools, expire, be rotated with a grace period, or be revoked with effect on the next request.	/legal/data-processing-addendum
2.3	Can access be restricted by network address?	Yes. Tokens can be bound to an IP range, and the gateway has an IP allow-list step.	/legal/data-processing-addendum
2.4	Do you store user passwords, and how do users sign in?	No. The service holds no passwords and no sign-in methods. Sign-up and sign-in happen at Avonao ID, which sends the service OpenID Connect claims.	/legal/data-processing-addendum
2.5	How long do dashboard sessions last?	Sessions are HttpOnly, Secure and SameSite=Lax, with a 12-hour absolute lifetime and a 30-minute idle timeout.	/legal/data-processing-addendum
2.6	Is access role-based?	Yes. Organisation and workspace roles limit who can manage keys, members, billing and data, and each action declares the permissions it needs.	/trust/security-pack/whitepaper#access
2.7	How are tenants isolated?	The gateway decides the workspace and forwards it in headers covered by a signature only Agined's services can produce; the regional service rejects a request without it. Every read and write carries the workspace id, and a regional service reads only its own region's database.	/legal/data-processing-addendum
2.8	Can a human be required before an agent action runs?	Yes. An action set to always ask is refused with an approval handle and runs only after a person answers. If an approval cannot be stored, the call is refused.	/trust/security-pack/whitepaper#approval
2.9	Can a customer stop an agent quickly?	Yes. A tenant can switch off one caller, one action, one domain or its whole surface with its kill switch, and can quarantine a counterparty. Both are checked on every call.	/trust/security-pack/whitepaper#architecture
2.10	Which limits apply to agent calls?	Per-minute rate limits, daily and monthly call caps, a plan allowance of production actors and a per-actor monetary ceiling, all applied before the tenant's backend is called.	/trust/security-pack/whitepaper#architecture
2.11	Who at Agined can access production and customer data?	Only the personnel who deploy and operate the service, bound by confidentiality. Support staff cannot open a session as a customer; they see a workspace only through time-limited access the customer grants, and each such session is recorded in the workspace audit log.	/legal/data-processing-addendum

Data protection and residency

#	Question	Answer	Source
3.1	Where is customer data stored?	In one of seven Cloudflare regions chosen when the workspace is created: US East, US West, Europe Central, Europe West, Europe North, Asia-Pacific or Oceania. Free is US West. A workspace stays in its region.	/legal/data-act
3.2	Is any data stored under an EU jurisdiction guarantee?	Yes. The three European regions store data under Cloudflare's EU jurisdiction, so it stays in the EU and Cloudflare chooses the datacenter.	/legal/data-act
3.3	Can we have a dedicated database?	On Scale, Enterprise and the isolation add-on, the workspace's own Amazon Aurora database on AWS in the AWS region the workspace chose. On Pro, Pro+ and Team, the workspace's own separate store on Cloudflare. Free and Starter use the region's shared Cloudflare D1 database.	/legal/data-act
3.4	Is a call ever answered from another region?	No. A regional service reads only its own region's database, and a call is never answered from another region.	/legal/data-processing-addendum
3.5	How much customer content do you store?	Tools that attest content store its hash, not the content. Relayed request and response bodies are not stored unless you turn on body retention. People in record chains are identified by a salted HMAC.	/legal/data-processing-addendum
3.6	How long is data kept?	Receipts follow the plan window: Free 7 days, Starter 30, Pro 90, Pro+ 180, Team 365, Scale 730; Enterprise by contract. Operational logs up to 30 days. The security audit log is retained through erasure.	/legal/data-processing-addendum
3.7	What happens to data when we leave?	You can export and delete at any time at no charge. After account deletion there is a 30-day grace period with nothing erased; then workspace data is erased, with listed exceptions such as receipts inside their window and records the law requires. Deletion is confirmed in writing on request.	/legal/data-processing-addendum
3.8	Can we export our data, and in which format?	Yes. The receipt export is a ZIP with the receipts, the key set, the verify.mjs script, a manifest and SHA256SUMS. The EU Data Act page lists each exportable data set and its format.	/legal/data-act
3.9	How do you handle government access requests?	Each request is checked for its legal basis, scope and conflict with EU law, and challenged where it is unlawful or too broad. Agined discloses the minimum required and tells you first unless the law forbids it.	/legal/data-act

Encryption

#	Question	Answer	Source
4.1	Is data encrypted in transit?	Yes. Traffic between you and the service uses TLS.	/legal/data-processing-addendum
4.2	Is data encrypted at rest?	Data at rest in Cloudflare D1 is encrypted by Cloudflare with AES-256, as Cloudflare documents.	/legal/data-processing-addendum
4.3	How are third-party credentials you hold for us protected?	Credentials and webhook secrets stored with a tool are sealed with AES-256-GCM, bound to your workspace and the endpoint, and are never returned or written to a receipt.	/legal/data-processing-addendum
4.4	Which algorithm signs your evidence, and who holds the keys?	Ed25519 over RFC 8785 canonical JSON. One key per data region, seven in all, held as encrypted Cloudflare Worker secrets and used only by the receipt service. No API route returns a private key.	/legal/key-management
4.5	How are signing keys rotated?	By a manual key ceremony run by Agined, with no schedule. No production signing key has been rotated so far. Owners and admins can record a rotation request.	/legal/key-management
4.6	What is your post-quantum position?	No receipt carries a post-quantum signature today. Receipts name their key inside the signed bytes so that a new algorithm can be added without breaking old receipts, and the path to ML-DSA is published without dates.	/legal/post-quantum

Logging and monitoring

#	Question	Answer	Source
5.1	Is every action call recorded?	Yes. Successful calls and refusals are appended to a per-workspace hash chain. If the audit write fails, the gateway answers 503 whatever the handler did. A call that reaches a tenant's host also leaves a fact on the tenant's chain, and the response carries a proof URL only when that fact was written.	/trust/security-pack/whitepaper#architecture
5.2	Can the logs be tampered with unnoticed?	Each audit entry hash covers the entry and the previous entry's hash, so a record cannot be removed from the middle of a chain unnoticed. Receipt tables reject updates and deletes by database trigger.	/trust/security-pack/whitepaper#evidence
5.3	Which security events are logged, and can we read them?	Sign-ins, key and role changes, denied access, receipt deletion and redaction and support sessions go to an append-only audit log with source IP address and user agent. Workspace admins read it in the dashboard.	/legal/data-processing-addendum
5.4	How long are logs retained?	Operational logs for up to 30 days. The security audit log is retained through erasure, with a person's identifier replaced where erasure is required.	/legal/data-processing-addendum
5.5	How do you monitor availability?	The status page checks each component every minute and keeps the history. The Enterprise SLA measures downtime from those checks.	/status
5.6	Do you detect abusive or anomalous agent behaviour?	Runtime detection on agent calls raises flags for review by a person, and a live breaker can raise an action to require human approval. A breaker can only tighten, never loosen.	/legal/data-processing-addendum

Incident response

#	Question	Answer	Source
6.1	When will you tell us about a personal data breach?	By email to the account owner without undue delay and within 72 hours of becoming aware, in phases if everything is not yet known.	/legal/data-processing-addendum
6.2	What will the breach notice contain?	The nature of the breach, categories and approximate numbers of data subjects and records, likely consequences, measures taken or proposed and a contact point, to the extent known.	/legal/data-processing-addendum
6.3	How are incidents communicated?	Incidents are published on the status page while they happen and kept in its history. Enterprise customers can subscribe to incident notices by email.	/legal/enterprise-sla
6.4	What is your plan if a signing key is compromised?	Handled as a security incident: stop signing with the key and move the region to a new key, publish a notice naming the key id, email the affected workspace owners, and decide whether the key stays published. There is no revocation list.	/legal/key-management
6.5	How fast does support respond for Enterprise?	Every report is acknowledged within 1 business hour (Monday to Friday, 9:00 to 17:00 US Eastern). These are acknowledgement targets, not resolution targets.	/legal/enterprise-sla

Vulnerability management

#	Question	Answer	Source
7.1	How do we report a vulnerability?	Through the report form, which accepts anonymous reports, or at security@agined.com.	/legal/responsible-disclosure
7.2	What response targets do you commit to?	Acknowledgement within 3 business days, initial assessment within 10 business days, updates at least every 14 days, and a fix or mitigation aimed at 30 days for critical and high severity and 90 days for lower. These are targets, not guarantees.	/legal/responsible-disclosure
7.3	Is there a safe harbor for researchers?	Yes, for good-faith research that follows the policy. It covers Agined's systems only. We ask for 90 days before public disclosure, by agreement.	/legal/responsible-disclosure
7.4	Do you run a bug bounty?	No. We do not pay monetary rewards; we credit reporters by name or handle if they wish.	/legal/responsible-disclosure
7.5	How do you protect against requests to internal addresses (SSRF)?	A filter refuses non-HTTP schemes, localhost, internal-looking names and private and reserved IP ranges, at submission and again when a scheduled check runs; relay tools never follow redirects, and capture tools check every hop. We do not describe the filter as a complete defence.	/legal/data-processing-addendum

Sub-processors

#	Question	Answer	Source
8.1	Do you publish your sub-processors?	Yes, with each provider's purpose, location, personal data involved and safeguards. It is Annex 3 of the DPA.	/legal/subprocessors
8.2	Who are the main ones?	Cloudflare (hosting, databases, storage, email delivery), Amazon Web Services (Amazon Aurora for Scale, Enterprise and the isolation add-on), Avonao Billing with Stripe (billing), Anthropic (assistants), Resend and Twilio, plus failover models and consent-gated analytics and fonts as listed.	/legal/subprocessors
8.3	How are we told about changes?	At least 30 days before a new sub-processor starts, owners of every workspace are emailed and the page is updated with the new date. An urgent replacement is notified as soon as possible with the same rights.	/legal/subprocessors
8.4	Can we object?	Yes, on reasonable data protection grounds within the notice period. If the objection cannot be met, you may terminate the affected service before the change and receive a refund of unused prepaid fees.	/legal/subprocessors
8.5	Is customer data used for advertising or resold?	No. We use no sub-processor for advertising or data resale, and our affiliates do not process the service's personal data.	/legal/subprocessors
8.6	How are international transfers covered?	By the Standard Contractual Clauses, the UK Addendum and the Swiss adaptations, which form part of the DPA and our agreements with sub-processors.	/legal/data-processing-addendum

Business continuity

#	Question	Answer	Source
9.1	Do you commit to an uptime level?	Enterprise plans with a signed order form: at least 99.9% monthly, with service credits of 10%, 25% or 50% of the monthly fee by shortfall. Self-serve plans carry no uptime commitment.	/legal/enterprise-sla
9.2	How are databases backed up and restored?	Cloudflare D1 Time Travel restores a database to any minute of the last 30 days. Agined keeps no other backup copy of those databases.	/legal/continuity
9.3	Can a bad deployment be reversed?	Yes. Deployments are versioned and can be rolled back without touching data.	/legal/data-processing-addendum
9.4	Does our evidence depend on your availability?	No. A receipt plus the public key it names verifies offline with standard cryptography, whether or not Agined is available or exists.	/legal/continuity
9.5	What happens if Agined stops operating?	At least 30 days' notice by email and on the status page, exports kept working for that period, the final key set published somewhere independent of Agined, and signing stopped before publishing stops. There is no third-party escrow of keys or source code today.	/legal/continuity

Privacy and legal

#	Question	Answer	Source
10.1	Is there a Data Processing Addendum, and do we need to sign it?	Yes. It is part of the Terms and applies on acceptance; no signature is needed.	/legal/data-processing-addendum
10.2	How do we exercise privacy rights?	Through the privacy request form, which covers GDPR and US state-law requests, or at privacy@agined.com.	/opt-out
10.3	Can we audit you?	First through documentation and written answers to a reasonable security questionnaire, answered within 30 days. If that is not enough, or after a breach or at a supervisory authority's request, you may audit once in 12 months on 30 days' notice, on the terms of DPA section 9.	/legal/data-processing-addendum
10.4	Do analytics and fonts load without consent?	No. Google Analytics loads only after you allow Statistics, and Adobe Fonts only after you allow Fonts in the EU, EEA, Switzerland and UK.	/legal/subprocessors
10.5	How does the EU AI Act apply?	The page says which part of the service is an AI system, how the assistant meets the transparency rules, and offers an Article 25(4) agreement for customers who build Agined into a high-risk AI system.	/legal/eu-ai-act
10.6	Where do I report illegal content or misuse?	Through the abuse report page, under the Digital Services Act notice process and the Acceptable Use Policy.	/abuse

Security pack

Vendor security questionnaire

The questions a security review usually asks, answered from Agined's own documents. Each answer links to the document it comes from. If your form asks something not covered here, send it to us.

Read the whitepaper Send us your questionnaire

Operated by Avonao, Inc.Answers describe the service todayNo certification is claimed

Organisation

#	Question	Answer	Source
1.1	Which company provides the service?	Avonao, Inc., a Delaware corporation (entity file number 10121895), publishes Agined and is the contracting company.	/legal/imprint
1.2	Where are legal notices sent?	To the Delaware legal address in the Imprint. The San Francisco mailing address is for general correspondence only and is not treated as the legal address.	/legal/imprint
1.3	Do you have an EU representative or data protection officer?	Yes. NUICORN, Berlin, is the Article 27 GDPR representative and the data protection officer for the European Union.	/legal/privacy-policy
1.4	Who do we contact about security and privacy?	Security: security@agined.com. Privacy: privacy@agined.com. Vulnerability reports can also be sent anonymously through the report form.	/trust
1.5	Do you hold a security certification or attestation report?	This site does not claim one. The compliance posture lists what is in place, what is on request and what is not offered.	/trust#compliance
1.6	Which law governs the agreement?	Delaware law. The parties first try to settle a dispute in good faith for 30 days, after which the courts in New Castle County, Delaware have exclusive jurisdiction.	/legal/terms-of-service

Access control

#	Question	Answer	Source
2.1	How is every request authenticated?	Each request carries a credential that the gateway resolves to a workspace before any action code runs. API keys, personal access tokens and session tokens are stored only as SHA-256 hashes and compared in constant time.	/legal/data-processing-addendum
2.2	Can credentials be scoped, rotated and revoked?	Yes. Keys can be scoped to read, write or manage groups and to specific tools, expire, be rotated with a grace period, or be revoked with effect on the next request.	/legal/data-processing-addendum
2.3	Can access be restricted by network address?	Yes. Tokens can be bound to an IP range, and the gateway has an IP allow-list step.	/legal/data-processing-addendum
2.4	Do you store user passwords, and how do users sign in?	No. The service holds no passwords and no sign-in methods. Sign-up and sign-in happen at Avonao ID, which sends the service OpenID Connect claims.	/legal/data-processing-addendum
2.5	How long do dashboard sessions last?	Sessions are HttpOnly, Secure and SameSite=Lax, with a 12-hour absolute lifetime and a 30-minute idle timeout.	/legal/data-processing-addendum
2.6	Is access role-based?	Yes. Organisation and workspace roles limit who can manage keys, members, billing and data, and each action declares the permissions it needs.	/trust/security-pack/whitepaper#access
2.7	How are tenants isolated?	The gateway decides the workspace and forwards it in headers covered by a signature only Agined's services can produce; the regional service rejects a request without it. Every read and write carries the workspace id, and a regional service reads only its own region's database.	/legal/data-processing-addendum
2.8	Can a human be required before an agent action runs?	Yes. An action set to always ask is refused with an approval handle and runs only after a person answers. If an approval cannot be stored, the call is refused.	/trust/security-pack/whitepaper#approval
2.9	Can a customer stop an agent quickly?	Yes. A tenant can switch off one caller, one action, one domain or its whole surface with its kill switch, and can quarantine a counterparty. Both are checked on every call.	/trust/security-pack/whitepaper#architecture
2.10	Which limits apply to agent calls?	Per-minute rate limits, daily and monthly call caps, a plan allowance of production actors and a per-actor monetary ceiling, all applied before the tenant's backend is called.	/trust/security-pack/whitepaper#architecture
2.11	Who at Agined can access production and customer data?	Only the personnel who deploy and operate the service, bound by confidentiality. Support staff cannot open a session as a customer; they see a workspace only through time-limited access the customer grants, and each such session is recorded in the workspace audit log.	/legal/data-processing-addendum

Data protection and residency

#	Question	Answer	Source
3.1	Where is customer data stored?	In one of seven Cloudflare regions chosen when the workspace is created: US East, US West, Europe Central, Europe West, Europe North, Asia-Pacific or Oceania. Free is US West. A workspace stays in its region.	/legal/data-act
3.2	Is any data stored under an EU jurisdiction guarantee?	Yes. The three European regions store data under Cloudflare's EU jurisdiction, so it stays in the EU and Cloudflare chooses the datacenter.	/legal/data-act
3.3	Can we have a dedicated database?	On Scale, Enterprise and the isolation add-on, the workspace's own Amazon Aurora database on AWS in the AWS region the workspace chose. On Pro, Pro+ and Team, the workspace's own separate store on Cloudflare. Free and Starter use the region's shared Cloudflare D1 database.	/legal/data-act
3.4	Is a call ever answered from another region?	No. A regional service reads only its own region's database, and a call is never answered from another region.	/legal/data-processing-addendum
3.5	How much customer content do you store?	Tools that attest content store its hash, not the content. Relayed request and response bodies are not stored unless you turn on body retention. People in record chains are identified by a salted HMAC.	/legal/data-processing-addendum
3.6	How long is data kept?	Receipts follow the plan window: Free 7 days, Starter 30, Pro 90, Pro+ 180, Team 365, Scale 730; Enterprise by contract. Operational logs up to 30 days. The security audit log is retained through erasure.	/legal/data-processing-addendum
3.7	What happens to data when we leave?	You can export and delete at any time at no charge. After account deletion there is a 30-day grace period with nothing erased; then workspace data is erased, with listed exceptions such as receipts inside their window and records the law requires. Deletion is confirmed in writing on request.	/legal/data-processing-addendum
3.8	Can we export our data, and in which format?	Yes. The receipt export is a ZIP with the receipts, the key set, the verify.mjs script, a manifest and SHA256SUMS. The EU Data Act page lists each exportable data set and its format.	/legal/data-act
3.9	How do you handle government access requests?	Each request is checked for its legal basis, scope and conflict with EU law, and challenged where it is unlawful or too broad. Agined discloses the minimum required and tells you first unless the law forbids it.	/legal/data-act

Encryption

#	Question	Answer	Source
4.1	Is data encrypted in transit?	Yes. Traffic between you and the service uses TLS.	/legal/data-processing-addendum
4.2	Is data encrypted at rest?	Data at rest in Cloudflare D1 is encrypted by Cloudflare with AES-256, as Cloudflare documents.	/legal/data-processing-addendum
4.3	How are third-party credentials you hold for us protected?	Credentials and webhook secrets stored with a tool are sealed with AES-256-GCM, bound to your workspace and the endpoint, and are never returned or written to a receipt.	/legal/data-processing-addendum
4.4	Which algorithm signs your evidence, and who holds the keys?	Ed25519 over RFC 8785 canonical JSON. One key per data region, seven in all, held as encrypted Cloudflare Worker secrets and used only by the receipt service. No API route returns a private key.	/legal/key-management
4.5	How are signing keys rotated?	By a manual key ceremony run by Agined, with no schedule. No production signing key has been rotated so far. Owners and admins can record a rotation request.	/legal/key-management
4.6	What is your post-quantum position?	No receipt carries a post-quantum signature today. Receipts name their key inside the signed bytes so that a new algorithm can be added without breaking old receipts, and the path to ML-DSA is published without dates.	/legal/post-quantum

Logging and monitoring

#	Question	Answer	Source
5.1	Is every action call recorded?	Yes. Successful calls and refusals are appended to a per-workspace hash chain. If the audit write fails, the gateway answers 503 whatever the handler did. A call that reaches a tenant's host also leaves a fact on the tenant's chain, and the response carries a proof URL only when that fact was written.	/trust/security-pack/whitepaper#architecture
5.2	Can the logs be tampered with unnoticed?	Each audit entry hash covers the entry and the previous entry's hash, so a record cannot be removed from the middle of a chain unnoticed. Receipt tables reject updates and deletes by database trigger.	/trust/security-pack/whitepaper#evidence
5.3	Which security events are logged, and can we read them?	Sign-ins, key and role changes, denied access, receipt deletion and redaction and support sessions go to an append-only audit log with source IP address and user agent. Workspace admins read it in the dashboard.	/legal/data-processing-addendum
5.4	How long are logs retained?	Operational logs for up to 30 days. The security audit log is retained through erasure, with a person's identifier replaced where erasure is required.	/legal/data-processing-addendum
5.5	How do you monitor availability?	The status page checks each component every minute and keeps the history. The Enterprise SLA measures downtime from those checks.	/status
5.6	Do you detect abusive or anomalous agent behaviour?	Runtime detection on agent calls raises flags for review by a person, and a live breaker can raise an action to require human approval. A breaker can only tighten, never loosen.	/legal/data-processing-addendum

Incident response

#	Question	Answer	Source
6.1	When will you tell us about a personal data breach?	By email to the account owner without undue delay and within 72 hours of becoming aware, in phases if everything is not yet known.	/legal/data-processing-addendum
6.2	What will the breach notice contain?	The nature of the breach, categories and approximate numbers of data subjects and records, likely consequences, measures taken or proposed and a contact point, to the extent known.	/legal/data-processing-addendum
6.3	How are incidents communicated?	Incidents are published on the status page while they happen and kept in its history. Enterprise customers can subscribe to incident notices by email.	/legal/enterprise-sla
6.4	What is your plan if a signing key is compromised?	Handled as a security incident: stop signing with the key and move the region to a new key, publish a notice naming the key id, email the affected workspace owners, and decide whether the key stays published. There is no revocation list.	/legal/key-management
6.5	How fast does support respond for Enterprise?	Every report is acknowledged within 1 business hour (Monday to Friday, 9:00 to 17:00 US Eastern). These are acknowledgement targets, not resolution targets.	/legal/enterprise-sla

Vulnerability management

#	Question	Answer	Source
7.1	How do we report a vulnerability?	Through the report form, which accepts anonymous reports, or at security@agined.com.	/legal/responsible-disclosure
7.2	What response targets do you commit to?	Acknowledgement within 3 business days, initial assessment within 10 business days, updates at least every 14 days, and a fix or mitigation aimed at 30 days for critical and high severity and 90 days for lower. These are targets, not guarantees.	/legal/responsible-disclosure
7.3	Is there a safe harbor for researchers?	Yes, for good-faith research that follows the policy. It covers Agined's systems only. We ask for 90 days before public disclosure, by agreement.	/legal/responsible-disclosure
7.4	Do you run a bug bounty?	No. We do not pay monetary rewards; we credit reporters by name or handle if they wish.	/legal/responsible-disclosure
7.5	How do you protect against requests to internal addresses (SSRF)?	A filter refuses non-HTTP schemes, localhost, internal-looking names and private and reserved IP ranges, at submission and again when a scheduled check runs; relay tools never follow redirects, and capture tools check every hop. We do not describe the filter as a complete defence.	/legal/data-processing-addendum

Sub-processors

#	Question	Answer	Source
8.1	Do you publish your sub-processors?	Yes, with each provider's purpose, location, personal data involved and safeguards. It is Annex 3 of the DPA.	/legal/subprocessors
8.2	Who are the main ones?	Cloudflare (hosting, databases, storage, email delivery), Amazon Web Services (Amazon Aurora for Scale, Enterprise and the isolation add-on), Avonao Billing with Stripe (billing), Anthropic (assistants), Resend and Twilio, plus failover models and consent-gated analytics and fonts as listed.	/legal/subprocessors
8.3	How are we told about changes?	At least 30 days before a new sub-processor starts, owners of every workspace are emailed and the page is updated with the new date. An urgent replacement is notified as soon as possible with the same rights.	/legal/subprocessors
8.4	Can we object?	Yes, on reasonable data protection grounds within the notice period. If the objection cannot be met, you may terminate the affected service before the change and receive a refund of unused prepaid fees.	/legal/subprocessors
8.5	Is customer data used for advertising or resold?	No. We use no sub-processor for advertising or data resale, and our affiliates do not process the service's personal data.	/legal/subprocessors
8.6	How are international transfers covered?	By the Standard Contractual Clauses, the UK Addendum and the Swiss adaptations, which form part of the DPA and our agreements with sub-processors.	/legal/data-processing-addendum

Business continuity

#	Question	Answer	Source
9.1	Do you commit to an uptime level?	Enterprise plans with a signed order form: at least 99.9% monthly, with service credits of 10%, 25% or 50% of the monthly fee by shortfall. Self-serve plans carry no uptime commitment.	/legal/enterprise-sla
9.2	How are databases backed up and restored?	Cloudflare D1 Time Travel restores a database to any minute of the last 30 days. Agined keeps no other backup copy of those databases.	/legal/continuity
9.3	Can a bad deployment be reversed?	Yes. Deployments are versioned and can be rolled back without touching data.	/legal/data-processing-addendum
9.4	Does our evidence depend on your availability?	No. A receipt plus the public key it names verifies offline with standard cryptography, whether or not Agined is available or exists.	/legal/continuity
9.5	What happens if Agined stops operating?	At least 30 days' notice by email and on the status page, exports kept working for that period, the final key set published somewhere independent of Agined, and signing stopped before publishing stops. There is no third-party escrow of keys or source code today.	/legal/continuity

Privacy and legal

#	Question	Answer	Source
10.1	Is there a Data Processing Addendum, and do we need to sign it?	Yes. It is part of the Terms and applies on acceptance; no signature is needed.	/legal/data-processing-addendum
10.2	How do we exercise privacy rights?	Through the privacy request form, which covers GDPR and US state-law requests, or at privacy@agined.com.	/opt-out
10.3	Can we audit you?	First through documentation and written answers to a reasonable security questionnaire, answered within 30 days. If that is not enough, or after a breach or at a supervisory authority's request, you may audit once in 12 months on 30 days' notice, on the terms of DPA section 9.	/legal/data-processing-addendum
10.4	Do analytics and fonts load without consent?	No. Google Analytics loads only after you allow Statistics, and Adobe Fonts only after you allow Fonts in the EU, EEA, Switzerland and UK.	/legal/subprocessors
10.5	How does the EU AI Act apply?	The page says which part of the service is an AI system, how the assistant meets the transparency rules, and offers an Article 25(4) agreement for customers who build Agined into a high-risk AI system.	/legal/eu-ai-act
10.6	Where do I report illegal content or misuse?	Through the abuse report page, under the Digital Services Act notice process and the Acceptable Use Policy.	/abuse

Vendor security questionnaire

Organisation

Access control

Data protection and residency

Encryption

Logging and monitoring

Incident response

Vulnerability management

Sub-processors

Business continuity

Privacy and legal

Trademarks Notice

Choose your region

Choose your language

Vendor security questionnaire

Organisation

Access control

Data protection and residency

Encryption

Logging and monitoring

Incident response

Vulnerability management

Sub-processors

Business continuity

Privacy and legal

Trademarks Notice

Choose your region

Choose your language