Privacy Policy
Effective date: September 21, 2026
DeckSync does not collect, transmit, or store any personal data. Your slides never leave your device except over a local network connection that you initiate. The only internet traffic is your App Store subscription purchase, handled entirely by Apple — and a diagnostic log, if you ever choose to email one to support yourself.
1. Who we are
DeckSync is developed and published by Kojex ("we", "us"). This policy applies to the DeckSync app for iOS and iPadOS.
2. Data we collect
None. DeckSync has no backend servers, no analytics, no crash reporting SDKs, and no third-party libraries. We do not collect, process, or store any personal information.
3. How the app works
DeckSync connects nearby devices directly, using Apple's Network framework. Devices find each other with Bonjour and connect over the Wi-Fi network they share, or device to device over Apple's peer-to-peer Wi-Fi when there is no network. Every path stays on your local network. None reach the internet or any DeckSync server, and every connection starts with an explicit action by the person holding the device.
Each session is protected in one of two ways, and the presenter chooses which when starting it:
- With a PIN, everything sent in the session (slides, page changes, and the pointer) is encrypted with a key derived from the PIN. Devices that do not know the PIN cannot read it. The PIN itself is never sent over the network; a joining device proves it knows the PIN without transmitting it.
- Without a PIN, the session has no protection of its own. Anyone with DeckSync on the same network can join it and read the deck. The app says so when you start a session without a PIN.
The connection is also wrapped in Apple's TLS transport security, which shields it from casual observation but does not by itself verify which device is on the other end. A PIN does.
- PDF files are stored on your device. When you present, the app may transmit a copy to connected viewer devices over your local network so they can follow along.
- Presentation sessions operate entirely over your local network. No presentation content passes through the internet or any DeckSync server.
- Session PINs are stored locally on your device and are never transmitted, to any DeckSync server or to other devices.
- Names other devices can see: your device's DeckSync name (by default "DeckSync" followed by four characters, editable in Settings) and, when you present, the session name, which defaults to the file's name, are broadcast to nearby devices so they can find your session. Choose them with that in mind.
- Compatibility beacon: for six months after the 1.2 release, DeckSync also runs a small beacon over Apple's Multipeer Connectivity, including Bluetooth, so devices still on DeckSync 1.1 can be told that an update is needed. The beacon carries your DeckSync name and no presentation data.
4. Diagnostic logs you choose to send
DeckSync keeps a technical log of its own activity — connection events, errors, and state changes — in the device's standard system log. This log stays on your device. It is never uploaded, and the app never sends it on its own.
If you hit a problem, Settings → Share Diagnostic Logs lets you export a chosen time range (5 to 60 minutes) and email it to our support address. Nothing is gathered until you pick a range, and nothing is sent until you tap Send in your own mail app, where you can read the attachment first.
- What a log contains: timestamps, connection and error events, and app state changes.
- What it does not contain: your deck contents, deck filenames, session names, or device names. These are replaced with short one-way codes so we can follow which device did what without learning what any of them are called.
- Scope: a log only covers the current app session. Closing DeckSync discards it.
5. Subscriptions and payments
DeckSync offers an optional subscription managed entirely by Apple through the App Store. We do not receive or have access to your payment information, Apple ID, or billing details. Apple's privacy policy governs all purchase transactions.
6. Third-party services
DeckSync uses zero third-party SDKs. The only external service involved is the Apple App Store for purchases, which is governed by Apple's Privacy Policy.
7. Children's privacy
DeckSync does not collect data from anyone, including children under 13. Because no personal information is collected, the app is compliant with COPPA and similar regulations by design.
8. Changes to this policy
If we change this policy, we will update the effective date above. Because we collect no data, meaningful changes are unlikely.
9. Contact
Questions about this policy? Email us at [email protected].