1. Who we are
Ink Thought Labs Inc. operates Inkling, including the app and heyinklings.com. This policy explains how we handle information when you use those services. For privacy questions or requests, contact support@heyinklings.com or write to us at 650 Chestnut St #209, San Francisco CA 94133.
2. Information we collect
The information we handle depends on the features you use:
- Account information: sign-in details, email address, chosen name, preferences, permissions, and account settings.
- Content: messages, generated replies, photos, documents, attachments, voice recordings and transcripts, reminders, tasks, and things you create with an inkling. This can include sensitive information you choose to provide.
- Saved context: memories, summaries, preferences, and search indexes, including numerical representations called embeddings used to retrieve relevant information. These can contain or be derived from personal information; they are not automatically anonymous.
- Shared activity: membership, invitations, roles, group messages, and records such as polls and bill splits.
- Connected accounts: account identity, authorization tokens, and information obtained through optional connections, including the Google data described below.
- Browser activity: website addresses, screenshots, action results, and saved browser state such as cookies and local storage. Saved logins can include usernames, passwords, and authenticator secrets you choose to store.
- Operational information: network addresses, request and error records, device and app characteristics, notification delivery information, and messages you send to support.
3. How we use information
We use information to sign you in, generate replies, remember relevant context, maintain conversations and creations, run shared spaces, deliver files and notifications, and carry out the features you request. Inkling is not entirely on-device: relevant information is processed on servers and shared with service providers.
We use non-connector information, such as content you provide directly, feedback, and usage information, to improve the product experience, including its usefulness, reliability, and personalization. This does not include information obtained from connected services or information derived from it, even when copied into a chat, summary, memory, or other record. Google information is governed by the separate commitments below.
We also use information to troubleshoot failures, protect accounts and the service, monitor and prevent abuse, answer support requests, and meet legal obligations. We do not sell personal information or share it for cross-context behavioral advertising.
4. Connecting Google
Connecting Google is optional and separate from signing in to Inkling. We request access to Gmail, Calendar, Drive, Docs, and Sheets. Google’s permission screen shows the access requested, and you choose what to grant. Some features may not work with a partial grant and may ask you to reconnect. Choosing a task does not narrow an account-wide grant to just the email or file involved.
Gmail and Google Drive access is not available in shared spaces at launch. The separate busy-time sharing described below is still available. A restriction on direct access does not itself erase information already saved in a conversation or memory.
We store access and refresh tokens so the connection works without signing in for every request. Google provides these tokens; connecting does not give Inkling your Google password.
Relevant Google information can be shared with our AI providers to answer you and carry out your requests. It can become part of conversation history, tool results, summaries, memories, and retrieval indexes. Downloaded email attachments and Drive files can also be saved as files on our servers, separately from a conversation. See retention below for the limits of removing these copies.
Connecting an account is not an instruction to send an email or change a file. Only request actions you are authorized to take. Actions can affect other people and services; not every action has a separate confirmation screen.
- Account identity: your name, email address, and basic profile identify the connected account.
- Gmail: messages, participants, subjects, labels, drafts, and attachments support finding and summarizing mail, drafting and sending messages, and organizing your mailbox.
- Calendar: calendars, event details, attendees, and availability support scheduling questions and creating or updating events.
- Drive: file names, metadata, and accessible file content support finding, downloading, organizing, and working with files. Access can extend beyond files created by Inkling.
- Docs and Sheets: document text and spreadsheet content support reading, summarizing, creating, and editing documents and spreadsheets.
- Space scheduling: “Share my busy times here” is off by default in each space. Turning it on lets that space’s inkling retrieve your busy time blocks, up to a year ahead, to help other members schedule with you. This sharing supplies busy times, not event titles or descriptions. Connecting Google alone does not turn it on.
- Space invitations: an inkling can create an event on a requesting member’s calendar and invite other members who have busy-time sharing on in that space. Google sends the invitations by email. The inkling is instructed to ask the organizer to confirm in the conversation; this is not a separate app approval screen. Turning sharing off does not recall invitations or information already shared.
5. Google data and Limited Use
Inkling’s use and transfer of Google API data will adhere to the Google API Services User Data Policy, including its Limited Use requirements. These commitments cover raw, aggregated, anonymized, and derived Google Workspace information, including summaries, memories, embeddings, and notification previews.
We use this information only for the disclosed, user-facing features you choose. We do not sell it, use it for advertising or credit decisions, or use or retain it to develop, train, or improve generalized or foundational AI models. It is excluded from the broader non-connector product-improvement use described above. Generating an answer for you is different from training a model for other people.
Transfers are limited to what is necessary to provide or improve those features with your consent, for security, or to meet legal requirements. A transfer as part of a sale, merger, or asset transfer requires your prior explicit consent. Our processors must follow the same applicable restrictions.
People may read Google data only with your affirmative agreement for specific information, when necessary to investigate abuse or a security problem, or when the law requires it. Any use of anonymized aggregate information for internal operations must meet Google’s restrictions. A support request is not permission to inspect unrelated mail or files.
7. Service providers and other disclosures
We share information with service providers that help operate Inkling, for the purposes below. Our Google Limited Use commitments still apply when a provider processes Google information.
Websites you visit through Browser receive the interactions and information sent to them under their own privacy practices. Messages, invitations, and files sent through connected services are available to their recipients. Disconnecting a service does not recall completed actions.
We may disclose information when required by law or necessary to address fraud, abuse, or security threats. A business transfer must respect applicable law and the additional consent restrictions for Google information.
- Authentication, database, hosting, and storage providers process account details, tokens, conversations, saved context, files, and operational records needed to run the service.
- Anthropic, the company behind Claude, is our AI provider. It processes relevant prompts, messages, retrieved Google information, files, and tool results to generate replies. Inklings can send your messages, and others’ messages in a conversation you share, along with names, time zone, memories, documents, and tasks. Embedding providers may process text to build retrieval indexes. Transcription providers process voice recordings to produce text.
- Search and remote-browser providers process queries, websites, instructions, screenshots, and browser/session data needed for requested work. A saved login can be used to sign in to a website you authorize.
- Push notifications travel through Expo and Apple or Google notification services. They include device delivery information, the sender’s name, and a message preview. A preview may contain Google-derived information, such as part of an email summary. Device settings control notifications and their visibility on your lock screen.
- Support and security providers process records needed to handle requests or investigate failures and security events.
- When you report a message, the message and up to four messages before it that you could read are kept for a person on our team to review, including after an account is deleted. We delete that copy 90 days after the report is handled.
- An inkling in a shared space may use what it remembers from any of its conversations, including your private chats with it, when it talks with the space’s other members. That applies while you are a member and after you leave: if you leave, your private chats with its inklings are deleted, but what an inkling saved from them, such as memories and documents, stays with that inkling.
8. Service and website records
Request, error, and security records help us deliver, troubleshoot, and protect the app and website. They can include network addresses, device or browser characteristics, and the time and outcome of a request. These operational records are separate from any optional usage-analytics controls.
Signing out, disabling notifications, or uninstalling the app does not itself remove records already held by Inkling or its providers. Contact us if you have a question about information collected when using the service.
9. Retention and account deletion
We keep account information, conversations, uploaded files, and saved context for continued use, rather than deleting them when a task ends. Retention depends on the kind of information and why it is needed.
You can request account deletion in Settings. Deleting your account also deletes the spaces you own, including their conversations and inklings, for everyone in those spaces. Before you confirm, we name the owned spaces that still have other members. Those members keep their accounts, the spaces they own, and the inklings in those spaces.
The acknowledgement confirms that we received your deletion request, not that deletion has finished. A request can be held when cleanup cannot safely complete. Contact support@heyinklings.com for help with a pending request.
Account deletion closes access, stops active work, and removes your sign-in, private account content, associated memories and indexes, covered conversation transcripts, connection records, uploaded files, saved logins, and saved browser state. The exceptions below explain what can remain. Disconnecting Google, signing out, or uninstalling the app is not account deletion.
- Deletion requests: we keep a limited cleanup record, including internal account and sign-in identifiers, a hashed email address, and cleanup status, for 30 days after deletion completes. This helps track fulfillment and prevent interrupted work from restoring a deleted account. The record is then deleted.
- Operational database records: a 30-day limit applies to tool-call and tool-result content in database records we can reliably link to your inkling. After expiry, the service’s record-reading features hide that content and scheduled cleanup clears it. Outages or a backlog can delay physical cleanup. Limited identifiers, timestamps, status, and processing safeguards remain. Older audit records that cannot be reliably linked are not covered by this automatic cleanup.
- Server-side conversation journals: these records can include full tool results, not only the replies you see. They have no automatic age-based expiry and are outside the 30-day database cleanup. We remove your account’s inkling journals during account deletion, and an owned space’s inkling journals when that space is deleted. The shared-record, backup, and provider-copy limits below still apply. The database limit is also not an expiry period for saved conversations, files, or memories.
- Google connection: disconnecting removes the selected saved connection and requests Google revocation. If revocation fails, remove access in your Google Account. Disconnecting does not erase retrieved content, conversation copies, memories, summaries, or embeddings.
- Downloaded Google files: account-linked email attachments and Drive files downloaded to our servers are removed during account deletion. Older downloads stored without account ownership can remain in shared storage after deletion because we cannot reliably associate them with an account. Downloads have no automatic age-based expiry. Contact support@heyinklings.com about removing older copies.
- Browser: saved cookies and other browser state can outlast a task. Ending a session is not the same as signing out of websites or clearing saved state. Content saved in conversations follows conversation retention rather than expiring when a browser task ends.
- Shared records in spaces you do not own: shared conversation history may remain with account attribution removed. Bill-split facts and poll participation can also remain, including participant or vote references. Removing a name or creator attribution does not make every shared record anonymous. Deletion does not remove copies another person has kept or undo actions in other services.
- Other retained records: limited information may be kept where required by law or needed to address a specific security or abuse incident. Backups and provider-held copies may persist beyond removal from active systems under their retention processes. Contact us for help with a particular deletion request.
10. Your choices
You choose what to provide and whether to connect optional accounts. Device settings control permissions such as microphone access and notifications. Busy-time sharing is a separate choice in each space. You can disconnect Google in Inkling or remove authorization in your Google Account, including when Inkling is unavailable.
Contact support@heyinklings.com to request access, correction, a copy, or deletion of personal information. We may need to verify your identity and authority. We will explain any applicable exception or inability to complete a request and will not penalize you for exercising privacy rights.
Depending on where you live and which laws apply, you may also have rights to object to or restrict processing, withdraw consent where processing relies on it, appeal a request decision, or complain to a privacy regulator. Contact us to exercise applicable rights; contacting us first is not a condition of contacting your regulator.
11. Security and processing locations
We use authenticated access and permission checks to limit access to account resources. No system can guarantee absolute security. Do not put passwords or authenticator secrets into ordinary chat; use the dedicated saved-login controls.
Inkling and its providers process information on servers that may be outside the place you live. Availability in a country does not mean all processing stays in that country.
12. Age and safety
Inkling is for people aged 18 and older. It is not intended for children.
If you believe a child has provided personal information to Inkling, contact support@heyinklings.com so we can investigate and take appropriate action. Inklings are AI-powered, not human. Inkling is not an emergency or medical service, and messages are not continuously reviewed by a person.
13. Changes and contact
We will identify the effective date of changes and notify you of material changes through the app, email, or another appropriate channel. We will obtain any required new consent before using information for a new purpose, including connected Google data.
Questions and requests: support@heyinklings.com.