Skip to content

Part of the Lit Shark family

Legal

Privacy policy

DRAFT for legal review, not the final policy. This page lists what SharkCollab processes so that counsel can write the policy. It is not legal advice and is not yet the operator's statement under the GDPR. Items in [square brackets] are for the owner or counsel to fill.

Who is responsible

SharkCollab is part of Lit Shark (litshark.com). Controller: [legal entity name, address, company number / OIB]. Contact for privacy questions: [privacy e-mail address]. Supervisory authority: [the Croatian data protection authority (AZOP), to be confirmed by counsel].

What we process, and why

Your account

  • Name, e-mail address, password (stored only as a hash), country and time zone; e-mail verification and password-reset records.
  • If Google sign-in is switched on: your Google account id and e-mail address. Your Google profile picture is never stored.
  • Which version of the Terms of Service and platform NDA you accepted, when, and the IP address and browser (user agent) used at that moment, as proof of acceptance.
  • The IP address you signed up from and the IP address of your latest sign-in. They are used only to detect referral abuse (an invite used by the inviter's own second account) and are visible to staff only.
  • Notification preferences, digest settings, and the in-app notifications we send you (deleted after 365 days).

Profiles and public pages

  • Editor, designer and client profiles: handle, bio, languages, genres, rates, specialties, credits (titles you worked on), availability. These are public under your handle.
  • The name you give for contracts ("display name") and a client's company are never public; they are shown only to the other party once a contract exists.
  • Gallery samples (images and descriptions). Images are re-encoded on upload, which removes camera metadata such as location.
  • Reviews, ratings and reputation figures. Reviews are public reputation data and are kept when projects are deleted.

Projects and contracts

  • Listings, offers, contracts, milestones, time entries, deadline extensions, contract changes and the contract timeline.
  • Messages and files exchanged in project chats. An automatic filter masks contact details and flags repeated attempts to staff.
  • Manuscripts and their version history in the built-in document editor (OnlyOffice Document Server, run on our own server; manuscripts are not sent to a third-party editing service). Each editing session is recorded with the person, the times and the IP address.
  • Delivered design files, dispute statements and evidence, reports, violations and appeals, and the record of every time staff opened a chat, file or manuscript.
  • Pro applications, including uploaded credential documents (diplomas, CVs, certificates). These documents are seen by staff only and deleted as soon as the application is decided; only the decision is kept.

Payments

  • Payments are processed by Stripe. Card details are entered on Stripe's own checkout page and never reach SharkCollab.
  • Editors and designers set up payouts with Stripe Connect; Stripe collects identity and bank details directly. We keep the Stripe account id, its country and its status (whether payouts are enabled).
  • We keep records of every charge, refund, payout, fee and credit, as accounting law requires.
  • Referral and credit records: who invited whom (never shown to the inviter), credit balances and their history.

Usage analytics

  • We record a small number of first-party events (for example "signed up", "listing published", "contract created", "dispute opened") with your user id and no IP address, browser or cookie identifier. They are used only for aggregate figures on our own dashboard and are deleted after 730 days.
  • No third-party analytics or advertising trackers are used.

Cookies

SharkCollab sets only cookies that are needed for the service you ask for, so no consent banner is shown [counsel to confirm]:

  • sharkcollab-session: keeps you signed in during a visit (120 minutes of inactivity).
  • XSRF-TOKEN: protects forms against cross-site request forgery.
  • remember_web_…: only if you choose "remember me" (or sign in with Google), to keep you signed in.
  • sc_ref: only after you open someone's invite link, to remember the invite code until you sign up (30 days). It holds the inviter's code, nothing about you.

Who else processes data

  • Server hosting: a virtual server rented from Contabo [data-centre location]. The database, search index (Meilisearch), document editor and backups on the server run there.
  • File storage: Cloudflare R2, in a bucket restricted to the EU jurisdiction [once enabled; until then files are stored on the server].
  • Payments: Stripe [entity; international transfers covered by …].
  • E-mail: [e-mail provider; currently an SMTP mailbox at our web host].
  • Realtime updates (when enabled): Pusher. Only ids are sent through it, never message text, file names, names or documents.
  • Error monitoring (when enabled): Sentry [EU region]. Configured not to send personal data by default; error reports can contain page addresses and internal ids.
  • Uptime monitoring: UptimeRobot checks a status address that carries no personal data.
  • Google, only if you choose to sign in with Google.

How long we keep it

  • Project messages and chat files: 12 months after the contract closes, then permanently deleted. Unused conversations are archived and deleted on the same clock.
  • Manuscript version history: 12 months after the contract closes. The final exported manuscript: 24 months, with a reminder to download it before it is deleted.
  • Dispute evidence is deleted with the chat; the decision is kept with the financial records.
  • Financial records (payments, refunds, payouts, fees, credit): [the period required by Croatian accounting law, to be confirmed by the accountant].
  • Reviews: kept as public reputation data.
  • Backups: database backups are kept for 35 days. Deleted data can survive in a backup until it rotates out; if a backup is ever restored, all deletions that were due are applied again before the service reopens.
  • A contract can be placed on legal hold (for example during a legal claim), which pauses deletion for that contract until the hold ends.
  • Deletion is real deletion: rows and files are destroyed, not hidden.

A request to delete your data does not remove a project chat inside its retention window: it is kept because of our legal obligations (disputes and chargebacks), then deleted on schedule. [Counsel: the account-deletion process, currently handled by staff on request.]

Your rights

[Counsel: access, rectification, erasure, restriction, portability, objection, withdrawal of consent, complaint to the supervisory authority; how to exercise them; legal bases for each purpose above (contract, legal obligation, legitimate interest).]