This policy covers Safe for iPhone and iPad, developed by Giuseppe La Guardia. For privacy questions or data requests, contact support@giuzzilab.com.
Data and accounts
Safe does not require an account. The developer does not receive or store the vault’s contents on their servers and does not sell data. The app contains no advertising, analytics, profiling or tracking across apps and websites.
Information stored on your device
Records, fields, passwords and PINs you enter, notes, history, categories, templates, loyalty cards, codes, logos and document front/back images are stored in the local archive encrypted with AES-256-GCM. Data is decrypted on the device while you use the unlocked vault. Search runs locally and does not send archive contents to search engines. Items you choose to share in iCloud groups are handled as described in the dedicated section.
Authentication and keys
Safe uses Face ID, Touch ID or the device passcode through Apple’s system services. The app does not receive biometric data. The archive key is protected in the iOS Keychain with user presence and is not sent to the developer. The device must have a passcode enabled. Values copied through Safe’s clipboard actions are limited to the local device and set to expire after 30 seconds.
Camera, photos and files
With permission, the camera reads codes or captures document sides. Images, PDF pages and files you choose through system pickers are processed on the device. Text and code recognition, cropping, rotation and data review run locally. Document data recognition is limited to supported Italian formats in the Italian interface; images and manual entry are available in English too.
Document images saved with a record are encrypted with the rest of the archive; reencoding removes personal photo metadata. Safe reads files you select, including images, PDFs, Wallet files, CSV, .vid, .safecard and backups. It has no general access to your Wallet library. Originals in Photos and Files remain managed by their respective services and are not deleted by Safe.
Device backup and iCloud Drive
When device backup is enabled and Safe is included, the encrypted archive and its migration-eligible key can be included in the encrypted backup managed by Apple. Safe cannot force or verify completion. Restoring this copy requires a full device backup restore.
You can also export a .vault file encrypted with a separate password to a location you choose in Files, including iCloud Drive or another provider. The destination receives an already encrypted file. Safe does not save the backup password. A .vault backup is a manual copy and does not synchronize the entire personal vault; iCloud groups separately synchronize only selected shared items. Cloud services follow their own policies.
Shared iCloud groups
Groups are optional. The owner chooses records and loyalty cards to share: the item’s fields, notes, codes, logos and document images synchronize with authorized participants through Apple’s CloudKit. Preexisting history, favorites and other vault preferences remain local. Group contents are encrypted before upload; the personal vault key is not shared. Cloud key handling uses Apple’s encryption services and participants’ iCloud configuration.
Each participant needs an iCloud account. Apple handles accounts, storage, transfer and technical information needed for invitations, record identifiers, permissions and participant status. The owner assigns view-only or editing permission and manages private invitations through links. The group name is encrypted; invitations use the generic Safe title. Invitation names and group status are also stored in the encrypted local vault. Synchronization happens while the vault is unlocked and can depend on network and iOS timing.
The developer does not operate a server for this data or receive group contents. Apple’s privacy policy also applies. Group updates are separate from manual iCloud Drive backups.
External connections for logos and email settings
Everyday vault use works offline. Some features connect to external services directly from your device:
- Logo lookup may search the loyalty program’s name on Wikidata and download an icon from the identified website. Card numbers, holders’ names, passwords, notes and photos are not sent.
- Website search sends the visible, editable search words to DuckDuckGo or Google in a nonpersistent web session.
- Email settings lookup may contact the provider’s domain and Thunderbird’s autoconfiguration service. It uses the domain needed for the lookup, not your password or full email address.
Service operators may receive your IP address, request time and ordinary network metadata under their own policies. Safe does not use a developer-operated server for these features. Web links you choose to open are handled by the browser or app you select.
Sharing, export and import
Text sharing happens at your request after selection and confirmation. Shared text and exported CSV files are unencrypted; protected fields are excluded from suggested selections and the initial CSV unless you explicitly include them. CSV excludes document images. Document copies exported as PDF or JPEG, delivered to apps or sent to AirPrint are unencrypted.
A .safecard file contains selected items with supported images and data, without the vault key. With a password you choose and confirm, the file is encrypted; without one, it is unencrypted as explained before sharing. The temporary copy prepared for the share sheet uses iOS file protection and is removed when the sheet closes. Recipients review and import an independent copy.
Apps, recipients, printers and providers you choose can retain copies that Safe cannot revoke. Imported files are read locally and not uploaded to developer-operated servers. An imported copy enters the local archive; selecting it for a group shares it through iCloud like other group items.
Widgets and app icon menu
Enabling quick access is optional for each record or loyalty card. Widgets and the app icon menu can show chosen titles, symbols and colors while the vault is locked. The widget uses a local copy of only these metadata and the information needed to respect the trial expiration; it receives no fields, passwords, notes, codes, photos or vault keys. Opening the contents requires authentication. Widget visibility also depends on your iOS settings.
Safe Free, trial and Pro purchases
Trial and reminder dates are stored locally in the Keychain, separately from the vault and .vault backups, without a developer-operated server. With badge permission, local notifications update remaining trial days or the count of expiring or expired documents. Flagged documents take precedence over the trial count. Badge notifications include no vault titles, values or images, sounds or Lock Screen alerts.
Expiry checks and summary acknowledgments are handled on the device, with acknowledgments stored in the encrypted vault. iCloud groups separately use silent CloudKit notifications to signal available updates, without unlocking the vault in the background.
Safe Pro is a one-time purchase processed by Apple through the App Store and StoreKit. Safe checks transactions and purchase entitlements through Apple’s services. The developer does not receive payment card details or Apple Account credentials. See also App Store & Privacy.
Retention and deletion
Local information remains in the archive until you delete it. Deleting a record, loyalty card or field removes its related history from the active archive. Earlier backups and exports may retain copies and need to be managed separately.
In iCloud groups, shared changes and deletions apply to the group according to permissions. The owner manages participants and revokes access. Losing access removes synchronized copies; linked personal copies and unsent local changes may remain in the personal archive. Revoking access does not delete previously exported or delivered copies. Restoring a .vault creates personal copies and does not automatically reactivate group links.
Uninstalling removes the app’s container but does not guarantee deletion of backups, data already shared through iCloud or external copies. Some Keychain information may persist according to iOS behavior. The developer cannot remotely access or delete the vault or recover a .vault password.
Support and contact
If you email support@giuzzilab.com, the developer receives your email address and the information you choose to send. These are used to respond to and manage your request and retained as needed for that purpose. Use the same address to request access, correction or deletion of correspondence data, subject to applicable requirements. Do not send passwords, PINs, backups or private vault contents. Use fictional data in screenshots.
Updates
This policy is updated when app features or the processing described here change. The revision date appears at the top of the page. Developer contact: Giuseppe La Guardia, support@giuzzilab.com.