Privacy Policy

Account information. Your email address and, where the sign-in method provides one, your name and profile photo. You can create an Inkenda account with Google, Apple, or an emailed sign-in link.

What you capture. Voice memos, photos, documents, typed notes, and forwarded emails you deliberately submit through the app, plus the contact and relationship information extracted from them: names, companies, facts, preferences, and dates you or the people you interact with have stated.

Device contacts, only with your permission.If you choose to import or search your phone's contacts, Inkenda reads the names, phone numbers, and email addresses you select or search against, never your full address book without an explicit action from you.

Google Calendar, only if you connect it. A separate, optional step from signing in, described in full below.

Ordinary technical data. Basic device and log information (timestamps, error reports) needed to keep the service running and diagnose problems.

If you choose to connect Google Calendar, a separate, explicit step from signing in, Inkenda requests read-only access to your calendar (the calendar.readonly scope) so it can prepare you before meetings with people already in your contacts.

What we access. Event titles, start and end times, location, and attendee email addresses, for events on your primary calendar. We do not read event descriptions, attachments, video-call transcripts, or any calendar other than your primary one.

Why.Attendee email addresses are matched against your existing contacts so Inkenda knows a meeting involves someone it already has a profile for. Matched meetings become timeline entries (the same as a voice memo or forwarded email, but tagged as calendar-sourced) and feed the cadence math behind Radar. About 30 minutes before a matched meeting starts, we send you a push notification with a short brief about that person, generated only from information you've already captured or corrected, nothing new is inferred from the calendar event itself beyond who, when, and where.

What we don't do with it.We never use calendar access to read or infer anything about unmatched attendees (people not already in your contacts), and calendar data is never used to train any AI model, ours or a third party's.

Storage and retention. Your Google access and refresh tokens are stored in our database (encrypted at rest by our infrastructure provider, Supabase), readable only by our backend services, never by the Inkenda app on your phone or in your browser. Disconnecting Google Calendar (Settings) immediately revokes and deletes the stored tokens; meeting-derived timeline entries already created stay, like any other captured interaction, until you delete the contact or your account.

Inkenda's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your captures are processed to extract facts, generate a short relationship brief, and draft message suggestions, all grounded in what you actually captured, never invented. This processing is done by third-party AI providers acting on our behalf under their own data processing terms, not to train their general-purpose models on your data:

• Anthropic (Claude) for extracting facts from your captures, generating briefs and message drafts, and reading business cards or screenshots.
• OpenAI (Whisper) for transcribing voice memos to text.
• Supabase for account authentication, database storage, and file storage. This is where your data actually lives.
• Postmark to receive email you choose to forward to your personal Inkenda forwarding address.
• Sentry for crash and error reporting, so we can find and fix problems. This is not linked to your account identity.
• PostHogfor product analytics (which features are used and how), linked to your account so we can fix what's actually broken for you, never sold or shared for advertising.

We do not sell your data, and we do not use it for advertising, ours or anyone else's.

Encryption in transit. Every connection between your device, our servers, and the third parties listed above happens over HTTPS/TLS. Nothing is ever sent in the clear, including during the Google OAuth handshake used to connect Calendar.

Encryption at rest.All data, including Google access and refresh tokens, captured artifacts, and extracted facts, is stored in Supabase's managed Postgres and storage infrastructure, encrypted at rest by that infrastructure. We do not maintain a separate copy of your data outside Supabase.

Access controls.Row-level security policies enforced at the database layer scope every table to the signed-in account that owns it, your data is not readable by another Inkenda user's session, by design, not just by convention. Google tokens specifically are never exposed to the client app (mobile or web); only our backend services can read them, and only to make the calendar read call described above.

Minimal scope, minimal retention. We request the narrowest Google scope that supports the feature (read-only calendar access, nothing else), and disconnecting immediately and permanently deletes the stored tokens rather than retaining them in a disabled state.

Vendor handling. The third-party processors listed above (Anthropic, OpenAI, Supabase, Postmark, Sentry, PostHog) act under their own data processing terms as processors on our behalf, not as independent owners of your data, and none of them are permitted to use it to train general-purpose models.

If something goes wrong. If we become aware of a security incident affecting your data, we will notify affected users without undue delay and take immediate steps to contain it.

These are product commitments, not just privacy ones, they shape how Inkenda is built, not only what this page promises:

• No personality profiling. No MBTI, DISC, Enneagram, Big Five, or similar inference about anyone in your contacts. No sentiment or emotion inference beyond what someone directly stated about themselves.
• No sending on your behalf. Inkenda drafts messages for you to review and send yourself, by copying them or opening your own email, messaging, or phone app. We never have the ability to send anything as you.
• No Gmail access. Inkenda does not request or use Gmail read scopes. Email context only reaches Inkenda through your own personal forwarding address, something you control and can stop using at any time.

You can correct or reject any fact Inkenda has captured, one tap from wherever it appears. Deleting a contact removes everything captured about them, claims, artifacts, and identities, permanently. You can stop using your forwarding address at any time by simply not sending mail to it.

We keep your data for as long as your account is active. If you delete your account, we delete your data within a reasonable period, except where we're required to retain records for legal or security reasons.

Inkenda is not directed at, and is not knowingly used by, children under 16.

If we make a material change to how we handle your data, we'll update the date at the top of this page and, where required, notify you directly.

Questions about this policy or your data: hello@stackedsolollc.com.