TexterryBack to Texterry

Privacy Policy

Last updated: 13 October 2026

The short version

Contents

  1. Who we are and what this policy covers
  2. Account, messenger, conversation and CRM information
  3. AI features and your controls
  4. Voice dictation and media handling
  5. Information on your Mac
  6. Device information, diagnostics and usage
  7. Payments and support
  8. How we use information and our legal bases
  9. Sharing and service providers
  10. No sale, resale or advertising use
  11. International transfers
  12. How long information stays
  13. Disconnecting and deleting an account
  14. Security
  15. Your choices and privacy rights
  16. California privacy notice
  17. Notes for EEA and UK users
  18. Other people's information and Business mode
  19. Third-party messengers and integrations
  20. Children
  21. Website visitors, Windows waitlist and storage technologies
  22. Do Not Track
  23. Changes to this policy
  24. Contact

1. Who we are and what this policy covers

Innolope LLC operates Texterry. “We”, “us” and “our” mean Innolope LLC. Our address and email appear in section 24.

Texterry is an Electron app for Mac combining Telegram, WhatsApp and Discord, with optional AI, dictation and a CRM and shared workspace called Business mode. Plans are Free, Plus and Pro; paid plans are coming soon. This policy covers the app, backend, website, Windows waitlist and support, including correspondents' and business contacts' information.

Our Terms govern the service. Their Delaware governing-law provision does not remove applicable privacy rights.

2. Account, messenger, conversation and CRM information

Information depends on your connections and features. Messages can contain almost any personal information, including sensitive facts you or a correspondent includes.

3. AI features and your controls

Texterry sends requests to Google's Gemini API for generation and transcription. Depending on the action, Google receives text, sender names, times and message identifiers, attachment descriptions, instructions, writing-style context, an existing lead summary, or audio. It returns text or structured results.

You choose, per chat, whether the assistant is off, reads and digests, or replies. The default assistant mode is off. Off prevents the assistant from capturing new messages for digests or automatically answering that chat; reading mode prepares digests without automatically replying. Reply modes can write as you or as a named assistant, depending on your settings. A stop control can stop automatic replies. Stopping replies and deleting stored information are separate actions.

Other AI actions have their own triggers. Asking for a draft or transcription sends the content needed for that action. Voice-message transcription can process incoming and outgoing spoken attachments as they arrive, separately from the assistant's per-chat mode. Business-mode automatic lead summaries follow the team's workflow settings. An assistant setting of off is therefore not a universal prohibition on every AI request associated with a conversation.

Gemini can describe your writing style using outgoing examples from the relevant chat or across recently active personal Telegram chats. Descriptions and example phrases are stored as context for later replies. This personalization is distinct from training a model.

Writing-style sampling is not restricted by each source chat's assistant setting. A chat marked off therefore should not be understood as an absolute prohibition on every AI use of its content. Turning off a chat assistant also does not disable the separate incoming transcription or Business-mode summary paths described above.

We do not train our own AI models on your messages. The application uses Gemini to generate responses and descriptions. Google's processing is governed by the Gemini API terms, which distinguish paid and unpaid services. Paid-service terms restrict product-improvement use but allow limited safety and abuse-prevention logging; unpaid-service terms can permit product improvement and human review. We do not make a blanket promise that Google never retains, reviews or uses submitted content. Those rules depend on the applicable service configuration and terms.

Digests appear in the app and can go to configured email or messenger destinations. They may contain names, summaries, actions, excerpts or original message lines. Choose appropriate destinations and review generated text before relying on it or sending it as your reply.

4. Voice dictation and media handling

Dictation starts when you use the microphone feature and allow microphone access on your Mac. The app records audio segments and sends them to our backend. The backend processes audio in memory, converts it to a suitable speech format and sends it to Gemini for transcription. The dictation flow does not save a recording in our application database or an audio-file archive. It returns text to the composer for review.

Dictation audio is not sent to correspondents. Sending the resulting text follows ordinary message rules. Google's terms govern its audio handling, including provider retention.

For Telegram, WhatsApp and Discord, photos, videos and files are not stored on our servers as a retained media library. Where media opening is supported, our servers may fetch a photo, video or file from the messenger and pass it to your app in transit without keeping a library copy. Telegram downloads use temporary memory buffers; WhatsApp media is fetched and streamed to the app. The current Discord integration records attachment descriptions and file names, rather than providing a general attachment download or upload service.

