privacy policy
Privacy Policy
Last updated 19 November 2026
01
Introduction
Adroyt ("we," "our," or "us") is committed to protecting your personal information and your right to privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our AI-powered project management platform.
اقرأ سياسة الخصوصية باللغة العربية
02
Data We Collect
Account & Profile
When you register, we collect your name, email address, organization name, role, language and timezone preferences, and (optionally) a profile photo. If you sign in through a single sign-on provider, we receive your name, email, and a stable identifier from that provider.
Billing
For paid subscriptions, our payment processor collects and stores your card or bank details directly. We never see or store full payment-card numbers; we receive only a tokenized reference, the billing email, the last four digits, the country, and invoice metadata.
Project Content
Data you and your team input into the platform — projects, tasks, milestones, resources, files, comments, custom fields, time entries, and reports — together with anything you upload (documents, images, schedule imports). You retain ownership of this content; we process it only to provide the service.
AI Conversations
The prompts you send to the in-app AI assistant, the project context attached to those prompts, and the assistant's responses. These are stored against your account so chat history persists across sessions.
Telemetry & Diagnostics
Pages visited, features used, performance metrics, error reports, and coarse device information (browser, operating system, approximate location derived from IP). We use this to operate and improve the platform.
Identity & Security Tokens
When you connect a third-party account (single sign-on, calendar, storage, integrations), we store the access tokens needed to maintain that connection, encrypted at rest. We never store the password to your third-party account.
Support & Communications
The content of support tickets, in-app feedback, and email correspondence with our team.
03
How We Use Your Data
We use the information we collect to:
- Provide, operate, and maintain the platform
- Generate AI-driven insights, summaries, and recommendations on your project content
- Send transactional communications, security alerts, and service updates
- Improve and personalise your experience
- Detect, prevent, and respond to fraud, abuse, and security incidents
- Bill you accurately and resolve billing disputes
- Comply with legal obligations and enforce our Terms of Service
We do not use your project content, AI conversations, or uploaded documents to train any machine-learning models — neither our own nor any third party's.
04
AI Processing
Our AI features are powered by third-party large language model providers operating under enterprise agreements. When you use an AI feature:
- Your prompt and the project context required to answer it are sent to the provider over an encrypted connection.
- The provider processes the request and returns a response. Under our enterprise terms, the provider does not retain your prompts or responses beyond the time needed to serve the request, and does not use your data to train its models.
- We log the request, the response, and metadata (timestamps, duration, token counts, cost) for billing, abuse prevention, and quality monitoring. These logs are scoped to your tenant and accessible to your tenant administrators.
- AI-generated content can contain errors. You are responsible for reviewing AI output before relying on it for decisions, and for ensuring the prompts you submit do not violate the rights of others.
You can disable AI features for your tenant from your workspace settings. A workspace administrator makes this choice. When it is off, the assistant, AI agents, AI-generated documents, document indexing and meeting transcription do not run, and nothing from your workspace is sent to our AI provider. The change takes effect within seconds. Content already processed before you turned it off is not recalled. You can also turn off individual AI agents without turning off everything. If you need AI processing restricted in another way, contact [email protected].
05
Subprocessors and Data Sharing
We do not sell your personal information. We share limited data with thirteen carefully vetted subprocessors who help us deliver the service, each bound by a written data processing agreement and confidentiality obligations. The named list below mirrors our internal vendor management policy and is updated whenever a subprocessor is added, removed, or replaced.
| Subprocessor | Service | Data shared | Region |
|---|---|---|---|
| Supabase | Database, authentication, object storage, realtime | Account, project, and session data; uploaded documents and images; authentication identifiers | European Union (Frankfurt) |
| DigitalOcean | Application hosting and managed cache | Application logs, build artifacts, ephemeral cache and background-job state, session refresh tokens | European Union (Frankfurt) |
| Cloudflare | CDN, DNS, and edge reverse proxy (TLS termination, DDoS protection) | IP address and request metadata (URL, headers, user agent) plus TLS/connection logs for traffic proxied to adroyt.io | United States / global edge network |
| Resend | Transactional email delivery | Recipient email, subject, rendered message body, delivery status | United States (with EU delivery option) |
| Anthropic | Primary AI inference provider | AI prompts and the project context attached to them | United States |
| OpenAI | AI inference fallback (only when primary provider is unavailable) | AI prompts and the project context attached to them | United States |
| Stripe | Payments and subscription billing | Billing email, tokenized payment method, subscription state, invoice metadata (no raw card data) | United States / European Union |
| Sentry | Error tracking | Error stack traces, request metadata, tenant and user identifiers | European Union (Frankfurt) |
| PostHog | Product analytics and feature flags | Pseudonymised usage events (only with consent), coarse geolocation | European Union |
| Google Analytics (GA4) | Website analytics — the GA4 script loads with analytics storage denied; nothing is stored or measured until you accept analytics cookies | Pseudonymised page-view and event data, device and browser metadata, coarse geolocation (only with consent) | United States (Google LLC) |
| GitHub | Source control and continuous integration | Source code, CI logs, encrypted build secrets | United States (with global edge) |
| Fly.io | Antivirus scanning host (uploaded files) | File bytes streamed through the scanner (not retained); scan logs containing filename, tenant identifier, and any virus signature detected | European Union (Frankfurt) |
| Dmarcian-EU | DMARC aggregate-report processing | DMARC aggregate reports (sender IPs, message counts, alignment status); no message bodies | European Union |
We may also disclose data when required by valid legal process, to enforce our Terms, to protect the safety of users or the public, or in connection with a merger, acquisition, or sale of assets (with notice to you).
06
Your Privacy Rights
Depending on your jurisdiction, you may have the right to:
- Access and export your personal data
- Correct inaccurate information
- Request deletion of your data
- Restrict or object to certain processing
- Data portability
- Withdraw consent at any time
Signed-in users can export their data and submit access, correction, and deletion requests directly from Settings → Profile → Data rights. You can also contact us at [email protected]. We respond within 30 days.
07
UAE and Saudi Arabia (PDPL)
If you are in the United Arab Emirates or the Kingdom of Saudi Arabia, we process your personal data in line with the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) and the Saudi Personal Data Protection Law (Royal Decree M/19 of 2021, as amended) and their implementing regulations.
- Roles. For project content your organisation puts into Adroyt, your organisation is the controller and Adroyt is its processor, acting under our Data Processing Agreement. For account, billing, and website data, Adroyt is the controller.
- Legal bases. We process data to perform our contract with you, to meet legal obligations, for our legitimate interests in securing and improving the service, and — for analytics cookies — on the basis of your consent, which you can withdraw at any time.
- Your rights. You may request information about and access to your data, correction, deletion, restriction, a copy in a structured format, and withdrawal of consent, as described in Your Privacy Rights. We respond within 30 days.
- Cross-border transfers. Your data is stored in the European Union, and AI requests are processed in the United States (see Data Residency). We transfer personal data outside the UAE or Saudi Arabia only where the law permits it, relying on contractual safeguards with each subprocessor, encryption, and access controls.
- Breach notification. If a personal data breach is likely to affect you, we notify the competent authority (the UAE Data Office or the Saudi Data & AI Authority, SDAIA) and, where required, affected individuals within the timelines the law requires — for SDAIA, within 72 hours of becoming aware of it.
- Complaints. You can contact our Data Protection Officer at [email protected], and you may also lodge a complaint with the competent authority.
08
Data Security
We implement industry-standard security measures including AES-256 encryption at rest and TLS 1.2 or higher in transit, role-based access controls, regular security reviews, hash-chained audit logs, and multi-tenant data isolation. Our security program is built around the SOC 2 Trust Services Criteria; formal third-party certification is on our roadmap.
09
Data Residency
Your account, project content, files, and operational data are stored in our primary region in the European Union (Frankfurt, Germany). Backups are stored in the same region.
The exception is AI inference: when you use an AI feature, the prompt and the project context required to answer it are routed to our AI provider, which processes the request on infrastructure in the United States, then returns the response. The provider does not retain or train on your data. If you do not want AI inference data to leave the EU, disable AI features in your workspace settings (see AI Processing above); this does not affect the other processing listed below.
Other processing also takes place outside the EU, and no AI control affects it: Cloudflare terminates TLS and proxies traffic to adroyt.io across its global edge network; Resend sends transactional email from the United States; Stripe processes payments in the United States and the European Union; GitHub hosts our source control and CI in the United States; and Google Analytics, whose script loads with analytics storage denied and which measures nothing until you accept analytics cookies, then processes pseudonymised website usage data in the United States. No workspace setting turns these off; analytics is the only one you can decline, through the cookie banner. See the Subprocessors table above for the data categories involved.
For international transfers, we rely on the Standard Contractual Clauses adopted by the European Commission, supplemented by technical and organisational measures (encryption in transit and at rest, access controls, audit logging).
11
Data Retention
We keep different categories of data for different periods, balancing your right to have data deleted with our legal, security, and operational obligations. Where a row says a rule is not in place yet, it is a rule we have decided and are building; the row says what happens until then.
| Data category | Retention period |
|---|---|
| Account profile | For the life of the account; deleted within 30 days of account closure |
| Project content (projects, tasks, files, comments) | For the life of the workspace; deleted from live systems 30 days after a workspace deletion request, and backup copies are overwritten within a further 35 days. Some records are not removed by the deletion yet. These include files the workspace generated (workspace exports, timesheet exports, generated reports, stored meeting minutes and uploaded meeting recordings), search summaries of project items, agent check results, single sign-on logs, meeting and decision records, and document version history. We are fixing this |
| AI conversation history | Until you or your tenant administrator deletes the conversation; in any case removed within 30 days of account closure |
| Text of AI agent runs (the question, the answer and any error) | We are putting in place a 12-month limit, after which the text is blanked and only the record of the run stays. Until then the text is kept until the workspace is deleted |
| Audit logs (security & compliance) | For the life of the workspace; never archived. After a workspace is deleted, we will keep them for 365 days and then delete them, except entries that explain billing records we still keep. This after-deletion rule is not in place yet: today some audit records are deleted with the workspace and others are kept with no end date |
| AI security log (checks run on AI requests) | We are putting in place a 180-day limit. Until then it is kept until the workspace is deleted |
| Notifications | 90 days after sending; approval requests nobody has acted on, and system alerts, up to 12 months. These limits are not in place yet; until then notifications are kept until the workspace is deleted |
| Usage records (metering of billable use) | Deleted 90 days after they are reported to our payment processor. We are putting in place a 13-month upper limit; until then, records not yet reported are kept until the workspace is deleted |
| AI usage lines (tokens and cost per request) | 90 days, then kept only as monthly totals |
| Project health scores, earned-value points and schedule change history | For the life of the project. Today schedule change history is deleted after 90 days; keeping it for the life of the project is not in place yet |
| Adroyt's billing records and invoices, and the AI credit ledger | We will keep them for 10 years from the end of the financial year, also after a workspace is deleted, to meet tax and accounting law. This period may change once the tax rules that apply to us are confirmed. It is not in place yet: today these records are deleted with the workspace |
| Error reports and error logs | Up to 90 days |
| Backups | Up to 35 days on a rolling basis, then overwritten |
| Marketing email subscription preferences | Until you unsubscribe; suppression list kept indefinitely so we do not contact you again |
You can request earlier deletion at any time. We may retain the minimum data required to comply with a legal obligation, defend a legal claim, or prevent abuse — these residual records are isolated and not used for any other purpose.
When you ask us to erase your personal data, we anonymize your account and remove your sessions, your notifications, the text of the questions you asked agents, and your user id on the AI security log. Some data is kept. The text of questions asked before 16 November 2026 can remain in agent run and usage records until the workspace is deleted. Billing and audit records are kept as the table above says. Copies of erased data in backups are overwritten within 35 days, and copies in error logs within 90 days. We only use backups for disaster recovery, and we re-apply erasures after any restore.
12
Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email or through a notice on the platform. Continued use after changes constitutes acceptance.
13
Contact Us
If you have questions about this Privacy Policy, contact our Data Protection Officer at [email protected].