Skip to content

Legal

Privacy Policy

Version of 17 November 2026. 16 sections.

Working draft: some service provider details below (contact email and phone) are still to be completed.

Service provider
Sebastian Małucha
Brand
ViralMedia
Address
ul. Orzechowa 45 lok. 12, 50-540 Wrocław
Tax ID (NIP)
8992491352
Business ID (REGON)
021319283
Email
hello@hiretorin.com
Vulnerability reports
security@hiretorin.com
Torin calmly reads a long scroll with a coral pen in his hand

Polish version: Prywatność. This English version has the same content.

§ 1Who is the controller

The controller of your account data is the service provider named in the block at the top of this page; for personal data matters write to the address in the Email field. For your clients' data you are the controller, and we process it on your behalf under the terms on the page Data Processing.

§ 2What data we collect

  • Account data: email address, name, agency name.
  • Your clients' data that you enter yourself or that we read from connected accounts.
  • Conversations with the agent and a log of actions in the agency.
  • The IP address and a description of the browser at sign-in and when documents are accepted, invoice details and recordings you send yourself.

§ 3Purpose and legal basis

Only to provide the service: show the state of accounts, prepare content, issue invoices. Account and conversation data is needed to perform the contract (Art. 6(1)(b) GDPR); billing data is kept because tax and accounting law requires it (Art. 6(1)(c) GDPR). We do not sell data and do not use it to train models.

§ 4Who we share it with

Only with entities that perform part of the service, and only when needed: the list, with when data reaches each of them, is on the page Subprocessors.

Some recipients on the Subprocessors list operate outside the European Economic Area, mainly in the USA. We transfer data to them under a European Commission adequacy decision or standard contractual clauses; the basis for each recipient is on that list and we send a copy of the safeguards on request.

§ 5How long we keep it

For as long as you use the service and for the period required by accounting law. On request we delete earlier everything except what we must keep for billing: data in the database, files and access to connected accounts, which we revoke with the provider.

Backups are encrypted and rotated: the oldest one is at most eight weeks old. We do not cut deleted data out of existing backups, because an encrypted backup cannot be changed without damaging it. Until it rotates out, a backup is used only to restore the service after a failure and for no other purpose. If we restore the service from a backup during that time, we carry out the deletion again before the data returns to use. Eight weeks after deletion at the latest, the data is gone from backups as well.

§ 6Contact form

When you write to us through the form on the website, we record: your name, email address, company name (if you give it), the subject and text of the message. We process them only to reply, in our legitimate interest, which is answering your question (Art. 6(1)(f) GDPR); you may object (Art. 21 GDPR) by writing to the address in the Email field. To protect the form from spam we also record a hash of the IP address the message came from, on the same basis. We keep the message for at most 365 days from sending, then delete it. We never add your address to a mailing list. The message is seen by the service provider and by the providers that run our server and email (Subprocessors page). The right to data portability does not apply, because we do not process this data on the basis of consent or a contract. Giving the data is voluntary, but without an email address we cannot reply.

§ 7Evidence of acceptance and consents

When you accept the terms of service, the data processing terms and the declaration that you act as a business, and when you confirm the price of a paid action, we record: the person's email address, the document and its version, the SHA-256 hash of its text, the time, the IP address and a description of the browser. We do this in our legitimate interest (Art. 6(1)(f) GDPR): to show who agreed to what and when, and to defend against claims. The record is kept for the term of the agreement and then until claims become time-barred, also after the account is closed.

§ 8AI acknowledgement

Before someone asks Torin for the first time, they confirm that they know Torin is an artificial intelligence system and can make mistakes. We then record: the person's email address, the version of the text, the language in which they saw it, the SHA-256 hash of that text, the time, the IP address and a description of the browser. Purpose: to show that we informed about working with AI, and to defend against claims. Legal basis: our legitimate interest (Art. 6(1)(f) GDPR); you may object (Art. 21 GDPR) by writing to the address in the Email field. We keep the record for the term of the agreement and 3 years from the end of the year in which it ended; after that we delete the IP address and the browser description, and the record of the confirmed version stays without them.

