Dukara keeps a trainer's client records in one place: contact details, body measurements over time, training sessions with their content, and a running balance of paid-for sessions. A trainer signs in with their Google account and sees only their own clients.
Read the Privacy Policy, Terms of Service, and Google API Limited Use Disclosure.
Dukara is used by individual personal trainers running their own practice. Each trainer's data is theirs alone — one trainer never sees another's clients, measurements, or payments.
Dukara asks for two things, and only these. Full detail is in the Privacy Policy.
When a trainer signs in with Google, Dukara receives the name, email address, and profile picture on that account. These identify the trainer inside the app, so their client records follow them to any device and so the app can show whose account is signed in. They are not used for advertising, not sold, and not shared with anyone.
Connecting a calendar is optional. It can be declined at sign-in, or disconnected later, and every other feature keeps working either way.
When a trainer connects a calendar, Dukara requests two narrow Calendar scopes:
calendar.app.created) — Dukara makes one dedicated calendar
of its own and writes session events to it. It never modifies any
calendar it did not create.calendar.freebusy) —
returns only opaque busy blocks, so sessions are not booked over existing
commitments.Neither scope can read the title, guests, description, or location of any event in the trainer's other calendars. Calendar data is used solely to schedule and display training sessions inside the app.
Testing the app? Get the test build.