Sending an attachment through a supported feature transfers it to the messenger. Telegram uploads can use a temporary file on our server while delivery is attempted. The normal delivery path attempts to remove that file after completion or failure. An interrupted process, an early validation failure or failed cleanup can leave a temporary copy requiring removal; this is not a permanent media backup.

Transcribing a voice message or video requires the backend to receive audio, or extract the speech track, before sending audio to Gemini. This temporary processing is separate from keeping attachments as files. Your Mac can cache opened media and save files according to your saving choices and settings.

Transcription text, attachment metadata and small account profile pictures can be stored even though an attachment file is not. An expired, removed or protected attachment may no longer be retrievable from its messenger.

Channels that are not yet available may handle media differently; we will update this policy before they launch.

5. Information on your Mac

Electron's local app profile stores Firebase authentication state, inbox snapshots, cached message text, chat selections and scroll positions, notification preferences, storage settings and download progress to keep you signed in and show conversations quickly.

Viewed Telegram media can be cached in IndexedDB on your Mac without a separate manual save. The app also supports a local download folder and automatic saving rules. Current defaults enable saving new media from Saved Messages or self-chats, subject to the configured size limit. You can change the scope, limits and folder in Settings. The default folder is Texterry inside your Downloads folder.

Account deletion clears inbox snapshots but does not erase every cache, preference, export or downloaded file. Use storage controls and your Mac's file tools to remove local copies. Access to your unlocked Mac or its backups can expose local information.

6. Device information, diagnostics and usage

The app and backend use Sentry for crash and error reporting and performance tracing. Events can include device or operating-system information, app or environment details, stack traces, request context, URLs, timing information and technical events leading to an error. This is telemetry, used to operate and repair Texterry.

Specified Sentry reporting paths remove authorization and API-key headers. This scrubbing is limited: it does not guarantee removal of all identifiers, message content, URL parameters, request details or information included in an error. Avoid including secrets or unnecessary conversation content in support reports.

Production backend request logs record the remote network address, request URL and method, time, status, referrer and user-agent information. The address observed can depend on network proxies. Application logs also include operational identifiers, connection errors and, in some Telegram paths, phone numbers, authentication-related values and short message excerpts. These logs are separate from the message database.

Business mode includes team analytics derived from conversation timing, sent-message counts, handled conversations, assigned contacts, deals, completed tasks and pipeline changes. Owners and admins can see team performance; ordinary members receive their own performance row. These are workplace activity records. Sentry telemetry and Business-mode analytics constitute collection and use of information even though we do not use advertising analytics or cross-site tracking SDKs.

7. Payments and support

Paid Plus and Pro plans are coming soon. When you choose one, Creem handles payment as merchant of record. We receive billing references and subscription information, not your full payment-card details. Records can include your account and email, Creem customer and subscription identifiers, checkout references and URLs, plan, status, billing-period dates, cancellation details and team seat counts. A billing-event ledger records event identifiers and processing status to prevent duplicates.

Creem may collect payment, invoicing and tax information directly under its own notices. Account deletion is not a substitute for managing a subscription, and our deletion routine does not itself cancel a Creem subscription. Check your billing controls and contact support if necessary.

Support receives your email and submitted questions, screenshots, account details or diagnostics. Include only what is needed and remove other people's private content where possible.

8. How we use information and our legal bases

We use information to authenticate you, connect messengers, display and send messages, synchronize the inbox, run enabled AI actions, deliver digests, organize CRM records, operate team workflows and exports, administer plans, answer support requests, secure the service and diagnose failures.

Where the GDPR or UK GDPR applies, the appropriate legal basis depends on the purpose and our role:

9. Sharing and service providers

We use service providers to run Texterry and share information needed for their function. Providers' roles and legal obligations differ; a payment merchant, messenger or CRM may act as a separate controller for some processing.

HubSpot maps contact names, email, phone, company and lifecycle stage. Pipedrive maps person and organization details, an associated deal and stage or status. Attio, Zoho and Freshsales map names, email, phone and an associated deal and stage. We store external identifiers and sync status. These mappings do not export every message, note, task or deal field.

