A connection for
each account.
Give your work mail and home calendar different VPNs. Each account gets the connection it needs, within the same app.
Work mail. Home calendars. Personal contacts. sec·o·sync finds the right connection for each account — so you don’t have to switch VPNs yourself.
In development · Android features documented below · Store links are previews
A VPN is a private connection to a network, like home or work. Your work mail and home calendar may need different ones. sec·o·sync handles each account separately — instead of asking you to choose one VPN for everything.
Give your work mail and home calendar different VPNs. Each account gets the connection it needs, within the same app.
Already on the right Wi-Fi or VPN? In “check first” mode, the app uses the connection you have. Accounts set to require their own VPN still use it.
Your existing VPN stays in place. On supported setups, sec·o·sync can even make its own connection through it.
The app opens the connection your account needs, shares it with related sync jobs and releases it after use. A short, configurable waiting period avoids needless reconnects.
Pick a situation. See how each account gets its own connection.
Your home calendar is already within reach. Only work mail needs its assigned VPN.
Illustrative connection choices. “Check first” respects each account’s policy; VPN-only accounts skip the direct check. Existing-VPN combinations depend on the network, build and access rules.
A configurable overview and quick access to your information — with the connection management underneath.
Android feature overview · documented in 0.3.1
Choose your dashboard widgets and hide sections you do not use. Accounts, VPNs and current issues stay easy to find.
Configurable overviewBrowse calendars, contacts, tasks and cached mail. Load a message when you need it; its contents are not fetched just because you opened the list.
Four everyday workspacesKeep reusable TOTP authenticators in the app, with protected widgets. Add them manually, scan a QR code locally or import supported authenticator files.
One-time codes, on deviceRefresh a resource yourself or use scheduled sync. See progress and issues in the activity history instead of guessing what happened.
Manual + automatic syncProtect account changes without stopping background sync, or enable the optional whole-app lock. Credentials use protected, encrypted storage.
You choose the access boundaryBack up accounts, VPN profiles and authenticators in a password-encrypted file, then restore them. This saves configuration — not your mail or calendar content.
Configuration backup + restoreThe VPN layer uses open-source engines: wireguard-go, OpenVPN 3 and OpenConnect. CalDAV and CardDAV bring open standards for calendars and contacts. You keep using your own compatible services.
Standard mail: IMAP / POP3 + SMTP. On-premises Exchange EWS is experimental; its mail uses separate standard-mail settings. IKEv2/IPsec is experimental too.
On Android, sync accounts integrate with the system. Calendars and contacts appear in compatible apps with the required permissions — not just inside sec·o·sync.
Mail and tasks use the app’s own stores and views; they are not universal system mail or task accounts. iOS does not yet have the same feature coverage.
Add mail, calendars, contacts or tasks. A guided setup helps you choose the services you need.
Assign a VPN to each account that needs one. Other accounts can sync without one.
It checks the connection, syncs your data and releases the connections it opened.
Use your existing service and VPN credentials. TOTP authenticators can be linked where supported. Interactive sign-in and your phone’s background limits still apply.
Setup, support and limitationsReach private services without putting a new cloud account in the middle. sec·o·sync connects to the services and VPNs you configure. No sec·o·sync relay, additional hosted sync service or separate sec·o·sync login is needed for that connection.
Storage, permissions and privacy boundariesUse accounts you already have. Your service and VPN providers remain involved; the app does not replace them.
Android Keystore-backed encryption protects account and VPN secrets. System calendars and contacts follow Android’s own access rules.
See sync stages, routes and failures. Detailed test logging is opt-in; review any diagnostics before sharing them.
A normal VPN decides which traffic goes where. sec·o·sync also knows which account is syncing, whether it is reachable, and when its connection can be released.
| What matters to you | No VPNCurrent network only | System VPNDevice / route rules | Per-app VPNRules for selected apps | sec·o·syncRules for each sync target |
|---|---|---|---|---|
| Different connections for different accounts in the same app | No VPN selection | Route-based, not account-aware | App-based, not account-aware | Yes — per target |
| Automatic, on-demand VPN | Not applicable | Depends on client / policy | Depends on client / policy | Yes — tied to account work |
| Checks availability before adding a VPN | No tunnel to add | Some on-demand rules can | Depends on client / policy | Yes — in “check first” mode |
| Can use an existing VPN | No VPN in this comparison | Depends on VPN combination | Depends on platform / client | Yes — when it routes this app |
| Own connection through an existing VPN | Not applicable | Depends on VPN combination | Depends on platform / client | Supported approach; setup-dependent |
| Releases its connection after account work | Not applicable | Not normally sync-aware | Not normally sync-aware | Yes — with a configurable delay |
| Can restrict an account to its assigned VPN | No | Via external routing policy | At app level | Yes — VPN-only policy |
The point is account-level control, not that other VPNs must stay on. System and per-app VPNs can overlap and may also offer on-demand rules. “No VPN” means no active tunnel; ordinary sync apps can also use a route provided by a VPN.
Read the conditions behind this comparisonYou shouldn’t need to understand networks to understand what the app does.
No separate sec·o·sync cloud account or relay is required for synchronization. You use your existing mail, calendar, contact and VPN access. You still need the relevant service credentials and, where required, permission to use the network. App-store access and any future purchase terms are separate.
A per-app VPN normally chooses a route for an entire app. sec·o·sync can choose a different profile for each sync target inside the app. It ties connection checks and connection lifetime to the account’s actual work. Other VPNs can also have automatic and on-demand features; account-level coordination is the difference.
Its own tunnels run inside the app rather than replacing the system VPN. A reachable account can use the existing route; another can establish its own tunnel through that route when supported. The outer VPN must carry and permit this traffic. This does not bypass kill switches, access policies or platform limits.
On Android, yes: selected calendars and address books are published through the system Calendar and Contacts providers, subject to permissions and app compatibility. Mail and tasks remain in sec·o·sync’s own stores. Locking sec·o·sync does not lock copies of calendar/contact data available to other permitted apps.
The Android interface supports reusable TOTP authenticators, local QR enrollment, supported file imports and protected authenticator widgets. Compatible VPN authentication can use linked TOTP codes. Push approvals, browser SSO and security-key prompts cannot be silently completed in the background. HOTP support in the shared core is not a finished Android enrollment feature.
The documented Android build includes DAV, standard-mail features and an experimental on-premises Exchange EWS adapter for supported calendars, contacts and tasks. Exchange mail uses IMAP/POP3 and SMTP separately. Microsoft 365 / Graph is not enabled. VPN engines include WireGuard, OpenVPN 3 and OpenConnect; IKEv2/IPsec is experimental. Check the compatibility guide for build and gateway limitations.
No. Expired credentials, interactive authentication or conflicts can need you. Android controls when background work runs; this is not a promise of instant or uninterrupted sync. You can also refresh manually and inspect the activity log.
No. These descriptions use the supplied 0.3.1 Android implementation documentation as their baseline, not an independently verified release. The iOS DAV/mirror foundation is not at Android feature parity; EWS is not implemented there, and native builds, device testing and store review remain release gates.
Mail, calendars and contacts — with the connection each one needs.
In development. Android is the documented feature baseline; iOS is not yet equivalent. Store links are placeholders.
Read the feature and compatibility guideSend your question to ADD ideas. The form is for project enquiries; please do not include passwords or account credentials.
You can also email us: kontakt@add-ideas.de