1. Information we handle
- Contact details and company information submitted in a pilot request.
- The role, desired outcome, systems and approval boundaries you describe.
- Technical security information such as timestamps, request identifiers, basic logs and errors.
- Approved pilot inputs, outputs, usage metadata and provenance required to review a supervised test.
2. Why we use it
We use information to review and answer requests, scope a safe pilot, operate approved features, enforce permissions, investigate abuse, improve reliability and meet legal obligations. We do not sell pilot content or use it for advertising.
3. Service providers and transfers
The public website and API currently rely on hosting and infrastructure providers. A model provider is contacted only when an approved pilot feature requires it. Before production use, ATACSYS will document the selected provider, region, retention setting, transfer basis and subprocessors in the applicable order form or DPA.
Website hosting currently uses Vercel. The application API currently uses Railway. These providers may process technical request data needed to deliver and secure the service.
4. Retention and isolation
We keep request, session and security information only as long as reasonably needed for the pilot, support, safety and legal obligations. Company Memory is designed to remain separated by customer and from an agent creator. Final production retention and deletion schedules require contractual approval.
6. Access, correction and deletion
You may ask what information we hold about your request, correct it or request deletion, subject to security and legal retention duties. Email hello@atacsys.com from the address used in your request. We may ask for reasonable verification before acting.
This pilot notice will be updated with the final legal entity, controller address, formal rights procedure and international transfer details before paid production launch.