Telegram, WhatsApp and Discord receive messages you send through their connections. Team members receive information available within their authorized workspace. Configured digest destinations receive digest content. We may disclose information with your consent, to comply with lawful requests, protect rights or investigate abuse, or in connection with a merger, acquisition or transfer of the business, subject to applicable privacy duties.

10. No sale, resale or advertising use

We do not sell or resell your personal information or message content, use your data for advertising, run ads, or share information for cross-context behavioral advertising. Provider disclosures are explained above.

11. International transfers

Innolope LLC is a United States company. Providers may process information in the United States and other countries with different privacy laws; an endpoint does not establish every copy's location.

Where EEA or UK transfer rules apply, a transfer must have an appropriate legal mechanism. Depending on the recipient and circumstances, this may involve an adequacy decision, approved standard contractual clauses, a UK addendum or international data transfer agreement, and required additional protections. This policy does not certify any recipient's participation in a transfer framework. Contact us about locations and safeguards applicable to your data, including how to request a copy of relevant safeguards.

12. How long information stays

Retention depends on category, purpose, account or team relationship and legal requirements. Turning a feature off does not erase past results. Application retention differs from backup and provider retention:

Configured expiry periods require the relevant database indexes and expiry mechanisms to operate. They describe eligibility for scheduled deletion, rather than a guaranteed deadline for every physical copy.

13. Disconnecting and deleting an account

You can disconnect a messenger at any time and delete your Texterry account in Settings. Deletion tears down your connections and removes your account and associated personal data, including personal assistant records. Workspaces you own without other members are removed with their conversations, messages, CRM records and related data. The process also removes the Firebase login when the authentication service is available.

An owner cannot delete their account while they own a team with other members. The app asks them to resolve those memberships first. If you belong to another person's team, deletion removes your membership and hands over relevant open work, while shared-team records remain. A former-member record can retain your identifier, name, email and handover information to keep past work attributable.

Deletion does not erase messages from original messengers, other people's accounts, connected CRMs or delivered digest destinations. It does not erase downloads from your Mac or cancel an external subscription. Billing rows, temporary sign-in requests, diagnostics, logs and applicable legal records may outlast deletion, as described above.

If deletion fails or is interrupted, do not assume it completed. Retry through the app or contact support; no universal completion or provider-cleanup deadline is promised.

14. Security

Messenger sessions are encrypted at rest, traffic between the app and our servers is encrypted in transit, and the Mac app is signed and notarized by Apple.

Authentication tokens and ownership or team-access checks limit access to account and workspace functions. Administration and exports have additional role checks. The backend must use connection credentials and process message text to provide requested features; encrypted session storage does not mean that text is inaccessible to our service.

No system is perfectly secure. Contact us about suspected compromise. We will notify affected people and authorities of personal-data breaches as required by law.

15. Your choices and privacy rights

Settings control assistant modes, replies, digests, local storage, connections and account deletion. Depending on location, legal grounds and our role, your rights may include:

Write to support@texterry.com with your request and enough context to locate the information. Do not send passwords, session tokens or card details. We may proportionately verify identity or an authorized agent's authority before releasing or changing information.

Where the GDPR or UK GDPR applies, the ordinary response period is one month. A lawful extension of up to two further months may apply for complexity or multiple requests, with notice within the original period. Where the CCPA applies, requests to know, delete or correct generally require a response within 45 calendar days, with a permitted extension of another 45 days and notice. Identity verification and other timing rules apply as provided by law. These are statutory response periods, not guarantees that every technical erasure finishes within them. See the ICO's timing guidance.

Owners and admins can export clients, deals and tasks as CSV, or CRM records and conversations as JSON with optional stored messages. This does not export every account, log or provider record. Contact us for personal-data requests. We do not discriminate for exercising applicable rights. Lawful limits can protect other people or required records; we will explain an applicable refusal.

16. California privacy notice

CCPA rights apply where its coverage requirements are met. During the preceding 12 months, the following categories may have been collected or disclosed for business purposes through features used during that period; paid-plan collection applies when available.

Sources are you, connected services, teammates, device interactions and provider responses. Purposes, recipients and retention appear above. Transcription processes speech without creating an identification voiceprint.

