Signaturesi
Legal Privacy Policy

Privacy, explained clearly.

This policy explains what information Signaturesi may collect, why it may be used, how it may be protected, and the controls available to users across NEO, Bean and Bean ID.

Effective date July 24, 2026
Version 1.0 Draft
Applies to NEO, Bean and Bean ID
Important publication note

This page is a product-ready privacy policy draft. Before public launch, replace all marked placeholders, confirm the actual backend and analytics providers, and obtain legal review for the countries where Signaturesi will operate.

01

Your information should have a clear purpose.

Signaturesi develops connected products for artificial intelligence and communication, including NEO, Bean and Bean ID. This Privacy Policy explains how information may be collected, used, stored, shared and deleted when you use Signaturesi websites, applications and services.

In this policy, “Signaturesi,” “we,” “our” and “us” refer to the operator of the Signaturesi services. The final legal entity responsible for the services must be inserted before public release.

Required before launch Replace this paragraph with the complete legal name of the entity operating Signaturesi.
02

Where this policy applies.

This policy applies to information processed through:

  • The Signaturesi website and related webpages.
  • NEO, including AI conversations, workspace features, personal memory and related account functions.
  • Bean, including messaging, presence, calling and communication features.
  • Bean ID, including account creation, authentication and unified identity features.
  • Support, security, research participation and product feedback channels operated by Signaturesi.

This policy does not automatically apply to third-party websites or services linked from Signaturesi. Those services may operate under their own privacy policies.

03

The information depends on the features you use.

Signaturesi may collect information you provide, information created through your use of the services, and limited technical information generated by your browser or device.

A

Information you provide

Account details, profile information, messages, files, feedback, support requests and preferences you choose to submit.

B

Service content

AI prompts, generated responses, communication content, project material and information saved through product features.

C

Technical information

Device type, browser type, application version, error reports, security signals and basic usage information.

D

Transaction information

Subscription status, product plan and payment confirmation information received from a payment provider.

04

One account across the ecosystem.

When you create a Bean ID, Signaturesi may process account information required to create, secure and maintain your identity across NEO and Bean.

Data category Possible examples Purpose
Account identity Display name, Bean username and profile image Create and display your account
Contact information Email address or verified phone number Authentication, recovery and support
Authentication data Password hash, login token and session records Protect access to your account
Account settings Language, theme, privacy and notification choices Personalize product behavior

Passwords should never be stored in readable plain text. The final authentication implementation and data flows must be verified before this statement is published without qualification.

05

AI interactions and personal memory.

When you use NEO, information may be processed to understand your request, generate a response, maintain conversation context and provide workspace functions.

NEO AI workspace
Data categories
Prompts and responses

Text, instructions and generated content within your NEO conversations.

Uploaded content

Images, files or documents you deliberately add for analysis or project work.

Conversation context

Temporary context used to keep the current conversation coherent.

Personal memory

Preferences or project information saved through an enabled memory feature.

Personal memory controls

A production version of NEO should provide clear controls to view, correct, disable and delete durable personal memory. Signaturesi should not describe these controls as available until they are fully implemented.

Model improvement

Signaturesi should not use private NEO conversations to train or improve general AI models unless the user is clearly informed and has provided an appropriate choice or consent. The final policy must reflect the actual production practice.

Recommended production position

Private NEO conversations should not be used for general model training by default.

06

Messaging and communication information.

When you use Bean, Signaturesi may process information required to deliver messages, maintain conversations, show availability and support voice or video calls.

Bean Communication
Data categories
Message content

Text, voice messages, images, videos, files and reactions shared through Bean.

Communication metadata

Sender, recipient, timestamps, delivery status and conversation identifiers.

Presence information

Online status, last active state, typing status or availability signals.

Call information

Participants, start time, end time, call status and limited connection diagnostics.

Encryption claims

Do not claim that Bean uses end-to-end encryption until the complete encryption protocol has been implemented, independently reviewed and verified across messages, media backups and calls.

Current wording Bean is being designed with privacy and controlled access as core product requirements.
07

Technical information used to operate the service.

When you access Signaturesi, certain technical information may be generated automatically. Depending on the final implementation, this may include:

  • Browser type, operating system and application version.
  • Device category, screen size and language settings.
  • Approximate location inferred from an internet protocol address.
  • Login time, session activity and authentication events.
  • Feature usage, page navigation and performance measurements.
  • Crash reports, diagnostic logs and security events.

Signaturesi should minimize this information and avoid collecting precise location, contact lists, microphone, camera or device files unless a feature requires access and the user provides permission.

08

Information should only support defined purposes.

Signaturesi may use information for the following purposes:

01
Provide the services

Create accounts, process requests, deliver messages and operate product features.

02
Personalize your experience

Apply your selected preferences, language, interface and enabled memory settings.

03
Maintain security

Detect unauthorized access, fraud, abuse, automated attacks and policy violations.