§ 9Data from Google accounts

When you sign in with Google or connect a Google account on the Integrations screen, TORIN requests only the scopes listed below, each one separately, for the integration you connect. Consent to one integration gives no access to the others.

  • Sign in with Google openid (non-sensitive): your Google account identifier. Used only to sign you in to an agency workspace you have been invited to.
  • Sign in with Google email (non-sensitive): your account email address and whether Google has verified it. The address must match your invitation; an unverified address is refused.
  • Sign in with Google profile (non-sensitive): the name on your account, so your team can see who did what.
  • Google Ads https://www.googleapis.com/auth/adwords (sensitive): structure, settings and performance of the ad accounts you have access to (campaigns, budgets, keywords, conversions, recommendations). TORIN uses it for a daily account health check and to answer your questions. A change to an account (for example a budget or a keyword) is made only after you approve that one specific change, or within the limits of a standing approval accepted by the client in the client portal (selected kinds of changes and campaigns, a percentage and an amount limit, an end date, a notification after each use). In both cases the previous state is saved so the change can be undone.
  • Google Analytics 4 https://www.googleapis.com/auth/analytics.readonly (sensitive): read-only access to reports: traffic, traffic sources, conversions and visits from AI assistants to your client's website. TORIN changes nothing in Analytics.
  • Google Search Console https://www.googleapis.com/auth/webmasters.readonly (sensitive): read-only: list of properties, clicks, impressions, CTR, queries and pages from Google Search. Used for traffic and ranking reports.
  • Google Business Profile https://www.googleapis.com/auth/business.manage (sensitive): information, reviews and performance statistics of the business profiles you manage. A reply to a review or a change to a profile is published only after you separately approve that one reply or change. TORIN never changes the business name.
  • Google Calendar https://www.googleapis.com/auth/calendar.events.readonly (sensitive): read-only access to upcoming events, so TORIN can remind you of client meetings and prepare for them. TORIN does not create events or send invitations.
  • Google Sheets https://www.googleapis.com/auth/spreadsheets.readonly (sensitive): read-only access to values in a spreadsheet you point TORIN to. TORIN writes nothing to your spreadsheets.
  • Google Merchant Center https://www.googleapis.com/auth/content (sensitive): read-only access to your store's products, their status and the issues that stop Google from showing them. Google has one scope for reading and writing Merchant Center data; TORIN writes nothing to Merchant Center, and improved titles and descriptions are given to you as a file you upload yourself.
  • Google Drive https://www.googleapis.com/auth/drive.file (non-sensitive): only files TORIN itself creates, never your whole Drive. When you choose “Export” and “Google Doc”, TORIN saves the report as a new document in your Drive and gives you the link. It cannot see or read any other files, and it never shares or sends the document to anyone.
  • Gmail (read) https://www.googleapis.com/auth/gmail.readonly (restricted): reading messages in the mailbox. In the current version the connection can be made, but TORIN does not fetch any messages through it.
  • Gmail (drafts) https://www.googleapis.com/auth/gmail.compose (restricted): creating reply drafts that you send yourself. TORIN never sends email on your behalf. In the current version it does not create drafts through this connection either.

§ 10How we use data from Google

  • Only to provide the features you see in TORIN: account health checks, reports, the agent's answers and changes prepared for your approval.
  • We do not sell it and we do not transfer it to data brokers or advertising networks.
  • We do not use it for advertising, including personalized or retargeted advertising.
  • We do not use it to develop, improve or train generalized artificial intelligence or machine learning models, and we do not transfer it to anyone for that purpose.
  • We do not use it to determine creditworthiness or for lending purposes.
  • We transfer it only when necessary to provide a feature you request: data you ask the agent about is sent to a language model provider so that the answer can be generated (see the list on the Subprocessors page). Otherwise only on your instruction, for the security of the service, or when required by law.
  • No human at TORIN reads this data unless you give explicit consent for specific data (for example when reporting a bug), it is necessary for security purposes (for example investigating abuse), it is required by law, or the data is aggregated and anonymized for internal operations.

