Sanchalan — Samay Sarathi

Samay Sarathi logo Sanchalan — Samay Sarathi

This page describes Samay Sarathi (published under the Sanchalan product page), a mobile app for structured, timed session plans on iPhone and Android — offline, on-device, and without an account.

Support: For questions, feedback, or assistance, contact us at sukashi.labs+support@gmail.com.

What the app does

Samay Sarathi runs session plans end-to-end on your phone: plan → run → log → share. One workflow supports personal routines and facilitated group programs.

Pillar In practice
Offline-first Primary actions work without a network. No cloud sync, no accounts.
Privacy-first No analytics, telemetry, or crash reporting in the MVP. Participant names never leave the device or appear on shared cards.
Phone-only iOS and Android, portrait orientation — no tablet or web build.
Background-safe Session timing and audio cues continue when the phone is locked or the app is in the background.

Activities

  • Create activities with a name and default duration; edit or delete your activities.
  • Three seed activities ship on first install (Warm-up, Main activity, Break) so you can run a session immediately.
  • Activities are snapshotted into plan steps when you create a plan — editing an activity later does not change plans that already used it.

Plans

  • Build a plan by ordering activities or ad-hoc steps; each step has a name and duration; total time is the sum of steps.
  • Saved plans are immutable — to change a plan, duplicate it and save the duplicate.
  • Archive plans to hide them without deleting; plans referenced by session logs cannot be hard-deleted.

Sessions (runner)

  • Start any plan to run a full-screen session with a live countdown and next-step preview.
  • A short audio cue plays at every step transition, including the end; cues use local notifications with bundled audio so they work when the device is locked.
  • Timing is drift-resistant (derived from elapsed wall-clock time). There is no Pause/Resume — use Break steps in the plan instead.
  • Skip advances the current step; End stops early. Every completed session creates a log automatically.

Logs & participants

  • Each finished session produces a log with an immutable link to the plan and start/end times.
  • You can later edit enrichment fields (participant counts or names, minutes-of-meeting notes, custom metadata). Plan reference and timestamps stay fixed.
  • Participants: optional count mode (by category) or name mode (names stay on-device and are never exported).

Share as image

  • Generate a minimalist share card from any log via the system share sheet.
  • Count-mode logs show category breakdowns; name-mode logs show only total count — names never appear on the card.
  • Rendering is on-device; nothing is uploaded for sharing.

Security (optional)

  • Optional app lock: Face ID, fingerprint, custom PIN, or skip — configurable under Settings.
  • Authentication gates app entry only; it does not replace OS protections for stored data.

Platforms

  • iOS (recent major versions) and Android (API 30+).
  • JavaScript-only fixes may ship via EAS Update; native changes require a new store build.

Privacy Policy

Last updated: May 2026

1. Application overview

Samay Sarathi is an offline-first mobile app. There is no user account, no sign-up, and no cloud sync. Your session data is meant to stay on your phone.

2. Why there is no “server-side” security risk for your session data

We do not operate a backend that stores your plans, logs, participant names, or notes. Because user-generated content is local only, there is no exposure of that data through our servers — there are no application servers receiving your session or participant information. Security questions common to cloud apps (breaches of a central database holding your data, account takeover against our API) do not apply to your app-managed session data in the way they would for a synced service.

Typical risks that remain are those inherent to any app that stores data on a physical device (e.g., device loss, someone unlocking the phone, OS-level issues). Optional app lock and device passcodes help reduce access by others.

3. Data storage and transmission

3.1 Local-first, no sync

  • No cloud sync and no shared accounts — by design.
  • No transmission of your plans, logs, participant names, or MoM text to us for app functionality.
  • Primary data lives in on-device SQLite.

3.2 Network use

  • The main outbound network activity described for normal operation is EAS Update polling for over-the-air JavaScript updates. That does not send your session content to us.
  • When you use the system share sheet, sharing is between your device and the app you choose (Messages, Mail, etc.) — not a dedicated Sarathi upload server for your logs.

4. Data collected and stored (on device)

Category Examples Notes
Plans & activities Step names, durations, ordering Immutable plans once saved
Session logs Plan reference, start/end times Core fields immutable after creation
Participants Counts by category; optional names in name mode Names are not placed on share cards
Notes & metadata MoM text, custom fields Editable enrichments on logs
Settings Security choice, participant categories Stored locally

5. Privacy characteristics

  • No analytics, no telemetry, no crash reporting in the MVP (as stated in product documentation).
  • Share cards never show participant names when names were captured — only totals appear for name-mode logs.
  • No sale of personal data — we do not operate an ad or data-broker pipeline for app content.

6. Data lifecycle

  • Data remains on the device until you delete it in the app or remove the app.
  • Uninstalling the app removes local app data unless the OS provides separate backup behavior outside our control.

7. Summary

  • Local session data: Plans, logs, and optional participant details are stored on your device; we do not sync them to our infrastructure.
  • No server-side repository of your session content — so no breach of “our cloud database” of your sessions.
  • Minimal tracking: No analytics/telemetry/crash reporting as described for the MVP.
  • Sharing: Share cards omit names in name mode; export is rendered on-device.
  • Updates: OTA updates may fetch JS bundles; they are not a channel for uploading your private log content.

For support inquiries, contact us at sukashi.labs+support@gmail.com.