Swanatronics is built around local-first tools and practical control. This page explains what information may be handled by the website, Swanatronics products, and Swanatronics Desk.
Website
The website may be served by normal web hosting and server infrastructure. Basic server logs may exist for security, diagnostics, and reliability.
Swanatronics does not use ad tracking, advertising profiles, or social media tracking pixels on the website.
The practical aim is simple: no cloud data harvesting, no ads, and no tracking profiles.
Accounts
Nest Remote does not require a Swanatronics account. The current public website does not provide user accounts.
Future products may have different account requirements. If that happens, the relevant terms and privacy wording will be updated when needed.
Discord applications and bots
Swanatronics may operate Discord applications and bots, including Sentinel, Cygnature, Swanatronics bot concepts, experimental bots, private testing bots, and retired bots where they remain installed, listed, or connected to a Discord application.
Depending on the bot and enabled features, a Discord application may handle Discord-provided identifiers and configuration data such as server IDs, channel IDs, role IDs, user IDs, command names, command options, permission settings, moderation settings, protection settings, audit-style action records, and bot configuration.
Some protection, moderation, setup, logging, or community features may need to inspect Discord events needed for that feature to work. Message content is only handled where it is required for an enabled feature, Discord permission, or approved intent. Swanatronics does not use Discord bot data for advertising profiles or data harvesting.
Discord bot data may be used to provide the bot, enforce protection or moderation settings, troubleshoot issues, investigate abuse, maintain security, and support server administrators.
Server owners and authorised administrators control which Swanatronics bots they add to their servers and how those bots are configured. Removing a bot from a server stops new bot activity in that server, although existing logs, configuration records, support tickets, or security records may remain where needed for reliability, abuse prevention, or legal reasons.
Nest Remote
Nest Remote stores node settings locally on your device. Node settings can include node names, hosts, ports, SSH usernames, pinned services, aliases, alert settings, and preferences.
Saved credentials such as passwords, private keys, and remembered passphrases are encrypted locally on the device. Node metadata is also stored locally using encrypted storage.
Nest Remote connects directly from the phone to nodes you add. It does not upload node settings, credentials, logs, backups, or alerts to Swanatronics.
Safe exports exclude passwords, private keys, and passphrases. Encrypted backups are user-created files protected by a password.
If you choose to include saved credentials in an encrypted backup, anyone with the backup file and password may be able to restore access to the saved nodes. You control where exports and backups are stored or shared.
Your setup stays on your device unless you choose to export or back it up.
Alerts
Nest Remote alerts are local app features. Alerts check selected nodes and services at intervals, so they are not instant.
Nest Remote does not poll nodes every few seconds in the background. Notification permission is requested only when alerts are enabled.
Support and Swanatronics Desk
Swanatronics Desk is used for support tickets and ticket tracking. Apps and services do not automatically upload telemetry, diagnostics, node settings, logs, credentials, backups, or support summaries to Swanatronics.
You choose what to paste, process, review, and submit. When a ticket is submitted, Desk may receive information you enter, such as product, issue type or category, severity, summary, what happened, expected result, steps to reproduce, optional app version, platform, and device details, optional contact method and contact detail, ticket status, history, receipt information, and normal server logs needed for security, diagnostics, abuse prevention, and reliability.
Anonymous bug reports and feature requests may be submitted without contact details. Support and testing requests may need contact details so Swanatronics can reply.
Ticket tracking uses a Ticket ID and access key shown on the receipt. Do not send passwords, private keys, passphrases, backup passwords, full SSH key files, API tokens, server secrets, or secrets copied from exports or backups.