ARGV / LEGAL
Privacy Policy
Effective:
How ARGV handles account information, persistent project intelligence, and the services involved in your work.
1. Information you provide
This Policy describes information handled by ARGV at argv.app and its associated service. You may provide account details, project material, task instructions, AI-provider configuration, and information in communications with us. Submit only information you are authorized to share and avoid unnecessary personal information, secrets, or credentials in project content.
2. Account and authentication information
Microsoft is currently our identity provider. When you sign in, ARGV receives identity information such as a provider identifier, display name, and email when available. ARGV stores an account and its link to that external identity. Microsoft handles your Microsoft sign-in credentials under its own privacy policy.
Authentication is managed by ARGV’s backend service, argv-api. The website forwards the opaque ARGV session cookie to that service; argv-api determines the current user. The website does not decrypt the cookie or use Microsoft profile information as the authority for project access.
3. Project and context data
ARGV stores project and context data in its backend database. This can include descriptions, architecture and engineering rules, memory and revisions, context snapshots, task instructions, prompts, Task Packs, generation and refinement history, and validation or execution-related records captured by the service. This is persistent project intelligence, not a local-only store. Sharing a project gives authorized members access according to their roles.
4. Usage and telemetry
The service records usage and operational information, such as generation activity, provider and model identifiers, token counts, estimated costs, timestamps, errors, and request or performance diagnostics. Technical information handled by hosting or logging systems may include network addresses and browser or request details. Operational diagnostics vary with deployment configuration.
5. AI-provider and tool processing
When configured generation uses an external AI provider, including OpenAI, relevant task instructions and selected project context are sent by ARGV’s backend to that provider to produce a response. A mock generation mode does not require an external AI request. Provider credentials you configure are handled by the backend and stored in protected form.
If you copy, export, or hand off a Task Pack to an external coding tool, that tool may process its contents under its own policies. Provider retention, training practices, and processing locations depend on the provider and your account configuration. Review those policies before sending material; processing is not necessarily limited to your device.
7. How information is used
We use information to:
- Authenticate users and enforce account and project permissions.
- Store project intelligence and prepare contextual engineering work.
- Provide generation, history, sharing, and usage visibility.
- Operate, troubleshoot, and protect the service.
- Respond to requests and meet applicable legal obligations.
Where data protection law requires a lawful basis, processing must be supported by an applicable basis, such as providing the requested service, legitimate interests in operating and securing it, or a legal obligation. Where consent is required for a particular use, it must be obtained for that use.
9. Data retention
Project content and its history are persisted so they remain useful across engineering sessions. Retention depends on the type of record, continued use, deletion actions, operational needs, and applicable legal obligations. Session records have expiry and revocation information. ARGV does not promise zero retention or a fixed deletion period under this Policy.
Deleting a project removes its project-owned data from the active product database. Separate account or operational records and any backup copies may have different lifecycles. Deleting information in ARGV does not delete copies you or others have sent to external tools or providers. Contact us about retention or deletion requests.
10. Security
ARGV uses measures including protected session handling, backend authorization, project access controls, and protection of stored provider credentials. No system or transmission method is completely secure. Protect your account, limit project sharing, and avoid placing secrets in task or context material.
11. Your choices and rights
You can edit project content, manage sharing where your role permits, delete projects you own, and choose what material to send to external tools. Availability of generation settings depends on your account’s access. Use browser controls to manage cookies and sign out when you no longer need a session.
Depending on applicable law, you may have rights to access, correct, delete, or receive a copy of personal information, restrict or object to processing, withdraw consent where processing relies on it, or complain to a data protection authority. Requests may require identity verification and may be subject to lawful exceptions. Contact ARGV to make a request; we do not imply that every right has a self-service control in the current product.
12. Business and customer data
If you use ARGV for an organization, follow its policies and ensure you have authority to submit and share its material. Project owners control current sharing permissions. Expanded organizational administration and governance are planned. A separate written customer or data-processing agreement, if signed, may define additional responsibilities for customer data; this Policy does not claim that such an agreement is already in place.
13. International processing
Processing locations depend on ARGV’s deployment and the identity, hosting, or AI providers involved in your use. Those providers may process information in countries other than yours. ARGV does not promise storage in a particular country or region. Providers’ privacy notices describe their processing arrangements. Applicable legal requirements for international transfers remain relevant to that processing.
14. Policy changes
We may update this Policy as the service and its data handling evolve. The revised Policy will show its effective date. Material changes will be communicated through the service or an available account contact where appropriate. We will obtain consent for a change where applicable law requires it.
15. Contact
Operator and privacy contact details will be published here before commercial launch. When contacting ARGV about a request, describe the information or account involved without including passwords or API keys.
16. Effective date
This Privacy Policy takes effect on 13 September 2026. See also our Terms & Conditions.