TORIN's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. See the Google API Services User Data Policy.

§ 11Storage and deletion of Google data

  • Access tokens for Google accounts are stored encrypted (AES-256-GCM), separately for each agency. The language model never sees a token: it is inserted only at the moment of the API call.
  • Results of reads (account checks, reports, conversations with the agent, change history) are kept in your agency's data for as long as you use the service.
  • When you disconnect an integration, its token is deleted immediately and TORIN stops reading that account.
  • When an agency account is closed or deletion of a client's data is requested, there is a 30-day period to cancel; after that we delete the data and revoke the tokens with Google. We keep only what the law and accountability require: invoices, payments and the activity log.
  • Backups are encrypted and rotated: the oldest one is at most eight weeks old. We do not cut deleted data out of existing backups, because an encrypted backup cannot be changed without damaging it. Until it rotates out, a backup is used only to restore the service after a failure and for no other purpose. If we restore the service from a backup during that time, we carry out the deletion again before the data returns to use. Eight weeks after deletion at the latest, the data is gone from backups as well.

§ 12How to revoke access to your Google account

  • In TORIN: open Integrations (Integracje), choose the connection and click Disconnect (Odłącz). The token is deleted immediately.
  • In Google: go to https://myaccount.google.com/permissions, select TORIN and remove access. This revokes the consent on Google's side, even if you no longer have access to TORIN.
  • Closing the agency account revokes the tokens with Google automatically.

§ 13Data from Microsoft Advertising accounts

When you connect a Microsoft Advertising account on the Integrations screen, TORIN requests the scopes https://ads.microsoft.com/msads.manage and offline_access (the latter refreshes access without signing in again). Microsoft has one scope for reading and writing ad accounts; TORIN only reads accounts, campaigns and performance reports to prepare health checks and reports, and changes nothing in Microsoft Advertising. The token is stored encrypted in the same way as Google tokens and the language model never sees it. When you disconnect the integration we delete the token immediately; you can revoke the consent on Microsoft's side at account.live.com/consent/Manage. We do not sell this data and do not use it for advertising or to train models; only what you ask the agent about is sent to the language model provider.

§ 14Data from other connected accounts

When you connect an account with another provider (for example Meta, TikTok, LinkedIn, Allegro, Shopify), TORIN requests the permissions shown on that provider's consent screen and uses them on the same terms as Google data: only for the features you see in TORIN, with no selling, no advertising and no model training, with the token encrypted and deleted on disconnection.

§ 15Cookies and browser storage

The hiretorin.com website stores no cookies and nothing in browser storage. After you sign in, the app stores a session cookie valid for 30 days and not accessible to page scripts, and after an action a message cookie for 60 seconds. Browser storage keeps only whether the app's sidebar is collapsed. The client portal has its own session cookie of the same kind. The sign-in screen and the code screen store, when first shown and before you sign in, a device cookie (torin_urz) valid for 365 days that opens nothing and only recognises your browser: a sign-in from a new device is reported to you by email straight away. This cookie is necessary for secure sign-in, so we do not ask for consent to it (Art. 399(3)(2) of the Polish Electronic Communications Law). For each session we keep the browser type and IP address, shown in Settings, Active sessions, to protect the account from takeover (Article 6(1)(f) GDPR). We use no advertising or analytics cookies.

§ 16Your rights

You have the right to access, rectify, erase and port your data, and to object to and restrict processing. Just write to the address in the Email field. You also have the right to lodge a complaint with the Polish supervisory authority (Prezes Urzędu Ochrony Danych Osobowych). We do not make decisions about you based solely on automated processing that would produce legal effects.

Working draft, before final legal review. It describes what the system actually does and does not replace a contract.