Skip to content
R Revisync
Features How it works Documentation Articles
More
Support Privacy
◎ PT-BR — Português (Brasil)
R Revisync

Navigation menu

Features How it works Documentation Articles Support Privacy
◎ PT-BR — Português (Brasil)

Revisync

How we protect the local database

Revisync uses local storage and SQLCipher to protect the database file from casual reading by other applications.

What is protected

The database lives in the app’s private directory and is encrypted with SQLCipher. The key is supplied by the application, so you do not need to type a password to use the app or restore a compatible backup.

Important limits

The first-version key is embedded in the APK. This means the protection is not designed to resist someone who can analyse or modify the application. Its main purpose is to prevent casual access to the local file by other apps.

Backups

A complete backup starts only when you request it. If you choose Google Drive, iCloud Drive, Files or another provider through the system picker, the file leaves Revisync’s private storage and also becomes subject to the security and privacy rules of the provider you selected.

What we do not claim

Revisync does not describe this storage as zero-knowledge, end-to-end encrypted or invulnerable. There is no automatic cloud synchronisation in the MVP.

Read the privacy policy

Revisync

Revisync — a Galcore Studios product

Product

Features How it works Download

Learn

Documentation Articles

Help

Support FAQ

Trust

Privacy Data security

Company

Galcore Studios Contact
© 2026 Galcore Studios. All rights reserved. Revisync Privacy