AWAbideWay
Privacy & memory

You decide what may be remembered.

Remembered context may improve continuity. It never becomes biblical evidence.

Device Journey Graph

Structured journey summaries persist when you explicitly save them. The full conversation transcript is not stored by this memory layer.

Account memory

A separate AbideWay Supabase project stores account memory. Signing in alone does not upload device memory. You explicitly enable account memory before automatic synchronization begins.

Open account-memory controls

Cross-device continuity

After account memory has been enabled, later signed-in sessions can merge the approved Journey Graph automatically. Deletion tombstones stop a removed journey or memory from being recreated by stale data on another device.

Private mode

Private mode suspends new journey-memory writes and automatic cloud synchronization on that device. Existing saved data remains until you remove it.

User control

You can inspect, edit and forget individual memories, remove journeys, export device data, clear device memory, pause account memory, or sign out.

Reasoning boundary

User-approved memory may prevent repetition and make follow-up questions more relevant. It cannot change what Scripture supports or manufacture commands, promises, diagnoses or personal divine direction.

Security foundation

Every cloud user-data table uses authenticated owner-based Row Level Security. The browser receives only a publishable project key, which cannot bypass those policies.

Return to AbideWay