04
Improve reliability

Investigate errors, measure performance and improve the stability of Signaturesi products.

05
Communicate with users

Send account notices, security alerts, transactional messages and support responses.

06
Meet legal obligations

Respond to valid legal requests and maintain records where required.

09

Some features may depend on external infrastructure.

Signaturesi may use carefully selected service providers for functions such as cloud hosting, databases, artificial intelligence processing, content delivery, authentication, payments, email, error monitoring and analytics.

These providers may process limited information on behalf of Signaturesi according to their role and contractual obligations. The production policy must identify important provider categories and accurately reflect the final technical architecture.

Service category Possible purpose Final status
Cloud database Account and application data Confirm before launch
AI model provider Process supported NEO requests Confirm before launch
Hosting and delivery Serve websites and product assets Confirm before launch
Payment provider Process subscriptions and billing Confirm before launch
Analytics Understand aggregate product performance Optional

Signaturesi should transmit only the information required for the requested function and should not expose unrelated personal memory or communication content to external providers.

10

Signaturesi should not sell personal information.

Signaturesi does not intend to sell personal information to advertisers or data brokers. Information may be disclosed only in limited circumstances, including:

  • To service providers supporting Signaturesi operations.
  • When you direct Signaturesi to share information or connect an external service.
  • To protect users, Signaturesi or the public from fraud, abuse or security threats.
  • To comply with a valid legal requirement.
  • As part of a merger, acquisition, financing or transfer of business assets, subject to appropriate protections and notice where required.

Aggregated or de-identified information may be used for analytics and research where it cannot reasonably identify an individual.

11

Keep information only as long as it remains necessary.

Retention periods depend on the type of information, the feature being used, security needs and applicable legal requirements.

Account data While the account remains active

Some records may be retained briefly after deletion for recovery, fraud prevention or legal requirements.

NEO conversations Based on user settings

Conversation deletion and history controls should be implemented before final publication.

Bean messages Based on delivery and storage design

The final policy must match the actual message storage and backup architecture.

Security logs Limited operational period

May be retained to investigate unauthorized access, abuse or system incidents.

Deleting information from an active interface may not immediately remove encrypted backups or temporary recovery copies. Those copies should expire through a defined backup lifecycle.

12

Security is a continuous process, not an absolute guarantee.

Signaturesi intends to use technical and organizational safeguards appropriate to the nature of the services. These may include:

Access controls

Restrict internal and system access to authorized purposes.

Account isolation

Prevent one user from accessing another user’s information.

Secure transmission

Protect data while it moves between supported systems.

Monitoring

Detect suspicious activity, failures and security incidents.

No online service can guarantee complete security. Users should protect their login credentials, use trusted devices and report suspected unauthorized access promptly.

Read the Security page
13

Users should be able to understand and control their data.

Depending on the service, account settings and applicable law, users may be able to:

View

Access basic account information and saved settings.

Correct

Update inaccurate profile or account details.

Export

Request a copy of eligible information.

Delete

Delete selected content or request account deletion.

Restrict

Disable optional memory, analytics or personalization.

Object

Object to certain processing where applicable.

Signaturesi may need to verify the identity of the person making a privacy request before releasing, changing or deleting account information.

Contact the privacy team.

Replace the address below with a real monitored support or privacy email before launch.

privacy@signaturesi.com
14

Age requirements must match the final launch markets.

Signaturesi services are not intended for children below the minimum age permitted to create an online account in their country without appropriate parental authorization.

Before launch, Signaturesi must select a minimum account age, create an age-handling process and determine whether any product will support supervised accounts.

Decision required Confirm the minimum user age before publishing this policy.
15

Information may be processed in multiple locations.

Signaturesi may use infrastructure and service providers operating in different countries. As a result, information may be processed outside the country where a user lives.

Where required, Signaturesi should use appropriate contractual, organizational and technical protections for international transfers.

The footer does not need to display Pakistan or any other location. However, the final Terms and Privacy Policy must accurately identify the responsible legal entity, applicable governing law and a valid contact method.

16

Use only what the service genuinely needs.

Signaturesi may use cookies, local storage or similar browser technologies to maintain sessions, remember preferences, protect accounts and measure product performance.

If optional analytics or advertising technologies are introduced, Signaturesi may need to provide a consent banner and additional controls depending on applicable law.

Read the Cookie Policy
17

The policy may change as the products develop.

Signaturesi may update this Privacy Policy to reflect changes in product features, data practices, security requirements or legal obligations.

When a significant change affects how personal information is processed, Signaturesi should provide appropriate notice through the service, account email or another suitable channel.

The effective date and policy version shown at the top of this page should be updated whenever the policy changes.

18

Questions about privacy.

For questions, concerns or privacy requests, contact Signaturesi using a verified and actively monitored address.

Signaturesi Privacy Privacy and data requests
Draft contact
Legal entity To be confirmed
Business address To be confirmed