DevSwat

GDPR overview

The only GDPR reference found in first-party sources is a single feature line on the pricing page archived on 16 February 2026, listing SOC2, HIPAA, GDPR compliance among Enterprise tier features. That line was published under the earlier ResonantGenesis brand and describes one commercial tier; it is not a general statement of compliance, and no certification or audit report supports it. No privacy policy is consultable, so legal basis, data subject rights, transfer mechanisms and retention periods cannot be checked. No Article 27 representative, no data protection officer and no GDPR contact address were ever published. The publisher appears to operate outside the European Union. Since the service went offline, none of this can be clarified with the vendor.

Who owns the data?

No ownership clause can be read. The /privacy and /terms routes existed inside the archived application, but their content was never captured and the site no longer serves them, so the contractual position on data ownership is unverifiable. The only first-party signals are promotional: the August 2026 home page stated Your agents, your data, your infrastructure, and the meta description described the platform as fully self-hosted. Semantic memory was presented as per-user AES-encrypted, and the archived Enterprise tier advertised on-premise or hybrid deployment with data locality control. Together these suggest that customers were meant to keep their data, but nothing binding is available to confirm it.

Reuse rights

No data-use policy can be consulted: the legal pages were never archived and the site no longer serves them, so nothing states whether an end user could reuse outputs freely, or under which conditions. What the archived material describes is technical rather than contractual: immutable, tamper-proof audit logs covering every action, plus compliance profiles and capability decay inside the RARA governance layer. On the billing side, credits covered AI model calls, compute time, storage and agent execution. Model access ran on customer-supplied keys (GitHub PAT, OpenAI, Anthropic, Google, Mistral, Groq, Cohere, Together AI, DeepSeek, TokenRouter), which means each provider's own terms governed the traffic sent to it. The primary source that would settle the question is missing.

Data retention & training

Hosting summary

No hosting country or region is declared. The pages that would state a jurisdiction, namely the privacy policy and the security page, were never archived and are no longer served, so the location of customer data is undocumented. The publisher's own positioning pointed away from vendor hosting: the meta description described the platform as fully self-hosted, and the archived Enterprise tier advertised on-premise or hybrid deployment with data locality control, which would place hosting under the customer's control. The Hash Sphere memory layer was described as AES-256-GCM encrypted per user, but encryption says nothing about jurisdiction. One measurable fact remains: on 5 September 2026 dev-swat.com resolves to 68.168.213.164, an Interserver address in New York City, United States. That is the hosting of the domain itself, and since the host now serves only a default directory index, it says nothing about where customer data ever lived. Anyone needing a jurisdiction answer should treat it as unknown.