Permission by permission
How prayer synchronization works
The complete user journey, from first sign-in to account deletion, with each permission tied to the promise it enables.
Start
Onboarding
Identity only. No calendar access exists yet.
Create account or log in
Email and password, or OAuth sign-in.
uses:
Set up prayer space
Location, calculation method, school, selected prayers, duration, and buffers are stored in the app. No calendar permission is needed.
Prayer times calculated
Aladhan calculates saved Prayer Defaults. This is an external prayer-time source, not a user calendar permission.
Preview draft
Arihna Biha proposes Prayer Blocks before anything is delivered.
Community tier by default
1 active read-only Calendar Connection, without full sync or scheduling automation.
Choice
Choose a delivery path
The first calendar permissions appear here, and two of the three paths need no calendar OAuth at all.
Path A: read-only agenda
Show agenda context and detect conflicts.
Path B: email / export
Deliver Prayer Blocks without Google or Outlook OAuth.
Path C: nothing connected
Maximum privacy, in-app only.
Upgrade
Supporter full sync
The upgrade adds write access only when the user chooses full sync.
Become Supporter
Stripe subscription or admin grant. Payment changes entitlement, not calendar permission.
Supporter entitlement
Unlocks full sync, scheduling automation, and up to 2 active Calendar Connections.
Full calendar OAuth consent
Everything needed to choose calendars, plus the provider write permission.
adds:
Choose Sync Target
The user picks the writable provider calendar where Prayer Blocks should live.
chooses via:
Review, then write
Arihna Biha creates, updates, deletes, or restores only app-owned Prayer Blocks.
writes via:
Synced Events
Provider events owned and tracked by Arihna Biha.
kept fresh with:
Scheduling automation
Live rules retrigger on saved scheduling changes, Prayer Defaults changes, blocker agenda notifications, and writable target notifications. Scheduled .ics email follows its saved cadence.
Fallback dispatcher
Every 5 minutes, recovers dirty live rules and due .ics email rules. Clean direct-sync rules are not blindly recalculated.
Manual edit protection
Can respect Prayer Blocks moved in Arihna Biha and app-owned events moved or deleted in Google or Outlook.
Second Calendar Connection
Supporters can keep an extra Google or Outlook account for blockers, previews, and targets.
Token promise applies to every calendar permission
Deletion
Account deletion
Every permission granted along the way is unwound in order.
Delete account requested
Active Supporter payments stop. Scheduling and live sync rules are disabled.
Optional provider cleanup
Future Arihna Biha-owned Prayer Blocks can be deleted from provider calendars while write access still exists.
last use of:
Provider access cleanup
Google revocation is requested. Microsoft local tokens are removed, and the user can also revoke consent provider-side.
Final deletion and receipt
Local OAuth tokens, Calendar Connections, Agenda Sources, Sync Targets, feeds, Prayer Defaults, User-tied history, and the User account are removed. A deletion receipt is emailed.
Arihna Biha - permission model overview - gray = identity/read-only - gold = write access