Privacy Policy
Your data. Clearly explained.
What SwengleIO handles, why it’s needed and the choices you have.
Updated 6 November 2026
1. Who we are and what this covers
SwengleIO is operated by Swengle, Inc., a Delaware corporation (“Swengle”, “we”, “us”). This policy describes personal information handled through our website, console, APIs, customer relationships and operation of the Services.
We determine how account, website and business-contact information is used and act as its controller where that term applies. For personal information in Customer Content that customers submit, customers determine the purposes and we process it on their behalf. If your information belongs to an application built by a customer, contact that application’s operator first; their privacy notice describes their use of your information.
This policy does not cover independent third-party websites, cloud accounts or applications merely linked to or integrated with SwengleIO.
2. Information we handle
- Account and identity: email address, user identifier, verification status, profile name and picture (one you upload, or your sign-in provider’s) and information returned by a sign-in provider you choose. Firebase Authentication handles sign-in credentials and authentication records.
- Workspace and deployment information: resource names, cloud account identifiers, regions, configuration, permissions or role identifiers, deployment actions and their results. If you authorize cloud access, the associated authorization information is used to perform requested actions.
- Customer Content: messages and payloads, recipient or account identifiers, channel metadata and other information supplied through the Services. Its contents depend on the customer’s application.
- Technical and usage information: IP addresses, request and device/browser information, timestamps, errors, resource utilization, delivery and replay metadata, and service activity needed to operate, secure and measure the Services.
- Correspondence: information you include in support, sales, privacy or security requests, including chats with the Console’s assistant. Avoid including passwords, private keys or unnecessary sensitive information; the assistant removes SwengleIO secret keys and other recognizable credentials from a message before it is stored. With each reply we keep which account lookups it made (below), not what they returned.
- Commercial records: where you purchase Services, the order, business-contact, usage, invoice and payment-status information needed to administer it. Payment-provider involvement and any additional collection must be disclosed in the applicable purchase flow.
Information comes from you and your authorized users, your application’s traffic, the operation of our systems, and the authentication or cloud providers you connect. Account and authorization information is necessary for authenticated service access; without it, we cannot provide that access. You choose what other content to submit.
3. Google user data
This section explains how SwengleIO accesses, uses, stores, shares and deletes Google user data when you choose Sign in with Google. It applies to the SwengleIO Console at console.swengle.io.
Data we access
SwengleIO requests only the standard sign-in scopes openid, email and profile. Through them Google gives us your Google account identifier, your email address and whether Google has verified it, your name and your profile picture. SwengleIO does not request or access Gmail, Google Drive, Calendar, Contacts or any other Google data.
How we use it
We use this data only to create your SwengleIO account and sign you in, to show your name and picture in the Console, to identify you to other members of the organizations you belong to, and to send you account, security and billing email. We do not use it for advertising, we do not sell it, and we do not use it to develop, improve or train machine learning or AI models, or send it to any AI model provider for that purpose.
How we store and protect it
Google user data is held by Firebase Authentication on our behalf and in our account database on Google Cloud in the United States. It is encrypted in transit and at rest, and only the staff who operate the Services can access it.
How we share it
We do not transfer Google user data to anyone except: the service providers in section 6 that host and operate SwengleIO for us; members of organizations you belong to, who see your name, email and picture; and authorities where the law requires it. We never sell it or share it for advertising.
Retention and deletion
We keep this data while your account is active. To delete it, email privacy@swengle.com from the account's address; we then delete your account and its Google user data, apart from records the law requires us to keep (section 7). You can also remove SwengleIO’s access at any time in your Google Account.
Limited Use
SwengleIO’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. Why we use it
We use information to authenticate users; create and manage workspaces; provision requested resources; process and deliver Customer Content; support reconnection and replay where configured; measure service usage; diagnose faults; protect accounts and systems; answer requests; administer orders; and comply with legal obligations.
Where a legal basis is required, account and service administration is based on performing our contract with you, or our legitimate interest in serving an organization you represent. Security, troubleshooting and business communications are based on our legitimate interests in operating and protecting the Services, balanced against individual rights. Legally required records and disclosures are based on legal obligations. Optional activities that require consent rely on that consent, which you may withdraw.
For Customer Content processed on behalf of a customer, that customer establishes the applicable lawful basis. We do not use Customer Content for advertising. Our current website and console do not include advertising trackers or an advertising-profiling system. Ordinary automated authentication, routing and security checks support service operation; we do not use them to make decisions about credit, employment or similarly significant personal matters.
5. Cookies, browser storage and fonts
The public website does not set application cookies or include an analytics SDK. It loads Google Fonts, which causes your browser to contact Google and send technical request information, including your IP address. Your browser or hosting provider may also cache resources and record requests.
The Console uses the swengle_session cookie to keep you signed in for up to 30 days, unless you sign out or the session is invalidated earlier. It is HttpOnly and SameSite=Lax; the hosted HTTPS configuration also uses the Secure flag. Firebase Authentication can use its own browser storage to support sign-in.
Local browser storage remembers Console preferences, such as the sidebar’s width, whether it is collapsed, your theme, the org you last worked in and the assistant panel’s width, whether it is open and the chat you last had open; session storage briefly remembers where a sign-up from the website should land. It remains until cleared or replaced by the application or your browser. You can clear cookies and site storage in your browser settings; doing so can sign you out and reset preferences. Blocking authentication storage can prevent console access.
6. Providers and other disclosures
Information is disclosed only as needed for service operation, your instructions, legitimate business administration or legal requirements. Recipients include:
- Google Cloud and Amazon Web Services: hosting and cloud infrastructure for the Services in the regions you choose, including Firebase Hosting for this website.
- Oracle (Oracle Cloud Infrastructure): hosting and cloud infrastructure for the Services in its regions you choose.
- Microsoft (Azure): hosting and cloud infrastructure for the Services in its regions you choose.
- Stripe: payment methods, invoices and payments. Card details go to Stripe on its own pages and never reach us; see Stripe’s Privacy Policy.
- Cloudflare: DNS for our domains; and, as a sub-processor of Customer Content, storage (Cloudflare R2) of encrypted copies of the backups of every region we offer, so that they survive the loss of a region or of a cloud provider. The copies are encrypted before they leave our cloud, and Cloudflare does not hold the keys. Where the copies are stored is in section 8.
- Resend: email we send, such as invitations to an organization and operational alerts.
- Anthropic: writes the Console assistant’s replies with its Claude models, through its API. It receives the messages of the chat being answered and what the assistant looks up in that chat’s organization to answer, only as far as your own permissions there allow: the organization’s name, its endpoints and their settings, usage and measured latency, regions, key IDs (never secret keys), other members’ display names and permissions (never their email addresses) and, if you have the billing permission, prices, charges, invoices and your payment method’s brand, last four digits and expiry. It does not receive your name, email address or picture. Under Anthropic’s commercial terms it does not use them to train its models by default; see Anthropic’s Privacy Policy.
- PagerDuty: pages our on-call staff for the most serious alerts about our systems. Alerts can name resources such as a cluster’s identifier and region; they contain no Customer Content or personal information.
- Google / Firebase: console authentication and related identity and technical information. Google also receives requests for the website’s fonts. See Firebase’s privacy information and Google’s Privacy Policy.
- Sign-in providers you choose: Google processes your authentication interaction under its own terms and privacy policy. We receive the identity information needed for your account.
- Authorized recipients: your workspace users, application recipients and integrations, as directed by your configuration.
- Professional advisers and authorities: where necessary for advice, legal compliance, enforcing agreements or protecting rights and safety.
- A business successor: in a merger, acquisition or asset transfer, subject to applicable protections and notice requirements.
The providers above that process Customer Content or account information for us are listed, with what each receives, on our sub-processor list.
We do not sell personal information or share it for cross-context behavioral advertising. Operational disclosure to service providers is distinct from those activities. Access within Swengle is limited to people who need information for their work.
Chats with the Console’s assistant are private to you within each organization: other members, its administrators included, cannot see them. Swengle staff may read them, with which lookups each reply made, to follow up on a support request and to investigate abuse. The assistant is an AI, and its replies are written by Anthropic (above) from the chat and its lookups. We never use assistant chats to train or improve AI models.
7. Retention and deletion
Retention depends on the type of information, service configuration, your instructions and applicable legal requirements:
- Account and workspace records: kept as needed to provide an active account and resolve closure, support, security or legal matters.
- Customer Content: governed by the applicable service configuration and order, including message-history and replay settings. Deleting an account does not itself prove that every resource in a customer-controlled cloud account has been removed.
- Assistant chats: kept until you delete them, each reply with the list of lookups it made. A deleted chat is hidden at once and permanently deleted, with its messages, 7 days later; backup copies follow their rotation (below). Leaving an organization hides your chats there until you rejoin it; deleting your account deletes them.
- Operational and security records: retained as needed for troubleshooting, investigating incidents, detecting abuse and establishing what actions occurred.
- Commercial and legal records: retained for applicable tax, accounting, claims and legal-preservation requirements.
- Browser storage: the session duration and preference-storage behavior are described above.
When information is no longer needed for these purposes, it is deleted or de-identified. Where backup copies exist, deletion follows their applicable rotation process; restricted copies may remain for legal preservation. A single fixed deletion deadline does not apply to every data category. Service-specific retention and export arrangements must be confirmed in the applicable order or data-processing agreement.
8. Security and international processing
Authentication, session validation and access controls help protect account access. Security also depends on customer configuration, credential handling and the providers involved. No transmission or storage method is completely secure; this policy does not promise end-to-end encryption, a particular certification or immunity from incidents.
Our account and console infrastructure is in Google Cloud’s us-east1 (South Carolina) region, reached through Google’s global load balancer, and its backups are kept in Google Cloud’s nam4 dual region (us-central1, Iowa, and us-east1, South Carolina); this website is served by Firebase Hosting. The regions you can choose for your endpoints are Google Cloud’s us-east1 (South Carolina), europe-west2 (London), europe-west3 (Frankfurt) and asia-northeast1 (Tokyo), Amazon Web Services’ us-east-2 (Ohio), eu-west-2 (London), eu-central-1 (Frankfurt) and sa-east-1 (São Paulo), Oracle Cloud Infrastructure’s us-ashburn-1 (Virginia), uk-london-1 (London) and eu-frankfurt-1 (Frankfurt), and Microsoft Azure’s centralus (Iowa). Encrypted copies of the backups of every region we offer are also kept in Cloudflare R2. For the regions in the United Kingdom and the European Union (Google Cloud’s europe-west2 and europe-west3, Amazon Web Services’ eu-west-2 and eu-central-1, and Oracle Cloud Infrastructure’s uk-london-1 and eu-frankfurt-1), they are kept in Cloudflare’s EU jurisdiction, which keeps them within the European Union; for the London regions, that means in the European Union, not in the United Kingdom. For every other region, Cloudflare is given only a location hint, which it treats as a preference and does not guarantee: eastern North America for us-east1, us-east-2, sa-east-1, us-ashburn-1 and centralus, and Asia-Pacific for asia-northeast1. So these copies can be stored outside the region’s country. Provider services and any customer-selected deployment region can involve additional locations. Accessing the Services can therefore involve processing in the United States and other countries with different privacy laws. A selected workload region does not by itself guarantee that all account, support or operational information remains there.
Where law requires a transfer safeguard, the applicable arrangement must be established before the affected processing. This policy does not itself create standard contractual clauses, an adequacy certification or a residency guarantee. Contact us for the arrangement relevant to your account.
9. Your choices and privacy rights
Depending on where you live and applicable law, you may have rights to access and receive a copy of personal information, correct it, request deletion, obtain portability, restrict processing, withdraw consent and appeal a refusal. You may also object to processing based on legitimate interests, including any direct marketing. Withdrawing consent does not affect earlier lawful processing.
Send requests through our privacy contact, identifying your account and the request without sending a password or unnecessary identity documents. We verify identity and authority proportionately, respond within applicable legal deadlines and explain any lawful exceptions. An authorized agent may act for you where law permits, subject to verification. We do not discriminate against you for exercising applicable privacy rights.
For Customer Content, contact the application operator or organization that controls it. We assist the relevant customer with requests as required by law and the applicable agreement. If you are dissatisfied, you may complain to your local privacy regulator; UK residents can contact the Information Commissioner’s Office, and EEA residents their national supervisory authority.
The current website does not conduct the sale, advertising sharing or targeted advertising that sale/sharing opt-out signals address. We do not treat browser “Do Not Track” signals as a separate preference setting; applicable legally required opt-out signals must be honored if covered processing is introduced.
10. Children and sensitive information
The SwengleIO website and console are intended for adult business and developer users, not children under 13. Do not create an account if you are under 18. If you believe a child has provided account information, contact us so we can investigate and take appropriate action.
Customers are responsible for their own applications’ age requirements, notices and permissions. Do not send specially regulated or highly sensitive information through the Services without an appropriate written agreement and safeguards.
11. Updates and contact
We show the revision date above and provide notice of material changes through the website, console or account email as appropriate. A new use that requires consent is subject to that consent; updating this policy alone does not supply it.
The responsible company is Swengle, Inc., a Delaware corporation. Write to privacy@swengle.com about your information; other contacts are on the Contact page.