Skip to document
Review version · not yet effective

Privacy policy

How account, conversation and attachment data is handled when you use SocialHamster.

Last updated:

On this page

Responsible entity and scope

SocialHamster is a product of EGYWARE LTD, company number 17522376, at 128 City Road, London, EC1V 2NX, United Kingdom. Contact info@egyware.com about the product or your data.

This policy covers account, workspace, team, channel and conversation data. A business normally determines the purpose and permissions for communicating with its customers, and we may process those conversations to provide its service. Service-account administration, security and purposes we determine ourselves require separate assessment; not every additional use is merely following the business's instructions.

Data we process

Data depends on your use, enabled features/channels and granted permissions. Relevant categories, to the extent supplied or generated, include:

  • Central-account, company and team-member details, roles, permissions and workspace settings.
  • Connected-page, account and phone-number identifiers, access permissions and necessary connection tokens; support does not require you to send social-platform passwords in a chat.
  • Messages and comments permitted by the channel, participant names/identifiers, timestamps, delivery/read/assignment states, notes and associated action history.
  • Images, audio, video, documents, attachments and their metadata within supported types/sizes and what the service actually receives.
  • Automation requests, replies and success/failure records, billing/transaction/receipt/support/usage/security/analytics data as applicable, without storing full payment-card details.

Data sources

Data comes from you, your team, people communicating with your business channels, connected platforms within their permissions, agent providers you choose to enable, and operational records.

The service may receive new messages or authorized imported/transferred data. Connection does not imply complete historical or attachment import; source permissions and limits determine what can be transferred. Stored messages, attachments and actions remain associated with their workspace context.

Service operation and support

We use data to operate the inbox, receive/display messages and send replies, manage channels/files/team/assignments/permissions, provide search/context/enabled automation, bill and measure use, protect security, prevent abuse and diagnose faults.

When you enable an agent, SocialHamster sends its provider the request context and data needed for the task within the integration and permissions. An agent does not mean every company record is sent to every ecosystem product or every employee can read every conversation.

Authorized staff may access relevant data when necessary for support or fault investigation without a prior customer request. This is not unlimited access for every employee for any purpose.

The processing basis depends on purpose, data and relationship, such as contract necessity, legal obligation, assessed legitimate interests or valid consent where required. Reading this policy or accepting terms does not make every processing activity validly consented to.

Providers and recipients

The service may involve AI-operation, hosting, storage, payment, connected-channel, analytics, marketing and support providers. Data and recipients depend on the relevant service, purpose and arrangements, not an unrestricted sharing authorization.

Some processing may take place outside your country depending on recipient locations. Transfers remain subject to applicable requirements and safeguards. No local-only processing or universal provider no-training promise is made.

Improvement, model training and data licensing

Proposed additional data uses include original-form conversations and attachments for improving EGYWARE or other companies' products, including training their or their providers' AI models, and paid sale or licensing of data. These are additional uses, not merely providing the requested service.

No separate consent choice for each training use is proposed, but accepting terms does not create blanket legal authorization or replace a suitable basis, individual rights or required consent/objection mechanisms. Describing proposed uses does not establish that training or sale currently takes place.

These secondary uses exclude passwords, access keys, payment details, sensitive personal information, children's data and confidential business information such as internal contracts and non-public customer lists. This does not prohibit necessary service/payment processing.

Data obtained from an external platform is also subject to that platform's permissions and terms. This clause does not permit training, sale or licensing of connection, conversation or platform data where prohibited by the source terms or outside granted authority. Publishing this wording does not automatically enable training or sharing.

Marketing and cookies

Marketing permission is optional and separate from terms acceptance. Registration can be completed without it, and marketing stopped later without closing the account. Necessary account/service messages are distinct from promotions.

Marketing permissions depend on the channel and applicable requirements; one generic approval is not assumed to cover every channel.

Necessary service cookies differ from advertising tracking. Consent-requiring tracking must not begin before consent. The proposed controls offer accept, reject and customize, with a footer Cookie settings link to reopen choices including for signed-out visitors.

Retention and capacity

Service-data retention is tied to available account capacity. On exceeding it, the customer is notified and has seven full days to reduce use or obtain capacity; only then is excess data eligible for system-selected deletion. No fixed numeric quota for every account is stated.

Required financial records are retained within the relevant obligation's scope and duration. Keeping a financial record does not justify automatically retaining all conversations and attachments.

Data may remain after closure or access revocation where retention is legally permitted or required, for an appropriate purpose and period, subject to applicable rights requests. Continued secondary use during recovery is subject to the same requirements; revoking access is not data erasure.

Disconnecting channels and deleting their data

An authorized member can manage connections in channel settings where supported and revoke the app's access from the external platform. This can affect incoming messages, sending and automation. Revoking connection permission differs from erasing messages/files saved earlier.

To request deletion of data linked to a channel or conversation, contact info@egyware.com with the business/platform name and an identifier that helps locate the data, without passwords, login tokens or unnecessary personal data. If you are a customer of a business using SocialHamster, you can also contact that business as the organization you deal with.

We assess the request's scope and the requester's authority and may need proportionate identity/authorization checks. Applicable rights, deadlines and exceptions apply; an account-recovery period does not postpone every erasure request for three months. This page does not claim an automated platform-deletion button or callback is enabled where it is not.

Deletion and data rights

The main account holder requests deletion through the dashboard. This covers its companies, teams and data within its scope, with three calendar months for recovery. Ordinary use stops and sign-in is limited to recovery/deletion management.

Renewal stops on request and does not restart automatically after recovery. No pre-deletion export feature is promised. Account recovery differs from statutory erasure and required record retention.

Depending on applicable law, individual rights may include access, correction, erasure, restriction, objection, portability, withdrawing consent and complaints to a competent regulator. Rights have conditions and exceptions; absent buttons or support guarantees do not determine legal deadlines.

Minors

Registration is intended for ages 13 and over without a general under-18 guardian-permission condition, except where applicable law requires a higher age or permission. Data-consent age alone does not settle contractual capacity.

Children's data is excluded from secondary training, improvement and sale/licensing uses, subject to appropriate child-protection requirements and safeguards.

Public information and updates

Conversations, attachments, notes, team directories and connection details are not public merely because they are stored in SocialHamster. Any publishing or action toward a connected platform depends on an enabled feature, authority and intended destination; we do not assume permission to show your inbox publicly.

Customer-name/logo publicity is covered by its terms clause and does not permit disclosing private content or inventing a partnership or endorsement.

The policy may change with purposes, services or requirements. Continued use alone is not blanket consent to new purposes; applicable notice, consent and objection requirements remain.

Privacy policy | SocialHamster