1. Who this policy covers
The operator of Suparko handles account information, website enquiries and information needed to run the service. When an organisation creates a workspace, that organisation also decides what work information is uploaded, who can access it and how it is used for its own purposes.
If you are a member of an organisation’s workspace, its own policies may apply to the work you put there. Contact its workspace administrator about that organisation’s use of your information. You can also contact Suparko directly about the service or your account.
This policy covers suparko.com and the Suparko application at app.suparko.com. Other websites and services you connect have their own privacy policies.
2. Information we handle
We receive information from you, from the people who invite you to a workspace and from your use of the service. The information depends on the features you use.
| Information | What it includes | Why it is needed |
|---|---|---|
| Account and profile | Name, email, password verification data, profile picture or chosen avatar, timezone, optional profile details such as job title and biography, the status you choose, and when you were last active in a workspace. | Create and secure your account, show your identity and presence to colleagues and display work in your timezone. |
| Workspace content | Workspace, project and team details; issues, descriptions, comments, status and assignment; chat messages; uploaded files and their metadata; project documents and their revisions; client portal publications, approvals and comments; check-in answers; workspace AI conversations; notification and activity records. | Store, organise and share your work with authorised people. |
| Access and security | Memberships, roles, access grants, session and invitation records, integration authorisations and audit records of relevant actions. | Check permissions, protect accounts, record changes and investigate problems. |
| Contact enquiries | Full name, email, optional company, selected topic, message and follow-up notes. | Respond to your question, product enquiry, support request or privacy request. |
| Technical and preference data | Information needed to deliver a web request, operational error logs, sign-in cookies and browser preferences such as selected workspace views. | Deliver the website, keep your session working, remember preferences and troubleshoot failures. |
3. Why we use information
We use information to provide the account and workspace features you request, respond to enquiries, enforce access permissions, maintain the service and protect it from misuse. Optional profile information is supplied by you. You can leave optional fields empty.
A name, email and password are needed for an account. Workspace permissions are needed to give you access to a particular workspace or project. Without these, the relevant feature cannot work. Contact requests need enough information to reply; do not include passwords or API keys in your message.
Where data protection law requires a lawful basis, providing a requested service or responding before an agreement may rely on contract; account security and service maintenance may rely on legitimate interests; an applicable legal obligation may require records to be retained; and an optional activity that requires consent will rely on that consent. The basis depends on the information, purpose and applicable law. An organisation using Suparko is responsible for the lawful basis of its own workspace content.
4. Who can see information
People in your workspace can see content according to the workspace, project, team, chat and file permissions that apply to them. Profile details and presence (for example “Active now” or a last-seen time) help colleagues identify and reach you. Workspace administrators can manage membership and access; project and team access are checked separately. A private conversation is available to its participants through the normal application, rather than to every workspace member.
People invited to a workspace's client portal see only the published file versions shared with them, and the approvals and comments they add are visible to the project team. They do not see internal chats, tickets or other workspace records.
The Suparko operator may need technical access to stored information for service support, security, maintenance or a request you authorise. Hosting and infrastructure providers process information as needed to run the service. Private conversations and files are access controlled; they are not described as end-to-end encrypted.
We do not sell personal information. We may disclose information when you direct us to do so, when necessary to comply with a binding legal requirement or when reasonably necessary to protect people or the service. A request from a third party does not itself give that party workspace access.
If you contact us by email, the email provider also processes that message to deliver and store it. Send only the information needed for your request. We may reply using email, whether your request arrived by email or through the website.
5. MCP, AI and other connected services
A connection can let another service request information or perform an action within the access you approve. Suparko’s remote MCP connection is limited to ticket operations. Its permissions remain tied to the authorised workspace, member and current project or team access. Read access and write access are different permissions.
When you use a connected AI service, ticket information returned to it becomes available to that service. Its own privacy policy and settings govern how it handles that information. Review those terms before connecting it, and avoid sending information you are not authorised to share.
Suparko AI is off until a workspace administrator turns it on. When it is on, a member's question and excerpts from records that member can access are sent to Google's Gemini API to produce a cited answer; an administrator decides whether accessible chat messages may be included. AI conversations are saved privately for the member who asked, and they are not shared with other members.
Connections can be revoked in workspace integration settings by an authorised person. Revocation stops future authorised requests; it cannot recall information that a connected service has already received. Public search engines and AI crawlers are permitted to read our public product and learning pages. This does not grant them access to private workspace records.
6. Storage and security
Workspace records are stored on the infrastructure used to operate Suparko. Uploaded file contents are stored separately from their workspace metadata. The service uses HTTPS, password hashing, protected sign-in sessions and server-side permission checks. These measures reduce risk, but no service can promise absolute security.
Hosting or a service you choose to connect may process information in a country different from yours. Contact us before uploading information if you need a specific hosting location, transfer arrangement or data processing agreement. A location or contractual safeguard should be confirmed for your arrangement rather than assumed from the website.
Keep your account credentials and integration keys private. Contact us promptly if you believe your account or workspace information has been accessed without permission.
7. Retention and deletion
Workspace content is retained to provide the service while it remains in the workspace. The current service does not apply a single automatic deletion period to every type of record. Retention decisions take account of an active account or workspace, the purpose of the information, security and audit needs, unresolved requests and any applicable legal requirement.
Archiving an issue or project is not deletion. Moving a file to Trash keeps it recoverable until an authorised person permanently deletes it. File storage removal is processed separately, and copies still used by another record or file version are not removed while they are needed.
Removing a person from one workspace does not delete their global account, their other workspace memberships or the work and activity they previously contributed. Some deleted messages and records are hidden from normal views while underlying records or security history remain stored.
Manual backups may contain earlier copies of information. Deleting a live record does not instantly remove every backup copy. Contact us about account closure or deletion so we can review the relevant workspace records, recovery copies and any retention requirement. Contact enquiries are kept for follow-up until they are no longer needed or a deletion request is resolved.
9. Your choices and rights
You can update available profile fields in your account settings. Contact your workspace administrator about membership or work access. For other privacy requests, email suparkoworkspace@gmail.com or use our contact form and choose “Privacy & data request”. Describe the request and the email associated with your account; do not send your password.
Depending on the law that applies to you, you may have rights to access, correct, delete, restrict or receive a copy of your personal information, withdraw consent or object to a particular use. You may also complain to your relevant data protection authority. These rights are subject to the applicable rules and to other people’s rights.
You can object to the use of your personal information for direct marketing, or to processing based on legitimate interests where applicable, by contacting us. Withdrawing consent does not affect processing that lawfully took place before withdrawal.
We may ask for limited information to verify your identity or your authority over a workspace before disclosing or changing records. We will assess the request, explain any applicable limitation and respond in the timeframe required by the law that applies. A workspace organisation may need to handle requests about content it controls.
10. Updates and contact
The date at the top of this page identifies this version. We will update the policy when the service or its information practices change. Review this page when choosing to use a new feature or connection.
Contact the individual operator of Suparko in the United States at suparkoworkspace@gmail.com, or use the contact form for privacy questions or concerns. Select “Privacy & data request” so your message can be identified. A company name is optional. Keep your request focused on the information needed to resolve it.
Need to talk about your data?
Email suparkoworkspace@gmail.com or send a message through our contact form. Keep passwords and private keys out of your request.