1. Our approach
Atbit World LLC uses the providers below to operate Densnap. We select providers for a defined purpose, limit the information they receive to what is reasonably needed, and configure their services to support Densnap’s privacy and security commitments.
“Subprocessor” on this page means a service provider that processes information to help Densnap deliver the service. Some platform, payment, identity, registrar, or registry participants may also act under their own legal or contractual obligations rather than solely on Densnap’s instructions. We identify those roles instead of inaccurately labeling every recipient the same way.
For a complete explanation of the information Densnap handles and why, read the Privacy Policy. This list does not mean every provider receives every customer’s information. Conditional services, such as Google Sign-In, receive information only when the customer uses that feature.
2. Service providers
| Provider | Purpose | Information involved |
|---|---|---|
| OpenAI | AI website generation and conversational editing through the OpenAI API. | Necessary business information, relevant customer uploads or extracted text, editing instructions, bounded website context, and generated output. |
| Cloudflare | Public API and edge delivery, application database, artifact storage, realtime coordination, durable operations, customer website and form hosting, DNS, HTTPS, network security, and domain registration services. | Account and project records, website source and builds, public website content, visitor inquiries, operational and security information, and domain contact information when registration is requested. |
| Cloudflare Turnstile | Protect Densnap-managed inquiry forms against bots, spam, and abuse. | Request, browser, challenge, and anti-abuse signals needed to assess whether a form submission is legitimate. |
| Supabase | Account authentication, email/password identity, sessions, confirmation, password reset, and optional social sign-in brokering. | Email address, provider identity, password hash, session, and authentication metadata. Densnap does not receive plaintext passwords. |
| Google Cloud Platform | Private AI runner compute, isolated website builds, service logging, and metrics. | Authorized job inputs, a project workspace during execution, generated source and build material, and operational logs. |
| RevenueCat | App Store subscription normalization, entitlement status, purchase reconciliation, and webhooks. | Densnap account identifier, product, store, transaction or event identifiers, renewal status, expiration, and entitlement metadata. Densnap uses its account identifier rather than email as the primary RevenueCat customer identifier. |
| Resend | Delivery of authentication and transactional service email where configured through Supabase or Densnap. | Recipient email address, delivery metadata, and the content of the service message. |
| Optional Google Sign-In and hosting or routing of Densnap’s public support, privacy, legal, and abuse mailboxes through Google Workspace. | Identity data only when Google Sign-In is chosen; correspondence sent to a Densnap public mailbox when Workspace handles that message. | |
| Expo / 650 Industries | Application build and signed update delivery where enabled for the production release. | Build artifacts and technical application or update-delivery metadata. |
3. Other necessary recipients
Apple
Apple distributes the Densnap iOS application, processes App Store subscriptions and payment credentials, manages subscription status, and acts as an identity provider when a customer chooses Sign in with Apple. Apple receives store and transaction information and, conditionally, the identity information needed for Apple sign-in. Apple’s processing is also governed by its own terms and privacy practices.
Cloudflare Registrar, domain registries, and ICANN-required participants
When a customer asks Densnap to register or manage a domain, the domain name and required legal contact information are disclosed to Cloudflare Registrar, the applicable registry, and ICANN-related participants as needed for registration, verification, DNS, renewal, correction, transfer, disputes, and other domain-governance obligations. These recipients may have independent legal or contractual duties.
The customer business receiving an inquiry
A visitor’s name, contact information, and message are delivered to the business named on the inquiry form so it can respond. That business is the intended recipient, not a subprocessor working for Densnap. The business is responsible for its later use of the inquiry.
Authorities and rights holders
Densnap may disclose narrowly scoped information when reasonably necessary to comply with law or valid legal process, address fraud or security threats, protect people or the service, resolve domain obligations, or establish, exercise, or defend legal claims.
4. Changes to this list
We update this page when a provider is added, removed, or materially changes its role. A new provider that receives personal information must pass a privacy and security review. If a change materially alters how previously collected information is used, Densnap will also update the Privacy Policy and provide notice or request new permission when required.
The date at the top of this page identifies the current version. Customers may contact us to ask about a provider or the information involved.
5. Questions
For privacy questions about a provider, email [email protected]. For operational help, email [email protected]. Legal notices may be sent to [email protected].