We have not sold personal information or shared it for cross-context behavioral advertising during that period and do not do so now. We do not knowingly sell or share children's information or use sensitive information for ads. California residents can exercise applicable access, correction, deletion, sensitive-information and authorized-agent rights through the contact route above, without discrimination. You do not need to create an account just to contact us. See the California Attorney General's CCPA guidance.

17. Notes for EEA and UK users

For our account administration, website, waitlist, support and service operations, Innolope LLC is the controller deciding the purposes and means of processing. For business-controlled customer records, our role can instead be processor. The bases in section 8 and transfer considerations in section 11 apply where the GDPR or UK GDPR covers processing.

Messages may contain health, political, religious or other special-category information. An ordinary legal basis may not be enough to authorize processing it. Business customers must consider any additional condition required by law before placing it in Texterry or enabling AI.

Any duty to appoint an EEA or UK representative depends on applicable law and processing circumstances. Contact us about the appropriate local contact. You may complain to your supervisory authority independently of our support process.

18. Other people's information and Business mode

Correspondents may not have Texterry accounts. Consider their expectations before enabling AI, shared access, exports or external digest delivery. Permission to read a message does not automatically authorize every onward use.

A business managing customers generally acts as controller for those records; we act as processor where we handle them on its behalf under its instructions. The business is responsible for notices, a lawful basis, member access and customer requests. We separately control our account, billing and security processing. If your use requires a data processing agreement, contact us to discuss required terms before connecting customer data.

Team-scoped connections and CRM records are accessible according to membership and roles; a private connection is not shared merely because you belong to a team. Owners manage membership, and owners and authorized admins can export records and see team performance. Turning Business mode off hides its interface rather than deleting the workspace or revoking membership. Leaving a team does not delete its history. Correspondents and employees should contact the business controlling the record as well as us where appropriate.

19. Third-party messengers and integrations

Telegram, WhatsApp and Discord have their own policies, retention and account controls. Texterry sends through your connected account or authorized bot connection. Replies configured as an assistant can identify themselves as such.

Connected CRMs, payment checkout, email recipients and linked websites also have their own policies. Disconnecting Texterry does not erase information they already received. Review connection permissions and use providers' controls for requests about their copies.

Read the Telegram privacy policy, WhatsApp privacy policy and Discord privacy policy for their practices.

20. Children

Texterry is not intended for children under 16, and we do not knowingly collect their information as users. Contact support if a child supplied information directly. Businesses must consider age-related obligations for contacts; a child's mention in a conversation differs from using Texterry.

21. Website visitors, Windows waitlist and storage technologies

Our website consists of static files served by Cloudflare. It sets no cookies, stores nothing in your browser, including no localStorage, and has no analytics or advertising trackers. Cloudflare receives IP addresses and ordinary request information to deliver the site and keeps normal server logs. The website loads fonts from Google Fonts, so your browser makes requests to Google that disclose network information such as your IP address.

The optional “Texterry for Windows” waitlist asks for your email address. If you submit it, we store only that email, the platform value “windows” and a timestamp in a Cloudflare D1 database. We use it to email you once when Texterry for Windows is available. It is not used to market anything else and is not shared with other businesses for their own purposes. Cloudflare hosts the database for us.

Submitting the form is your consent to that specific notification. Joining the list does not create an app account or subscribe you to unrelated messages. You can withdraw consent and request deletion at any time by emailing support@texterry.com.

The app uses local storage, IndexedDB and authentication state for functionality as described in section 5. These are similar storage technologies, although they are not advertising cookies. External checkout, authentication or CRM pages may have their own cookie practices. Clearing local storage can remove preferences or sign you out without deleting server records.

22. Do Not Track

Texterry does not change its processing in response to browser Do Not Track signals. Our no-sale and no-advertising-sharing commitments apply regardless, including for California opt-out preference signals. Contact us about privacy rights.

23. Changes to this policy

We will update this date when the policy changes and notify you in the app or by email about meaningful changes. An updated policy does not replace any legally required new consent or notice.

24. Contact

For privacy questions, requests, concerns or information about business processing terms, contact us:

Innolope LLC, 8 The Green, Suite A, Dover, DE 19901, United States
Email: support@texterry.com