← Back

Privacy

Last updated 2026-09-23

Contact imports and name-card scanning

Excel, CSV and vCard files are read on your device. Name-card text recognition runs in your browser; the card photo is not uploaded or retained by Kizuna. Review and correct the extracted fields before saving. Reviewed contacts are stored in the active device or account workspace. The capture inbox, circles and templates follow the same storage choice and are included in backups.

Your latest import, merge or organization operation keeps a recovery snapshot for undo. Undo is available for seven days and only while the workspace has not changed. The snapshot is replaced by the next organization operation, and removed when the account workspace or device data is cleared. Individual account-profile deletion also clears its recovery snapshot.

Kizuna is a personal notebook about the people in your life: who they are, what they like, key dates, reminders and notes. The information you enter is about real people, so this page says exactly where it goes.

When you use local mode, your relationships are saved in this browser (IndexedDB). Clearing site data deletes those local records. The storage label in Settings tells you which store is active. Export a complete JSON backup from Settings & data. Older local records are retained as a recovery copy when upgrading the app’s local data model.

When account mode is active, reads and changes go directly to your account database in Google Cloud. Account data needs an internet connection and is not stored in the shared offline browser cache. If this device already has local data, use Upload local data in Settings to merge it into your account. Signing in to an account that already has people opens that account’s data. Local records remain on the device until you use Clear this device or clear browser site data. Your Google account id, email, name and picture are used for your session; we do not receive your Google password. Sessions expire after seven days and can be revoked in Settings. Delete account workspace removes the personal account database records and revokes its sessions; shared-space deletion is described below; local and downloaded copies remain. Legacy Firestore backups, if any, remain separate from the account database until explicitly migrated.

Shared spaces require an account and stay separate from your personal workspace. Only fields you explicitly add or publish in a space are visible to its current and future members. Copying a personal contact starts with the name only. Members see each other’s names and email addresses. Owners invite a specific email as a viewer or editor using a single-use link that expires after seven days; you send the link yourself. Editors can change shared records; viewers can read them. Every request checks membership and role.

Notes start private to their author, including from the space owner. Private notes do not appear in another member’s search, exports or shared activity. Shared-space content is not included in personal AI assistance. Each member can separately opt in to generic reminders for tasks assigned to them and events in that space; names and note contents are not sent in notifications. Shared records and your own private notes have separate JSON exports in the space; personal backups do not contain spaces. Owners can restore shared archives after reviewing a preview; members can restore their own private-note archives. Restore adds new copies, remaps internal links and clears assignments; it never restores membership or author identity. Space data is held in page memory and is not saved to the offline cache.

Revoking access blocks future requests but cannot recall records already viewed or downloaded. An open page checks access periodically and on focus. Revoked members’ private notes remain inaccessible to other members and can become available again if the author rejoins. Leaving a space deletes your private notes there; shared contributions remain. Deleting your account deletes all spaces you own for every member, deletes your private notes elsewhere and removes your author identity from shared contributions in other spaces. Names or details you wrote in shared record text remain until edited by a member. Archiving a space pauses member access and can be reversed by its owner. Owners can offer ownership to a current member, who must accept within seven days. The previous owner becomes an editor. Owners can permanently delete archived spaces after typing their name; editors can permanently delete archived shared records. References to deleted records are detached. Downloads and text copied elsewhere cannot be recalled.

Assistance is optional and requires sign-in. Before each request, you choose up to 40 saved records and review their names, text, types and dates along with your question. Only this selection is sent through Kizuna to Google Vertex AI (Gemini). Hidden, archived, private-marked and AI-excluded records are not offered to assistance. Exclusions also apply to memories derived from those records. Other profile fields, plans, inbox items and contact details are not automatically included. Generated suggestions cite source excerpts but may still be wrong. Results remain in page memory until you explicitly save reviewed tasks/dates or copy a message draft. No messages are sent. Saved items include source-record identifiers and follow your active storage and backup settings. Memory review does not need AI. Exclusion is not encryption and cannot recall data already sent; copies and previously saved results remain until edited or removed. We do not log prompts or provider response contents.

  • Sell your data or use it for advertising or analytics profiling.
  • Send messages to your contacts or generate AI suggestions automatically.
  • Write the contents of your notes into server logs.

When you choose to connect Google Calendar, Kizuna requests read-only access to calendar events and calendar properties, and reads your primary calendar directly in your browser. The short-lived access token stays in page memory; it is not stored in your backup or sent to Kizuna’s server. You select events before their titles, dates, time zones and locations are saved to your chosen device or account storage. The calendar identifier is saved with each imported event to distinguish calendars. Older imports can be linked only after explicit review. Calendar imports are manual and do not send invitations or change your Google events. Disconnecting stops further reads and asks Google to revoke access; saved plans remain until removed. Removing Google access may require signing in again for other Google features.

Plans, attendance, introduction permissions and gift ideas remain private to your own space. Recording an introduction or RSVP does not contact anyone. Logging attended contacts copies a summary of the plan’s outcome into the selected attendees’ saved histories.

When you enable notifications, Kizuna stores your browser’s push subscription and associates it with your signed-in session. Encrypted, generic reminders pass through your browser provider’s push service; names and personal notes are not included. Clicking a reminder opens Kizuna, where normal account access checks apply. Quiet hours and your chosen time zone control scheduled sends. Signing out, session expiry, disabling this device, or deleting your account stops future sends. A notification already accepted by the browser provider may briefly remain in transit. Delivery records retain an opaque occurrence identifier and delivery status, not note contents.

Archiving a person hides them from daily views but preserves their history. Restore archived people in Settings. Archiving is not deletion. You can permanently delete individual memories from their editor after typing DELETE. This clears the latest undo snapshot; derived records and downloaded backups remain until removed separately. Clearing browser site data removes local records; it does not remove account records. For permanent account-data removal, use the authenticated Delete account workspace control in Settings & data. Export your data first if you want a copy. Signing out clears your session cookie on this device and removes any old shared Kizuna caches.

Kizuna is run by its owner as a personal project at kizuna.you. Questions or deletion requests: use the contact details on the account you signed in with, or the project repository if you were given access.