Legal
Privacy policy
Last updated
Bizisy is operated by Wisely Lda (NIPC 516845128), Rua de S. Pedro 12A, 4720-092 Amares, Portugal. In this policy, “we” and “us” mean Wisely Lda.
Bizisy is an HR platform: a company keeps its people records and organization structure in Bizisy, and its staff sign in to see their own details and their colleagues. This policy explains what personal data Bizisy handles, why, who helps us run it, how long we keep it, and the rights you have. For anything about it, write to privacy@bizisy.com.
1. Who is responsible for your data
Two different roles apply, depending on the data:
- We are the controller of the data we need to run Bizisy itself: sign-in accounts, sessions and API keys, developer accounts and their access tokens, developer organizations and developer sandboxes, partner accounts and their firms (accountants, HR consultants, implementation and referral partners), the revenue share terms and records, email delivery records, billing records, security and technical logs, this website, and messages you send us.
- Each customer organization is the controller of the HR data it puts into Bizisy: its people records, organization structure and invites, and, if it uses Hiring, its job posts and the people who apply or are referred to it. For that data we are a processor: we handle it only to provide Bizisy to that organization, on its instructions.
If you are an employee of a company that uses Bizisy and have a question about your HR records, contact your employer first: they decide what is recorded about you. You can also write to us and we will pass your request on and help them answer it.
2. What we handle
Account and sign-in data
- Your name and work email address, the organization you belong to and your role in it (owner, admin, HR, member, viewer, or a custom role the organization created).
- When a company signs up: the company name, its Bizisy address (for example acme.bizisy.com) and its country. Bizisy’s own team is told of each new company in its internal Slack workspace with these three facts only, never the name or email of the person who signed up.
- How you sign in: with a password, Google or Microsoft, and an identifier of that sign-in.
- The language you choose for Bizisy (English, Portuguese, Spanish, German, French or Italian), if you choose one. It applies in every organization you belong to and to the emails you get, and is included when you download your data. An organization’s owners and admins can also set a default language for the organization.
- How you set up Bizisy for yourself in each organization: which Home each app opens on and the pages and actions you pin to the top of the menu. They are in your data download, and deleted with your data or the organization.
- Passwords are held by Google Identity Platform, never by Bizisy. When you set a password, our server passes it to Identity Platform and keeps no copy.
- Two-step sign-in: when you add an authenticator app, its secret is made and kept by Google Identity Platform, never by Bizisy; Bizisy shows it to you once as a QR code and keeps the name you give the app, when you added it, how many apps your login has, and whether each session was opened with a second step. Adding or removing an app, and an owner or admin resetting yours, are recorded in Activity and emailed to you. Whether the organization requires two-step sign-in, and of whom, is part of its settings.
- Sessions: when you sign in we create a random session token. Your browser keeps it in a cookie; we store only a hash of it, with when it was created and when it expires (after 7 days, or when you sign out, which deletes it).
HR data entered by customers
What a customer records about its people, for example: name, pronouns, work email and phone, job title, team, manager, location, legal entity, start date, employment type and job history; and its organization structure (teams, locations, legal entities). Job titles come from the organization’s list of job titles, which can group them into job families and levels; a person can show a different title on their profile, set by HR or asked for by the person and decided by HR, and it follows the same rules as the job title.
Bizisy also has a private tier of personal details: personal email and phone, home address, birthday, sex for equal-pay reporting (optional) and emergency contacts. In the app, private details are shown only to the person themself and to the organization’s owners, admins and HR. API keys and AI assistants connected over MCP never receive anyone’s private details except the caller’s own.
Profile photos and company logos
A person can add a photo of themself to their profile, and the organization’s owners, admins and HR can add or change anyone’s photo. Owners and admins can add a company logo. Before storing an image, Bizisy checks it, crops it to a square of 512 × 512 pixels and saves a new copy without any of the original file’s metadata (such as camera details or the location where the photo was taken). A photo is visible to everyone in the same organization who can see the person, including API keys and AI assistants connected to that organization; never to anyone outside it. A company logo is also shown on the organization’s sign-in page, which anyone who opens its Bizisy address can see. An organization that uses Hiring can also add a cover photo to its careers page (owners, admins and HR): Bizisy checks it the same way (a JPEG, PNG or WebP of at most 5 MB, by its content), keeps a new copy without any of the original file’s metadata and the crops the careers page shows; anyone who opens the careers page sees it, so the organization should only use a photo everyone in it agreed to show. Photos, logos and cover photos are stored in Google Cloud Storage in the EU and are served only through Bizisy.
Documents
An organization can keep documents in Bizisy: documents about a person (such as their employment contract, addenda, certificates and copies of identity documents) and documents for the company (such as its handbook and policies). Person documents can contain sensitive information, including special categories of data such as health information in a medical certificate; the organization decides what it stores, as the controller of that data. For each document we keep the file, its title, category, original file name, size, type, the dates it was added and changed, an optional expiry date and notes, who it is about, and who can see it. The organization’s owners, admins and HR choose who sees each one when they add it: only HR; HR and the person; or HR, the person and their managers (a company document: everyone, managers and HR, or HR only). When HR adds a document the person can see, the person is told it is there (in Bizisy, and by email if the organization sends those emails), unless HR chooses to add it without telling them; the notice names only the category, never the title or file name. A person can also add documents of their own for their HR team (“From me”); only they and their HR team see those. Owners, admins and HR (and roles the organization allows to manage that person’s documents) can ask a person to add a document of a category, optionally by a date and with a short note; we keep the category, the note, the date, who asked and when, and whether it was added or cancelled. The person sees the request in My documents and gets a notice in Bizisy (never an email); it closes when they add a document of that category in My documents or HR uploads one for them. Requests are erased with the person, included in their data download and in the company export, and deleted when the organization closes. An organization can also add custom fields that hold a file (such as a copy of a driving licence or a CV); each such file is kept as one of the person’s documents, is seen by the same people who see that field (only the person and HR, also their managers, or everyone in the organization), and, where the organization allows it, the person can upload, replace or remove their own. Replacing or removing it deletes the previous file. Through API keys and AI assistants, other people’s documents are visible only as their title, category, date and size, never their contents. Files are checked when they are uploaded (the size, a fingerprint of the bytes and the file type, the whole file for text; programs, archives, Office files with macros or embedded programs, and text files that begin as a web page or a script are refused, and every file is saved with the extension of its checked type, so a text file is always saved as text) and stored in Google Cloud Storage in the EU (Belgium). Files are uploaded and downloaded directly between your browser and that storage through links that work for a few minutes. PDFs and images can be previewed inside Bizisy in an isolated viewer; downloads are always saved as files. Downloading a person’s document is recorded in the organization’s activity (which document category, not the file name). Storage is counted per organization (documents, profile photos and the logo) to apply its limit and to bill any storage above the included amount.
Contract terms
For each job: contract type (permanent, fixed term, temporary, internship or freelance), when a fixed-term contract ends, when probation ends, weekly hours and notice period. They belong to the job details, which the person, their managers and the organization’s owners, admins and HR can see.
Payroll details
A person’s tax ID, social security number and IBAN (the bank account their pay goes to). They are private details: only the person and the organization’s owners, admins and HR see them, and API keys and AI assistants never receive them except the caller’s own. They can only be set or changed by someone signed in to Bizisy (one person at a time, or by importing a CSV file), never through an API key or AI assistant, and every change is emailed to the person and to the organization’s owners, admins and HR. When an import changes several people’s details at once, each person gets their own email and owners, admins and HR get one email listing the people. These emails say who changed the details and when, never the new values. The organization’s daily email limit never stops them. To prevent abuse, a person’s payroll details can change at most three times a day, and each organization’s emails of this kind are limited per address and in total each day; when an organization would pass a limit, its change is refused rather than made without the email. Separately, an address that gets an unusual number of these emails from different organizations in one day receives no more that day, and we are alerted. Activity records never keep these values; the change history (below) keeps the old and new values, which only the person and the organization’s owners, admins and HR see, in the app.
If an organization uses Verified bank details, a new or changed IBAN applies only with a proof: a bank statement or the bank’s IBAN certificate that the person, or HR for them, uploads. Bizisy sends that file to Google Cloud Document AI, in the EU, which returns its text and keeps nothing; Bizisy then checks whether the IBAN is on it and whether the account holder’s name matches the person’s legal name, and keeps the result (verified, needs review or rejected) and why, never the document’s text. Depending on the organization’s choice, a verified change applies at once or HR reviews it. The proof, the IBAN asked for and the result are private details: only the person and the organization’s owners, admins and HR (or a role with private details) see them, never API keys or AI apps. They are kept with the person’s record, included in their data export and deleted when the person is erased or the organization closes.
Pay
A person’s pay history: amount, currency, period (per year, month or hour), the date each amount applies from, and an optional note. Pay has its own, stricter visibility: only the person and the organization’s owners, admins and HR see it in the app. Managers never see it. An API key or AI assistant receives only the caller’s own pay. Pay can only be recorded or corrected in the app by owners, admins and HR, never for their own pay. Activity records of pay changes keep only which fields were sent; the change history (below) keeps the amounts, seen only by the person and the organization’s owners, admins and HR, in the app.
Payroll preparation
An organization can prepare its payroll in Bizisy for its payroll provider or accountant; Bizisy never calculates pay or files anything with tax or social security authorities. For each pay period of a legal entity Bizisy lists who joined, who left and what changed (job, contract, pay, and names, addresses and payroll details changed since the last period), with variable pay HR adds (bonuses, overtime, allowances, deductions), notes and files for the accountant, and comments between HR and the accountant. When HR locks a period we keep a copy of that list and of each person’s details as they were, so that later corrections can be shown in the next period; we also keep each person’s employee number and whether they asked for paper payslips. Exports (Excel, CSV, JSON, DATEV LODAS, BrightPay, Lexware lohn+gehalt, Sage 50 Payroll, Silae) are made when downloaded and are not stored: we keep each file’s fingerprint (SHA-256), its format, who made it and when. Where an organization sends its payroll to Meta4, it keeps in Bizisy the codes Meta4 knows its leave types, pay items and other rows by (company settings, no personal data), and each Meta4 export also keeps those codes and, for each line, a key and a short fingerprint, never the values, so a later export can say what changed. When HR compares Meta4’s results with what Bizisy sent, Bizisy keeps the comparison with the period (per person and code: what was sent and what was paid), seen only by those who prepare payroll for everyone in the period; a person’s rows are deleted when their data is erased, and all of it when the organization closes. The net pay the provider calculated can be imported to make a SEPA salary file for the organization’s bank; Bizisy keeps the net amounts but not the file, and never moves money. All of this is pay and private data: only the organization’s owners, admins and HR see it, and outside access the organization gives (for example its accountant, with the Accountant role, who then acts as the organization’s processor) sees it only for the people their role covers, until the end date the organization set. API keys, AI apps and connected payroll software receive pay amounts and private details only when an owner, admin or HR member allowed that connection in Payroll settings; that consent is recorded in Activity and can be revoked at any time.
Payslips uploaded by HR or the accountant are split and read in their browser to match each one to a person; only the single payslip of each person is sent to Bizisy, where it becomes that person’s document (category Payslip) and they are told. Payslips that could not be matched stay visible to HR only until they are assigned or discarded. A person may ask for paper payslips (in France employees may refuse electronic payslips at any time); their payslips are then kept as HR’s copy only. Payslips are kept like other documents: until the organization deletes them, the person’s data is erased, or the organization is closed. In France an employer must keep electronic payslips available for 50 years or until the employee turns 75: download them before closing your account.
Pay equity
An organization can use Bizisy to meet the EU Pay Transparency Directive. Its owners, admins and HR can record pay bands (a minimum and maximum pay for a job title or a job level), an evaluation of each job title (scores for skills, effort, responsibility and working conditions, with a rationale), categories of workers that group jobs of equal value, and a written pay policy. These describe jobs, not people. Pay bands follow the rules for pay: only owners, admins and HR see them, unless the organization chooses to show each person their own band.
Sex for equal-pay reporting (female, male, another, or prefers not to say) is optional and private: only the person and the organization’s owners, admins and HR see it, and it is never shown to managers or colleagues. It is entered by the person on their profile, or by HR, and is used only to count women and men in pay gap figures and pay averages. Owners, admins and HR can also check whether review ratings, potential and calibration changes, and the raises that follow them, differ between women and men. Bizisy shows only totals, hides any group with fewer than 5 women or 5 men, never shows these figures to managers or through API keys and AI apps, keeps nothing from the check and records each check in Activity.
From the gap figures, owners, admins and HR can prepare a yearly pay gap report. For it Bizisy adds up each person’s variable pay for the year from the pay items in Payroll and the benefits in Benefits, where the organization uses them, and HR may import more from a spreadsheet (bonuses, allowances and benefits in kind); amounts read from Payroll and Benefits are not stored, and imported per-person amounts are deleted when the report is finalised, and only the report’s totals and percentages are kept.
A person can ask, in My workspace, for their own pay level and the average pay of women and men in their category; when they ask HR another way (for example in a letter), HR can record the request in Bizisy for them, with the day it was received and an optional note on how it came. We keep the request, when it was made and is due, the answer (the person’s own pay level and the averages, never anyone else’s individual pay) or why it could not be given at once, and HR’s written reply. Averages are given only when each group is large enough not to reveal a colleague’s pay. Only the person and the organization’s owners, admins and HR see a request; managers are never told. When HR replies, the person gets an in-app notice. Once a year, organizations that have set up pay equity remind their people of this right with an in-app notice and an email; like other reminders, Bizisy records that a person was reminded that year (identifiers and dates only).
Open positions
An organization can plan roles it is going to fill: the job title, team, location, legal entity, who the role reports to, contract type, weekly hours, a target start date, a status, why it exists (a new role or a replacement, optionally naming the person who is leaving), notes, and an optional budgeted pay range. A manager can ask HR for a role in their team from My workspace (a new role, or a replacement for someone in their reporting line): we keep who asked, when and their note for HR, and it stays a draft that only HR and that manager see until HR opens or cancels it; the person being replaced is not told. If that manager’s data is erased, their name and note are removed from the request. Owners, admins and HR see every position. A manager sees only the open roles that report to them or to someone below them, without the notes or the budget, and sees who is being replaced only when they can already see that person’s job details. Everyone else does not see open roles. The budget follows the rules for pay: only owners, admins and HR see or set it, and only in the app, never through an API key or AI assistant. When someone is hired into a position, the position records who filled it and their first job records the position. When HR downloads a person’s data, it lists the positions that person filled or is recorded as being replaced in; a person’s own download lists only the positions they can already see in Bizisy, so it never reveals a planned replacement. Activity records of position changes keep only which fields were sent. If the organization requires approval to open a position, we keep the request: who asked and when, why it needed approval (always, over the team’s headcount plan, or a pay range above the band), each approval step with who decided, when and their comment, and the numbers the approvers saw (the pay range, the band of its title and the team’s plan against people, open and requested positions). Approvers see those numbers in the app, even when they don’t otherwise see pay; never API keys or AI apps. Approvers are emailed when it is their turn, and whoever asked when it is decided (the title, the team and the comment).
Planning
HR can forecast headcount and cost per team from job, contract, hiring and pay data; forecasts are visible to HR roles only (owners, admins and HR). A forecast counts people joining and leaving, including recorded last days that the person may not have been told about yet, and fixed-term contracts ending; it shows them as numbers, and names the people behind a number only to owners, admins and HR signed in to Bizisy, never to API keys or AI assistants. Cost is calculated from pay and follows the rules for pay: in the app only, for owners, admins and HR. Scenarios hold assumptions and planned numbers per team (planned reductions are numbers, never named people) and no personal data; adopting one writes the headcount budget. Scenarios are included in the organization’s data download and deleted when the organization closes. No new processor is involved and nothing is kept beyond the organization’s own records.
Custom fields
Each organization can add fields of its own (up to 30 each) to people’s profiles (for example a T-shirt size), to their job (for example a shift pattern, kept with the job’s history), to teams (for example a cost centre) and to open positions. A field can hold text, numbers, dates, a choice, a list of rows (a table) or the name of a colleague. The organization decides for each field who can see it: everyone in the organization, the person with their managers and HR, or only the person and HR (job fields: the person, their managers and HR; private team and position fields: owners, admins and HR, never API keys or connected AI apps). Organizations must not use custom fields for special categories of data such as health, religion or trade union membership.
Exports and reports
Owners, admins and HR can export their people as a spreadsheet (CSV). Private details are included only when they explicitly ask for them in the app, and pay is never included in that spreadsheet. Owners and admins can also download all of the organization’s data as one zip file (Settings → Close account or Data & privacy): every person’s profile including private and payroll details, job and pay history, photos, the company logo and the careers page’s cover photo, documents with their files, the structure, open positions (with their budgets and notes), approval requests, checklists, saved groups, webhook endpoints (never their secrets), connected tools with their links and logs (never their credentials) and the headcount-cost journals prepared for accounting tools, data export and BI settings (never the BI token), logins, API keys (never the keys themselves), connected AI apps (never their tokens), billing details and invoices, the plan and its monthly records, the full activity record and the change history. Downloading it is recorded in Activity. Anyone can download a copy of everything Bizisy holds about them from their profile (their photo and the documents shared with them included), and HR can download a person’s data, including all of their documents, to answer a request. Once a file leaves Bizisy, keeping it safe is the responsibility of the organization or person who downloaded it. Anyone who can see the org chart can download it. Pictures and PDFs are made in their browser and show only what the chart shows them: names, job titles, teams, managers, locations, the open roles they are allowed to see and, if they choose, photos and the job dates they are allowed to see. Lists (CSV or Excel, or through the organization’s AI or API keys) show the same names, job titles, teams, managers and locations, plus start dates and report counts. Neither ever includes private or pay details. Reports (headcount, joiners, leavers, turnover) are totals calculated from the job history; they show no individual’s personal details. People analytics, for owners, admins and HR, aggregates job, leaving, absence and, where the organization records them, gender, age (from the birthday) and the organization’s own fields it marks for analytics; groups under 5 people (or more, if the organization chooses) are always hidden, gender, age and absence are never listed per person and never given to API keys or AI apps, and Bizisy never reports on health, ethnicity, religion, sexual orientation, disability or other special categories. When HR records a voluntary leaver, they may note whether the organization regretted losing them (yes, no or not set): it is kept on that person’s last job, shown only to owners, admins and HR in the app, never to the person’s colleagues, managers or through webhooks, used only in attrition figures as a count, included in the person’s own data download and removed when their data is erased. Owners, admins and HR can save people analytics views (a name and the table’s settings, never personal data); they are part of the company export and deleted when the company closes.
Custom roles and outside access
An organization’s owners and admins can create custom roles: for each area (people and jobs, private details, pay, documents, checklists, open positions, pay equity, structure and Activity) what the role may do, and whom it covers (legal entities, teams, locations, saved groups, the reporting line of whoever holds it, and named people; or everyone). Someone with a custom role sees and changes only what their role allows, only for the people it covers, and never their own records; the organization’s pay-equity, structure and Activity areas are company-wide. We keep each role’s name, description, areas, the people it covers, who created it and when, and which login holds which role. Owners and admins can also give access to people who do not work for the organization, such as a payroll bureau, an accountant or an auditor (outsiders): we keep a contact card for them (name, firm and work email), their login, their role and the day their access ends (at most three years ahead); on that day their sign-in, API keys and connected AI apps stop working, and owners and admins are reminded on their Home two weeks before. Outsiders see only the people their role covers and are never in the directory, the org chart, headcount or reports. A role’s API keys and connected AI apps reach the same people as the role; they receive private and pay details only when an owner or admin turned that on for the role, with a warning. Creating, changing and deleting roles, giving them, and changing an outsider’s end date are recorded in Activity. An outsider’s contact card is erased like anyone else’s, and roles are part of the company export and are deleted when the company closes.
Saved groups
Owners, admins and HR can save groups of people as conditions, such as “everyone in Lisbon still on probation” or “the managers in Engineering”: a name, an optional description and the conditions (teams, locations, legal entities, managers, job titles, employment and contract details, or the organization’s own fields). A group may name people only as managers (“reports to”). Bizisy does not keep who is in a group: it works it out from the current records each time the group is used, to filter the people list and the org chart, to decide whom a custom role covers, or who gets a checklist. Everyone sees a group’s members only through the details they are already allowed to see, so a group never shows who has a value they could not see themselves; groups that use a private field are shown only to people who see private details, and can’t decide whom a role covers or who gets a checklist. Saving, changing and deleting groups is recorded in Activity. Erasing a person removes them from the groups that name them; groups are part of the company export and are deleted when the company closes.
Processes saved for later
When someone at an organization prepares a hire or a change about a person (a promotion or raise, a job change, a move, someone leaving, a probation or contract decision, a rehire) and clicks Save for later, we keep what they typed (which can include a new hire’s contact and payroll details and pay), a short label, the people it is about, who saved it and when, so that they or a colleague who may make that change can finish it. Nothing is saved unless they click it. A saved draft is kept until someone finishes or deletes it; drafts about a person are deleted when that person is erased, and all of them when the company closes. Through API keys and AI assistants, saved drafts never include private details or pay. A person never sees drafts about them (a planned change is not shown before it happens), and their own data download leaves them out; HR’s download of a person’s data includes them. A manager can also save a proposal for someone in their team (a new title, a new manager or team, a resignation or a probation outcome) in My workspace: only that manager sees it until they send it to HR, and it is deleted when they send or delete it, when the person or the manager is erased, or with the company.
Importing people from a file
Owners, admins and HR can import people from a CSV file (up to 10,000 people), or an AI app or API key acting for them from CSV text (up to 250). Bizisy reads the file and keeps, for each import, its rows as they were in the file (and as corrected in Bizisy), which column feeds which field, what applying each row would change, the problems found, who started it and when. A file larger than 1 MB is uploaded to our storage and deleted as soon as it has been read. Big imports are read, checked and applied on our servers in the background, in the European Union like the rest of Bizisy, as the person who started them: they stop if that person can no longer import. A row is cleared once it is applied (the person’s record then holds the data); rows that could not be applied are kept so they can be fixed. Only owners, admins and HR see imports; through API keys and AI apps, payroll details, sex and private fields in an import are never shown, and an API key or AI app only changes imports it started. Each import, with its rows, is deleted 30 days after it was started (within a day of that), when someone discards it, or with the organization; rows about a person are deleted when their data is erased. A person’s own data download leaves imports out; HR’s download of a person’s data includes the rows about them. Importing records each change as usual, in Activity (counts only, never names or values) and in the change history.
Moving from another HR tool
Owners, admins and HR can move their organization’s data from the HR tool it used before (Personio, Factorial, Sesame HR, HiBob, BambooHR or a spreadsheet) by uploading that tool’s export files, or an owner or admin can connect it with an API key created in that tool. The files and what Bizisy reads hold the people and their contact and private details, their job and its history, teams, managers and locations, time off, documents and, only if the person moving chooses it, pay. Bizisy reads, checks and imports them on our servers in the European Union, in the background, as the person who started the move: it stops if that person can no longer do it. Uploaded files are deleted from our storage as soon as they have been read. An API key is stored encrypted, used only to read the old tool (Bizisy never writes to it) and removed when the move ends or at most 24 hours after it was connected, whichever comes first. For each move Bizisy keeps its rows (each person, leave, balance and document as read, with the checks and problems found), which column feeds which field, what it created (to undo it within 24 hours), who started it and when; a row is emptied once it is imported (the person’s record then holds the data). Only owners, admins and HR see moves; through API keys and AI apps, only pasted text of at most 250 people can be moved, without pay, payroll details, sex or private details; an API key or AI app changes only moves it started and never sees the private, payroll or pay values of a move. Each move is deleted 30 days after it was started, or with the organization; rows about a person are deleted when their data is erased. Nobody is emailed by a move (except the usual security notice when the payroll details of someone already in Bizisy change), and Activity records it with counts only, never names or values. The old tool is chosen by the organization and works for it under its own agreement (the organization’s processor, not ours); what it keeps stays under that agreement. A move from a payroll tool such as Meta4 PeopleNet can also bring a job-history file (each person’s job from each date) and each person’s employee number, which is kept in Payroll; people without a work email in the file get one made from their name and the organization’s email domain, or sign in with their personal email, as the person moving chooses. So that the next move from the same tool needs no matching, Bizisy remembers, per organization and tool, which column of the file feeds which field, what the codes in it mean (such as contract codes) and that choice of email; this holds column names and codes, never anyone’s data, and is deleted with the organization.
Moving to another HR tool
Owners and admins can download their organization’s data laid out for importing into another HR tool (Personio, Factorial, Sesame HR, HiBob, BambooHR or any spreadsheet), in the app only. The download holds the people they may see with their contact and private details, their job and its history, teams, managers, locations, legal entities, custom fields, time off and, only if they choose them, documents and pay (pay only for those who may see it). Bizisy builds it on our servers in the European Union, in the background, as the person who asked: it stops if that person can no longer do it. We email that person that it is ready, with a link to the app and never the file. The file can be downloaded through a link valid for 5 minutes, made on each click, for 7 days, and is then deleted from our storage (earlier if someone in it is erased, or with the organization). We keep a record of each such export (the tool, the options, counts, who asked and when, and the optional reason given for leaving) for 30 days; Activity keeps who asked and when, never the data or the reason.
Structure over time, reorg plans and dotted-line managers
Bizisy keeps the history of each team (its earlier names, where it sat and who led it, with the dates) and team changes an organization schedules for a later day (who scheduled them and when). An organization can also draft reorg plans: proposed new teams, team changes and moves of named people from a date, with who prepared each plan. Plans are seen only by the organization’s owners, admins and HR, never by the people in them, until a plan is applied. A person can have dotted-line managers: someone they also report to on a project or function, from a date, with an optional note; a dotted-line manager sees that person’s job details (never their pay or private details) and never approves changes for them.
Invites
When an organization invites someone, Bizisy stores the invitee’s email address, role, who sent the invite and when it expires (after 14 days). The invite link is emailed to the invitee and shown once to the sender; we store only a hash of its secret, never the link itself. Someone who signed in but whose login isn’t linked to their person record can ask HR to link it: we keep when they asked, until it is linked. An invite can also be scheduled with the hire, to go out on a later day at 08:00 company time: we then keep that day, who scheduled it (it is sent as them, only if they may still invite) and, if it could not be sent, why.
An organization can also invite people by their work email alone, before it has their other details. Bizisy then keeps a record for each invitee with their work email, who invited them and when, and whatever the organization adds about the job they will take (such as a job title, team, manager or start date). Invitees add their own name and details when they sign in, and can suggest their job title and start date for the organization’s HR to confirm; their planned manager can suggest them too. Until they are registered (once their name, job title and start date are known), invitees are not counted as employees, not charged for, and not shown in the company directory or org chart; only the organization’s owners, admins and HR see them. Until then, an invitee who signs in sees only their own record and Get set up, not their colleagues. If they won’t join, the organization withdraws the invitation, which erases the invitee’s record, login and everything entered about them; Bizisy reminds HR of invitations still waiting after 30 days.
Announcements in Slack, Microsoft Teams and other chat tools
An organization can connect its own Slack workspace, or a channel of Microsoft Teams, Google Chat, Mattermost, Discord or Rocket.Chat, so that Bizisy posts there when someone joins, moves team or gets a new job title (and, only if the organization turns it on, when someone has left). Each post holds only the person’s name, job title, team and manager, and the organization’s name; it is posted on the day the change takes effect and never earlier, so a planned change or leaving is never posted before it happens. Owners, admins and HR see each post before it goes and can skip it. For Slack, Bizisy keeps the access token Slack gave it, encrypted, the workspace’s name and identifier and the chosen channel, and, to mention the person in the post, asks Slack which member has their work email (Slack already holds it; Bizisy keeps no answer). If someone removes Bizisy from the Slack workspace or revokes its access, Slack tells Bizisy, naming only the workspace’s identifier; Bizisy then deletes the access token it kept, stops posting there, records this in Activity, and shows owners and admins how to connect again. For Teams, Google Chat, Mattermost, Discord and Rocket.Chat, Bizisy keeps the address of the workflow or webhook the organization created in its channel, encrypted, and sends each post to that address only; Bizisy sends these tools no email address and mentions nobody there, so the post names the person. Bizisy keeps a record of which announcement was posted, skipped or could not be posted, with the person’s identifier and the day only (never the text). Slack (Salesforce), Microsoft Teams (Microsoft), Google Chat (Google), Mattermost (the organization’s own server, or Mattermost Cloud), Discord and Rocket.Chat (the organization’s own server, or Rocket.Chat Cloud) are the organization’s own tools, chosen and controlled by it: what is posted there is kept under their terms and the organization’s settings, and stays in the channel after the organization disconnects or the person’s data is erased in Bizisy. Nothing is sent to any of them unless an organization connects it.
Directory sync (Google Workspace and Microsoft Entra)
An organization can connect its own Google Workspace or Microsoft Entra directory. An administrator of that directory grants Bizisy access; Bizisy keeps the access it was given (a refresh token or the directory’s tenant id) encrypted, and the directory’s identifier (the Google customer id or the Entra tenant id) so that a directory is connected to one organization only. While connecting, Bizisy reads the connecting administrator’s email and role from the directory to check they may connect it, and does not keep them. Nothing is sent to the directory until an owner or admin finishes the setup. From then on Bizisy sends the directory what an account needs and nothing more: first and last name, work email, job title, team (as the department), manager and the groups mapped to a team, the organizational unit the organization chose for new accounts (Google Workspace), and whether the account is suspended, each on the day it takes effect, never earlier. It never sends pay, private details or future changes, never deletes accounts and never assigns licences. The directory is the organization’s own system, chosen and controlled by it. Once, on request, Bizisy can also read the directory’s accounts (names, email, title, department, manager) to add or link people. When Bizisy creates an account, its first password is kept encrypted until the person sees it through a one-time link sent to their personal email (or until HR reveals it once), and for at most 7 days. When HR confirms a new account, Bizisy keeps the personal email shown to HR then, and sends the link only if the person’s personal email is still that address. Which account belongs to whom is kept with the organization’s data and erased with the person; disconnecting forgets the connection and those links, and gives Google back the access it granted.
Calendar invites (Google Calendar and Outlook Calendar)
Where Bizisy offers it, an owner or admin can connect one Google or Microsoft calendar of the organization (usually HR’s) so that Bizisy puts a new hire’s first-day meetings, and, only if the organization turns it on, onboarding tasks’ due dates, on that calendar as invitations. The person who connects it signs in with Google or Microsoft and allows Bizisy to manage events on calendars they own; Bizisy keeps that access encrypted and the account’s identifier and email address, and only reads the events it made. Each invitation holds the meeting’s title, the new hire’s name, the time, the organization’s own note, and the invited people’s names and work email addresses (the new hire, their manager, their team or the people the organization chose; an assignee for a task). It is sent from the connected calendar at most as many days before the first day as the organization chose, never before the person is recorded as a hire, and is moved or cancelled when the start date changes, the hire is withdrawn or the person’s data is erased (meetings that already happened stay in the calendars). Bizisy keeps which invitation belongs to which person (the provider’s event identifier and link) and a log of what each run did, without names. Google and Microsoft are the organization’s own tools, chosen and controlled by it, under its own agreement with them: invitations stay in people’s calendars under their terms after the organization disconnects. If the organization runs interviews in Bizisy and keeps Interviews on for that calendar, each interview booked from then on is also sent as an event from it: its title (“Interview:”, the candidate’s first name and the job), the step, job and organization, the time, the place (an address or the video link HR set) and a link to Bizisy’s Interviewing page, with the interviewers’ names and work email addresses and the candidate’s name and email address as guests, each guest seeing only themselves; never pay, notes, scores or the CV. If the step asks for it, Google or Microsoft makes a Google Meet or Microsoft Teams link for it in the organization’s own account, which Bizisy stores with the interview and shows to the candidate and the interviewers. Moves and cancellations follow; the event is cancelled when the interview is, or when the candidate’s data is deleted. Nothing is sent to Google or Microsoft unless an organization connects a calendar, at its own request.
Payroll tools (Staffology, Xero Payroll, Silae)
An owner or admin can connect the organization’s own payroll tool: Staffology (IRIS Software Group, United Kingdom) with an API key from that account, Xero Payroll (Xero Limited, New Zealand, for UK payroll) by signing in to Xero, or Silae (Silae SAS, France) with the API access the organization’s Silae partner gives it. Owners, admins and HR then choose which legal entity goes where and, for a locked pay period, see exactly what would be sent before sending it. Nothing is sent until an owner, admin or HR member allowed that connection to receive pay and private data (recorded in Activity, revocable in Payroll settings) and pressed Send. Staffology and Xero Payroll receive, for new and changed employees, their name, work email, date of birth, home address, National Insurance number, employee number, start date, job title, bank details (sort code and account number taken from a UK IBAN) and pay, the last day of leavers (Staffology), and the period’s variable pay; Silae receives only the period’s variable pay by employee number. For new UK employees the tool needs answers Bizisy does not keep (title, gender as HMRC records it, marital status, the HMRC starter declaration or NI category): HR gives them when sending, and Bizisy keeps them only until they are sent. Bizisy keeps, per send, who sent which period and when, and for each person what was done or why it failed, in Bizisy’s own words; these results are removed when the person is erased and deleted with the company. Each tool is chosen by the organization and works for it under its own agreement (the organization’s processor, not ours); what it keeps stays under that agreement.
E-signature (Yousign)
An owner or admin can connect the organization’s own Yousign account (Yousign SAS, France, now called Youtrust) with an API key from that account, so that owners, admins and HR (and roles the organization allows to manage a person’s documents) can send that person’s document for electronic signature, in Bizisy or through the organization’s own integrations with Bizisy. Bizisy keeps the key, encrypted, the name of the Yousign workspace, and the secret Yousign gives Bizisy to sign the status updates it sends. When a document is sent, Bizisy sends Yousign the document and, for each signer (the person, their manager, the sender, or another colleague an owner, admin or HR member chooses in Bizisy), their name, email address (the work email, or the personal email when there is no work email), language and, for an advanced or qualified signature, their phone number for the one-time code (the work phone, or the personal phone when there is none). Yousign then emails each signer and runs the signature under its own terms. Bizisy keeps a record of each request with identifiers, statuses and dates only (never names, email addresses or phone numbers), and, once everyone has signed, stores the signed copy among the person’s documents (seen by whoever saw the original) and the signature audit trail Yousign produces (signers’ details and how they signed; HR only). The person and their manager are only asked to sign a document they can already see in Bizisy; a colleague chosen as another signer sees it in Yousign. Yousign is chosen by the organization and works for it under the organization’s own agreement with Yousign (the organization’s processor, not ours); what Yousign keeps stays under that agreement after the organization disconnects or a person is erased in Bizisy. Nothing is sent to Yousign unless an organization connects it and someone sends a document.
Spend management tools (Pleo, Moss, Payhawk and Spendesk)
An organization can connect its own Pleo, Moss, Payhawk or Spendesk account, with an API key it creates there (Pleo: by approving Bizisy in Pleo). Bizisy keeps the key, or the access Pleo granted, encrypted. To match people, Bizisy reads the people in the tool (name, work email and, where the tool says so, their role, status, team, manager and active cards) and keeps, for people who are in Bizisy, only the tool’s account identifier, email, state, team membership, whether they are an administrator, their manager in the tool and how many active cards they have; people in the tool who are not in Bizisy are only counted. It also keeps the tool’s team or cost centre names. Nothing is changed in the tool until an owner or admin has reviewed the plan and started syncing. From then on, and only where the tool’s API allows it, Bizisy sends: first and last name and work email to invite a new hire (Payhawk, when HR confirms or the organization chose automatic invites), team membership and team names (Pleo, Payhawk), the team lead as a team’s manager or a cost centre’s owner (Payhawk, Spendesk), and a request to block a leaver’s active cards the day after their last day (Payhawk). It never sends pay, private details or future changes, never deletes people, cards or expenses, never changes spending limits, never changes accounts the tool marks as administrators, and never replaces a cost centre owner the organization chose itself. Making someone an approver, and the first card block on an account Bizisy did not create, wait until an owner or admin confirms that the account matched by work email is that person’s. What the tool’s API can’t do is listed for HR in Bizisy instead. The tools are the organization’s own, chosen and controlled by it; what Bizisy sent stays there under the organization’s agreement with that provider. Erasing a person deletes what Bizisy kept about their accounts; disconnecting a tool deletes what Bizisy kept about it.
E-signature with DocuSign, Dropbox Sign, Signaturit or Skribble
Instead of, or as well as, Yousign, an owner or admin can connect the organization’s own DocuSign account (where Bizisy offers it: the person connecting signs in with DocuSign and allows Bizisy to send envelopes), Dropbox Sign account (with its API key), Signaturit account (with its access token) or Skribble account (with its API user and key); owners, admins and HR choose which connected tool new requests go through. Bizisy keeps that access encrypted, the account’s identifier and name (for Skribble, the API user name and whether the account is in Switzerland or the EU), and a secret of its own to recognise the status updates the tool sends back; for Dropbox Sign, Bizisy also creates an app called Bizisy in the organization’s account so that only its own requests report back, and removes it on disconnect. When a document is sent, Bizisy sends that tool the document, a hidden reference to its own request, and, for each signer, their name, email address and language, and their phone number only for a level that tool confirms by a code sent by SMS (DocuSign and Skribble advanced signatures). The tool then emails each signer and runs the signature under its own terms. Bizisy reads each request’s status back from the tool, keeps the same records as for Yousign (identifiers, statuses and dates, never names, email addresses or phone numbers), and once everyone has signed stores the signed copy among the person’s documents and, where the tool produces one separately, its audit trail or certificate (HR only; Dropbox Sign puts it inside the signed copy). Each tool is chosen by the organization and works for it under the organization’s own agreement with it (the organization’s processor, not ours). Nothing is sent to these tools unless an organization connects one and someone sends a document through it.
Qualified signatures in Autenticação.gov (Portugal)
An organization in Portugal can ask for a person’s document to be signed in Autenticação.gov, the Portuguese state’s app and website, with a Cartão de Cidadão or Chave Móvel Digital, without any e-signature tool. Each signer downloads the document from Bizisy, signs it there under the Portuguese state’s terms, and the signed file is uploaded to Bizisy, by the signer in their workspace or by owners, admins or HR for them. Bizisy checks each upload with its own signature validation service, run on Google Cloud in the EU like the rest of Bizisy: that it is the same document, unchanged, and that each new signature is a valid qualified signature of someone asked to sign (the name on the signing certificate is compared with the name in Bizisy). To check a certificate, the service asks the certificate authority that issued it whether it is still valid (it sends the certificate’s identifiers, never the document), and reads the European Commission’s public trusted lists. When everyone has signed, Bizisy adds long-term validation data and a timestamp to the signed copy, for which it sends a timestamp authority a fingerprint of the file (never the file). Bizisy keeps the signed copy among the person’s documents (seen by whoever saw the original), and, for owners, admins and HR, what each check found: the name and serial number on each signing certificate, the signature level and time. A file refused by a check is not kept. Erasing a person removes what was read from their certificate; a person’s data export includes it.
Document templates and documents made from them
Owners, admins and HR (and roles the organization allows to manage people’s documents) can write document templates in Bizisy (contracts, written statements of working conditions, letters, policies and other employment documents) or copy Bizisy’s own, and generate documents from them for one person or a group. A template holds text and placeholders, not personal data; Bizisy keeps each template, its draft, every published version, who changed or published it and when, with the organization’s data. To preview or generate a document, Bizisy fills the template with what the organization already keeps about the person (their name, address and identifiers, job and contract, pay, the legal entity and, where used, custom fields), only with what the person generating it may see: pay only for those who see pay, and private or pay details never through an API key or AI app. Values typed for one document only are used for that document and not kept elsewhere. Each generated document is stored as a PDF among the person’s documents, with the template and version it came from and a fingerprint of its text, and, privately, the filled text it was made from, so that a Word copy downloaded later says exactly the same; both are deleted with the document, when the person is erased, or with the organization. Bizisy checks templates against the employment law of the person’s country (what a document must contain, the signature it needs, when it is due): a starting point, not legal advice.
Templates can hold contract clauses (a non-compete, probation, remote work, confidentiality and others) from Bizisy’s clause library or the organization’s own, kept like templates with each published version. A clause has typed details (a duration, a compensation percentage, the tasks a probation assesses…) that HR fills in when generating; Bizisy checks them against the law of the person’s country, using what the organization already keeps about them and what HR may see (the contract type and its length, whether they work part time, whether they are under 18 from their birth date), without storing anything new about the person. Each generated document records which clauses it contains and their versions; the details typed are in the document itself and, while it is a draft waiting for HR, kept with the draft like other values typed for that document only.
A template or clause can be started from the organization’s own Word document (.docx, up to 5 MB). The file is uploaded to Bizisy’s storage, read once on Bizisy’s servers to turn its text, headings, lists and tables into the template’s text and to find what looks like a blank to fill (such as [Name], ____ or highlighted words), and then deleted: as soon as the draft is made, or within two hours when it is not imported. Pictures, comments, footnotes, headers and footers are left out, and files with macros, passwords or links to content elsewhere are refused without being opened. The text that becomes the template is whatever the document said: if it still holds a real person’s details, they are in the draft until HR replaces them with fields, as with any text HR types. Activity records that a template was imported, never what the file said. An organization can also require that a new version of a template is approved before documents are made from it, by another HR person or by an owner: Bizisy keeps the version waiting, who asked for it and when, who approved it or sent it back, when, and their comment, and emails the people who may approve it and, once decided, the person who asked (the emails name the template, never a person).
Written statements of working conditions and change notices
EU law asks every employer to give each employee a written statement of their main working conditions and to tell them in writing when one of those conditions changes. When a hire is recorded in an organization that uses Documents (unless it turned this off), Bizisy prepares that statement from the organization’s template, or from Bizisy’s own for the person’s country, with the deadline the law of that country sets; when a change of those conditions is recorded to take effect (a new job title, place of work, employer, contract term, working time, notice period or base pay, once approved where approval is required; never a correction of a mistake), it prepares a change notice listing only what changed, its value before and after, and the day it takes effect. People can ask for their own statement in My workspace, and HR can prepare statements for people already employed. A prepared document is HR’s until it is sent: Bizisy keeps, for HR only, who it is for, why and when it was prepared, its deadline, the fields that changed with their values for a change notice (pay included when the base pay changed), values HR typed for that document only, and why it could not be sent by itself; the person, their manager and API keys or AI apps do not see it, it is not in the person’s own data export, and Activity does not name the person before it is sent. HR sends it, edits it or discards it; when the organization keeps it on, a statement HR has not acted on goes out by itself on its legal deadline, filled with what the organization keeps about the person as HR would see it, and never with a value missing. Sent electronically, the document appears among the person’s documents, they get an email (it names neither the document nor anything in it) and are asked to confirm in My workspace that they received it; as proof of delivery, Bizisy records on the document when it was sent, when the person first opened it and when they confirmed receipt, and confirming adds a receipt page to a copy of the PDF with the name typed, those times, a SHA-256 fingerprint of the document, a keyed one-way hash of the network address used (never the address itself) and the browser’s name. Confirming receipt is not agreeing. Printed and handed over instead (in the Netherlands without the person’s consent to electronic delivery, or in German sectors where the law asks for a signed paper copy), Bizisy records the day HR says it was handed over. A person can agree, or stop agreeing, to receive their employment documents electronically in My workspace, or HR records it for them; Bizisy keeps that choice, when it was made, by whom, and its history. Prepared documents and consents are deleted when the person is erased or with the organization, and are part of HR’s copy of the person’s data; the person’s own copy includes the ones sent to them, with their proof of delivery, and their consent.
Accepting a document in Bizisy
When HR sends a person a document to accept in Bizisy (where a simple electronic signature is enough), the person accepts it in My workspace by typing their full name and confirming: a simple electronic signature (Regulation (EU) No 910/2014, art. 25). Bizisy then records the name typed, the time, a SHA-256 fingerprint of the document, a keyed one-way hash of the network address used (never the address itself) and the browser’s name, adds them on a last page of the PDF, and stores that signed copy among the person’s documents (seen by whoever saw the original), with the request record (identifiers, statuses and dates). They are kept and deleted like the person’s other documents.
Amendments, end notices, work certificates and declarations
Bizisy can also prepare, for HR to review, the other documents of a person’s employment: an amendment to their contract when an approved change takes effect (only if the organization turned this on; never for a correction), with the change’s values before and after and a reference to their latest contract made in Bizisy; for a fixed-term contract, the notice before it ends, saying whether it continues and on what terms, once HR has decided (a renewal, an open-ended contract or the end, recorded in their job like any other change and following the organization’s approval rules); a work certificate when their last day is reached (where the law of their country gives one then), with their dates and the positions they held, and in Germany, on request, a qualified reference with an assessment HR writes; and declarations of employment or of employment and pay. These are prepared documents like the written statement above, kept and shown in the same way: HR’s until sent, never seen by the person, their manager, API keys or AI apps before, and a last day or an ending contract is never revealed to the person by them before it has been announced. People still employed can ask for an employment declaration in My workspace, and for a salary declaration only if their organization allows it (it shows their pay), at most five requests a day; depending on the organization it is sent to them at once or prepared for HR. Bizisy keeps what was asked, when and in which language, with the prepared document; former employees ask their former employer directly.
Policies to acknowledge
An organization’s owners, admins and HR can publish a policy (for example a staff handbook, an IT policy or a privacy notice for staff) to everyone employed or to a saved group. A policy is the same text for everyone and holds no personal data; Bizisy keeps each published version’s text, when it was published and to whom. Each person asked sees it in My workspace, with what changed since the version they last acknowledged, and acknowledges it by typing their full name and confirming they have read it: a simple electronic signature (Regulation (EU) No 910/2014, art. 25). Bizisy records, for each version, the name typed, the time, a SHA-256 fingerprint of the text, a keyed one-way hash of the network address used (never the address itself) and the browser’s name, and who is still asked and by when. Owners, admins and HR see who acknowledged which version and who has not; managers, colleagues, API keys and AI apps do not see a person’s acknowledgements (webhooks carry identifiers only). A person who has not acknowledged a policy a week before its date gets a reminder email naming the policy, sent only to them. Acknowledgements stay as the organization’s record when a policy is retired; they are deleted when the person is erased or with the organization, and are part of the person’s data download and of the company export.
Approvals
An organization can require that job changes, terminations or pay changes are approved before they take effect, by HR, by the person’s manager (or, when the person has no manager, the team lead of their team), or by both. While a change waits, Bizisy keeps it as a request: the change as proposed (for example the new title or manager, the last day and its reason, or the new pay and its note), who proposed it and when, and for each step who approved or rejected it, when and their comment. Job and termination requests are seen by the organization’s owners, admins and HR, the person’s managers, whoever proposed them and a team lead asked to decide one; pay requests only by owners, admins and HR signed in to Bizisy. The person a request is about does not see it while it waits; once decided, it is part of the data they can download. Each approver gets an email naming the kind of change, the person, the date and who proposed it, never a pay amount. Requests are kept with the organization’s HR data, deleted when the person’s data is erased or the organization is closed, and included in a person’s data download (pending ones only in the download HR makes for them).
Changes prepared for review
An organization’s owners, admins and HR, or an AI app or API key acting for them, can save a set of changes (for example new hires, moves, people leaving, new teams or pay changes) without applying it, for someone to check and apply in Bizisy. We keep the changes as prepared (names, work emails, job details, dates, reasons, notes and pay amounts where included), who prepared them and whether through an AI app, when, and who applied or discarded them. Only owners, admins and HR see them; pay amounts only when signed in to Bizisy, never through an API key or AI app. A set not applied within 14 days expires. Sets are deleted 30 days after they are applied, discarded or expire, or with the organization; when a person they name is erased, the set is emptied at once and deleted within a day. Applying a set records each change as usual, in Activity and, where approval is required, as an approval request.
Reminder emails
An organization’s owners, admins and HR can have Bizisy email them reminders once a day: probation and fixed-term contracts ending, people starting, and work anniversaries. A reminder names the person and the date (for anniversaries, the years of service) and links to them in Bizisy. It goes to the organization’s owners, admins and HR, and, as the organization chooses, to the person’s manager; anniversary reminders can also go to the person themself. Nobody gets a reminder about their own probation or contract, and a manager whose access was removed gets none. To send each reminder only once, Bizisy keeps a record of which reminder was sent for which person and date (internal identifiers and dates only), deleted automatically after about 400 days; when the person’s data is erased, it is unlinked from them at once and deleted within a day. A person’s data download lists the reminders sent about them.
Reminders can also cover documents with an expiry date (such as an ID card, a work permit or a certificate), company renewals (such as an insurance policy) and occupational health checks. A document reminder names the person and the document’s category, never its title or file, and goes to owners, admins and HR, and to the person’s manager only when the organization chooses it and the document is shared with them. Company renewals are company records: a type, a name, an optional provider and reference, the renewal date, how often it renews, whether it renews by itself, its notice period, its cost, notes (which must not hold personal data), the company documents attached to it (kept in Documents, seen by owners, admins and HR) and a history of each renewal (when, the dates, the cost before and after, a note, and who recorded it). A renewal can name an owner, someone with an owner, admin or HR login, who gets its reminders together with HR; only owners, admins and HR see renewals. They are kept until the organization deletes them or closes; erasing a person’s data removes them as an owner and from the history. Owners, admins and HR, or an AI app or API key acting for them, can also add a renewal from its document, such as an insurance policy, a lease or a licence agreement: Bizisy sends the file to Google Cloud Document AI, in the EU, which returns its text and keeps nothing (a text file is read by Bizisy itself), finds the renewal’s details in that text and shows them to be checked, and deletes the file and its text once it is read, or within an hour if it is never read. An AI app or API key gets only the details found and the lines they came from, never the whole text. Only what is then saved is kept, and the document itself only if they choose to keep it in Documents. To limit how many documents are read a day, Bizisy notes for about two days who started each reading and when, never the file or its text.
When an organization records someone’s last day, it also records whether that person has been told yet. Until someone at the organization marks them as told, or the day passes, Bizisy shows the last day, the reason and anything that follows from it (offboarding tasks, changes to their time off) only to the organization’s owners, admins and HR and to the person’s managers, and keeps it out of the person’s own pages, data download and history. Meanwhile a reminder, a week before the last day by default, asks HR and the manager to tell them; it names the person and the date, is never sent to the person, and each organization can change or turn it off in Settings → Reminders. Who marked someone as told, and when, is kept in the organization’s Activity and change history like any other change.
1:1s and quarterly check-ins
Unless the organization switches 1:1s off, people and their managers can keep a regular 1:1 in Bizisy (and, if the organization allows it, a skip-level 1:1 with a manager’s manager, or a 1:1 with a dotted-line manager): how often it happens, each meeting’s date and time and whether it was held, moved or skipped, and when it started and finished; the topics each of them adds to talk about (with an optional tag), the notes they take together on each topic and whether it was done or moved to next time; action items (who owns them, by when, done or not); and, for each meeting, a private note and a rating of how useful it was from each of them. A private note and a rating are seen in Bizisy only by the person who wrote them: not by the other side, not by higher managers, not by HR; Activity records that a note was saved, never its text, and it is never in the change history. When a skip-level 1:1 is set up, the manager in between is told it exists, never what is said in it. A person can be exempt from regular 1:1s: their manager asks and HR decides, or the person asks and their manager, then HR, decides; Bizisy keeps who asked, the justification they gave, an optional end date and each decision with its note. The justification is seen only by the person, their direct manager and the organization’s owners, admins and HR. If the organization turns on quarterly check-ins, the person and their manager answer the organization’s questions each quarter (and, if the organization asks for it, the manager gives a rating from 1 to 5); each sees the other’s answers once submitted. The shared parts and the check-ins are seen by the person, their managers and the organization’s owners, admins and HR, who see 1:1 health (whether 1:1s happen and action items are done, never what is said); never by colleagues; over API keys and AI assistants only the person’s own. Bizisy reminds both the day before a 1:1 and the owner of an action item the day after it was due, and reminds each of them when their check-in answers are missing; managers get an email when HR asks or reminds them about their team’s 1:1s and when someone on their team asks to be exempt (optional emails the organization can turn off in Settings → Notifications). Summaries, action items given to someone and decisions are in-app notices. If the organization turns on calendar invites and connected Google Calendar or Microsoft Outlook, each 1:1 with a time is sent as an event to both people through that connection: its title (“1:1:” and both names), date, time and both work emails, never the agenda or notes. Everything is kept while the people work there and deleted when either person’s data is erased or the company closes; a person’s data download includes their 1:1s, meetings, topics, action items, their own notes and ratings, their check-ins and their exemptions, and the organization’s export of a person’s data (for an access request) also the notes written in their 1:1s.
Announcements
An organization’s owners, admins and HR (and, if the organization allows it, managers to the people reporting to them) can post announcements: a title, a text and, optionally, a request that each person confirms they have read it, by a date. When an announcement is published, Bizisy keeps the list of people it was published to (people employed on that day in the chosen audience; never people outside the organization or not registered yet). For each of them it keeps when they first opened it and, when it asks for it, when they confirmed, whether in the app or at a time clock kiosk, and a fingerprint (a SHA-256 hash) of the exact title and text they confirmed, as the organization’s evidence that they were told. Once someone has confirmed, the text can’t be changed. The owners, admins and HR, and the person who posted it, see who opened and confirmed it; a manager posting to their team sees only their own announcements. Each person gets an in-app notice, a push notification if they turned them on, and an email with the title and a link (an optional email the organization can turn off in Settings → Notifications; the text stays in Bizisy); reminders to confirm go to the person only, before and after the date, and stop when they confirm or leave. If the organization connected a chat tool and kept it on, announcements to everyone post their title to its channel. Drafts can be deleted; published announcements (also withdrawn ones) and these records are kept until the organization closes; erasing a person’s data deletes their records and takes them off every list, and a person’s data download includes the announcements published to them and when they opened and confirmed each. Organizations must not put health or other special categories of data about anyone in an announcement.
Occupational health checks
If an organization turns on health check reminders, Bizisy keeps, for each person, the date of their last occupational health check and, when HR sets one, the date the next one is due. Bizisy never keeps a result, a fitness decision, a diagnosis or any note about the check: those stay with the organization’s occupational health service. The interval comes from the law of the country the person works in (for example every 2 years in Portugal, every year under 18 or from 50) or from the organization. Only the organization’s owners, admins and HR see these dates in Bizisy (and custom roles allowed to see private details), and the person sees their own in My workspace; managers and colleagues never do, and API keys and AI assistants only when the organization allowed them sensitive details. A reminder names the person and the date only. The dates are kept while the person is at the organization and deleted when their data is erased or the company closes; a person’s data download includes them.
Checklists
An organization can keep checklists for onboarding, offboarding and other moments: lists of tasks with a title, an optional description and link, who does each task and its due date. When it adds someone, or records their last day, Bizisy starts the matching checklist for that person; where a termination needs approval, offboarding starts only once it is approved. For each checklist we store whom it is about, its tasks, who ticked or skipped each task and when, the reason given for a skipped task, and comments people add. Checklists are job details: the organization’s owners, admins and HR and the person’s managers see them in full; the person sees the tasks given to them, and someone given a task about another person sees only that task and whom it is about. Offboarding is discreet: the person leaving and colleagues given a task see it only shortly before it is due (7 days by default), unless HR shares the checklist with the person earlier. Through an API key or AI assistant, comments and skip reasons about someone else reach only HR. Organizations must not put health or other special categories of data in tasks or comments. Activity records of these changes keep only which fields were sent, never comments or reasons. Checklists stay with the organization’s data until it is deleted; erasing a person’s data deletes their checklists and the comments they wrote.
When preparing a batch of job changes, owners, admins and HR can describe it in their own words (for example “move the energy campaign to Team Porto 3 from 1 December”). Bizisy sends that text, today’s date and the organization’s team, location and job title names to the same language model as Ask HR (Google Cloud Vertex AI, in the EU), and gets back the fields of the batch. Bizisy then matches the names to people itself: the list of the organization’s people is never sent. Nothing is saved by the model or used to train it; the result only fills in the form for HR to check, and nothing changes until HR applies the batch. The AI never chooses who moves. It uses the organization’s AI credits, and Activity records that it was used (never the text).
Owners, admins and HR can group people who start together (a start group): we keep its name, start date, who is in it, who made it and when. Its progress (contract, admission notice, invite, onboarding, training) is worked out from the data Bizisy already holds each time it is opened. Groups are part of the company export, a person is taken out of every group when their data is erased, and groups are deleted when the company closes.
Owners, admins and HR can prepare a batch of the same job change for many people (a move batch): we keep its name, the change, its dates, who is in it and, for each person, whether they are ready, left out or blocked and why, the fields that change, who prepared, approved and applied it, and when. Each change is written to the person’s job history as any job change is. Until the batch’s announce day, the people it moves (and colleagues who don’t manage people) see their job as it is; their own data download includes the batch once it is announced. Batches are part of the company export, the person’s rows are deleted when their data is erased, and everything is deleted when the company closes.
Owners, admins and HR see one list of cases that need HR (the case list), worked out each time from the data Bizisy already holds; nothing new is collected for it. When they snooze a case or hand it to a colleague, we keep the case’s reference, the person it is about, the day it comes back, whom it was handed to, who did it and when. Only owners, admins and HR see this; it is part of the company export, deleted when the person’s data is erased or when the company closes, and snoozing or handing over is recorded in Activity.
If the organization keeps checklist task emails on, the daily reminder email also lists each person’s tasks that are due or overdue: on the due date and then once a week while the task stays open. HR tasks go to the organization’s owners, admins and HR; other tasks go to the person they are given to, from their first working day. Like other reminders, these emails store only internal identifiers and dates, and the task titles and names are filled in when the email is sent.
In-app notifications
Reminders, checklist tasks, approval requests, “a person added a document” and “HR shared a document with you” notices also appear in Bizisy itself, under the bell in My workspace and Manage, for the same people the email goes to, whether or not the organization emails them. So do the yearly pay-rights reminder and, for the person who asked only, a notice that HR answered their request about pay (it never carries the answer, and is not emailed). Some notices appear only there and are never emailed: to a person, that HR asks them to add a document (its category and date only); to owners and admins, that another owner or admin switched AI assistants or API keys on or off, or switched modules on or off; and to a person whose API keys or connected AI apps stopped working because the organization switched them off, that this happened and whether they come back (these keep only which switches or modules changed). For each notice we keep the address it is for, its type, internal identifiers of what it is about, when it was created and when it was read. Names, titles and links are filled in when the person opens their notifications, never stored with the notice, and a notice that no longer applies (a request decided, a task done, a document deleted, a person erased) is removed. A person sees only their own notices, matched to their login; API keys and AI assistants see them only for the person they act for, and never notices about pay changes. Each notice is checked again whenever it is shown: once its reader no longer holds the role that earned it (for example HR, or that person’s manager), it is no longer shown. To prevent abuse, the number of notices per person and per organization each day is limited, and the same notice on the same day is kept once. Notices are deleted 90 days after they are created, when the person they are for or about is erased, or with the organization. A person’s data download lists the notices addressed to them (type and dates).
An organization’s owners and admins choose in Settings → Notifications which of these notices are also emailed, and may set a monthly limit on extra emails. To bill optional emails above what is included, we count how many each organization sends per month (counts only, no recipients or content), kept for about 13 months.
Data exports and BI tools
An organization can send its HR analytics to its own data tools under Integrations: scheduled exports to its own BigQuery, Google Cloud Storage, Amazon S3 or Azure Blob Storage, and a read-only feed that Power BI, Excel and Looker Studio read with the organization’s BI token. Owners and admins set these up; HR can see them. What is sent: everyone employed on the day (names, work email and phone, pronouns, job title, team, manager, location, legal entity, employment and contract terms), job history, teams, locations, legal entities, open positions (never drafts, notes or whom a replacement replaces), monthly headcount totals, checklists with their progress, and custom fields of the public and job tiers. Private details (such as home address, birthday, emergency contacts, bank, tax and social security details) are never sent, and nothing planned shows before its day. Pay (everyone’s pay history and the pay ranges of open positions) is sent only after an owner, admin or HR member turns on pay sharing in the app; Bizisy records who did in Activity, and anyone of them can turn it off. The organization is the recipient: the files land in its own storage and the feed is read by its own tools, under its own control and terms. For Google Cloud and AWS, Bizisy uses no stored keys: the organization lets Bizisy’s own identity (each token names the organization) write to its bucket or dataset. For Azure, Bizisy keeps the container’s access address encrypted. Bizisy keeps, for each export, the schedule and what was last delivered (counts and the place, never anyone’s details), and a log of deliveries that never names anyone, for 30 days. The BI token is stored only as a hash. Erasing someone in Bizisy removes them from later exports and from the feed, but not from files or tables already delivered or from data a report already loaded: those copies are the organization’s, and it is responsible for them.
Other connected tools
An organization’s owners and admins can connect other tools it uses (such as a task tracker, an identity provider, a recruiting or a payroll tool) under Integrations; each tool’s page says what Bizisy sends and reads before anything is connected, and nothing is exchanged with a tool unless the organization connects it. For each connection Bizisy keeps the access the tool gave it (tokens, or the API token or password typed in) encrypted, never shown again; the account’s name and identifier in that tool; the connection’s settings; its health (when it last worked and why it last failed, in Bizisy’s own words); and, where the tool sends Bizisy its own notices, a secret to check them, encrypted. Bizisy keeps a log of what it did with each tool (such as “connected”, “sent 2 tasks”, “the tool refused the request”) that never names anyone, for 30 days, and the identifiers of the tool’s notices it has already handled, for 7 days. Where a Bizisy record (a task, a person’s account) is linked to a record in the tool, Bizisy keeps both identifiers and the record’s address in the tool; these links are erased with the person and deleted when the tool is disconnected. Each tool is the organization’s own, chosen and controlled by it: what is sent there is kept under its terms. Disconnecting forgets the connection, its settings and links, and gives the tool back the access it granted where the tool allows it.
Marketplace apps
An organization’s owners and admins can install apps made by other developers from Integrations → Browse. Before an app is installed, they see who makes it, whether Bizisy reviewed it, and everything it will be able to do; nothing is shared until they allow it. An installed app then receives, through the Bizisy API and webhooks, the data the organization allowed: by default what every employee sees in the company directory (names, job titles, teams and work email) plus the areas it was allowed (for example people and their jobs, documents, checklists or the company structure). It receives private details (such as home address, personal contacts, birthday, tax, social security and bank details) or pay only when an owner or admin explicitly ticked that for it. Its webhook notices follow the rules for webhooks below. The app’s developer receives that data as the organization’s own processor or as an independent controller under the developer’s own privacy policy, which is linked on the app’s page; once received, it is outside Bizisy. Everything an app changes is recorded in Activity with its name. Uninstalling an app ends its access at once and deletes its webhook endpoint. We keep the installed app’s name, what it was allowed, who installed it and when, its last use, and only hashes of its tokens.
Every app is owned by one developer or by a developer organization (see Developer accounts and organizations below). For each app we keep its description and links (its manifest), its icon and screenshots, a hash of its client secret, and each version submitted for review with the reviewer’s decision and reason and the email address of the developer who submitted it, so we can tell them the decision. Bizisy’s team reviews every app before other organizations can install it, and can suspend an app that puts organizations’ data at risk.
Developer accounts and organizations
People who build apps sign in to the developer console at developers.bizisy.com with a developer account of their own (a password, Google or Microsoft; the email is confirmed before the first sign-in). Developer accounts are never billed. We are the controller of this data. For each developer account we keep the name and email address, when it was created and last used, and whether it is active or suspended; and its sessions (only as hashes) for up to 7 days.
Each app is owned either by one developer or by a developer organization. Apps a developer owns themselves are listed as “by” the developer’s display name, with the public page address, website and support email they choose; their sign-in email is never shown. Any developer can create organizations and belong to several. For each organization we keep its name, public address, logo, website and support email, which appear publicly on its page and its apps’ listings; its members and their roles (owner or developer); and its invitations (the invited email, the role and who invited them) for 14 days or until they are accepted or declined. An organization’s page never shows its members’ names or email addresses. An owner can move an app between themselves and organizations they own; we record that in their developer Activity. An owner or admin of a Bizisy company who also owns an organization can link it to the company (or create one linked from the start), which then shows “Verified” with the company’s name and address. Owners and admins of that company see the organization’s apps and its members’ names and roles (email addresses only of the developers the company invited, or of everyone in an organization the company created), can invite developers and remove those it invited, and can unlink it; unlinking or closing the company removes only the link.
Each developer can have one developer sandbox: an organization that is never billed and holds at most 25 people and 5 logins, with fictional sample data on request, of which the developer is the owner. “Open sandbox” signs them in with a one-time code that works once, for 60 seconds, and is never put in an address. When neither the sandbox nor the developer console was used for 90 days we email a warning; 30 days later the sandbox is closed and its data deleted within the hour. A developer can delete their sandbox at any time and create a new one 24 hours later.
A developer can test the unreviewed draft of an app they build in a Bizisy company where they are themselves an owner or admin (the same person, by their confirmed email), instead of or as well as their sandbox. Only they can install it there, on that company’s own consent screen, which says it is an unreviewed draft; the install is recorded in that company’s Activity and shown as “Unreviewed draft” in its Integrations, and the company can uninstall it at any time. The developer console lists, for this, only the names and addresses of the companies where the developer is an owner or admin.
A developer can create access tokens for their own scripts and AI assistants, which work only on developers.bizisy.com (its API and its MCP server) and never with any company’s data. For each token we keep its name, the first characters of the token (to recognise it), a hash of the token (never the token itself, which is shown once), what it may do, the one owner of apps it may be limited to, and when it was created, last used, expires and was revoked. A token is deleted 30 days after it expires or is revoked, and with the developer account. What a developer does with a token is recorded in their developer Activity with the token’s name.
What a developer does in the console (creating, changing and transferring apps, organizations, invitations, the sandbox and their account) is recorded in their developer Activity, which only they see. A developer can download everything we keep about their developer account as a file (Account → Download my data), and delete it (Account → Delete, after confirming their email and a recent sign-in): their sandbox is closed, the apps they own themselves are delisted and deleted, they leave every organization (an organization they alone own and that has no apps is deleted; while they are the last owner of one with apps, deleting is refused until they make someone else an owner, transfer its apps or delete them), and their developer login is removed. Organizations’ apps stay with their organization; versions they submitted keep the review record without their email address. An organization’s owner can delete it once none of its apps are listed; its unlisted apps are deleted with it. When a developer offers an app to another developer (by email address) or to an organization, we keep the offer (the app, both owners, the address it was sent to, the developer’s optional message and the answer) and email the address or the organization’s owners; an offer is deleted 14 days after it is made if nobody answers, 30 days after it is answered, and with the account of whoever made or received it.
Partners (accountants, HR consultants, implementation and referral partners) and partner access
People who work for a partner firm sign in to the partner console at partners.bizisy.com with a partner account of their own (a password, Google or Microsoft; the email is confirmed before the first sign-in), held in a sign-in tenant of Google Identity Platform kept apart from every company’s; the console accepts only its own session cookie, never an API key or token. We are the controller of this data. For each partner account we keep the name and email address and when it was created and last used. For each firm we keep what it gave when it applied: its type, name, country, city, professional registration (for example its OCC member number in Portugal or its colegio number in Spain), website, contact email, phone and languages, who applied, our review decision and its reason, its members and their roles (owner or staff), its invitations (the invited email and role, for 14 days or until accepted or declined), its referral code, and its revenue share terms with their history (every default, firm or client term we record, with when it starts, who recorded it and why). When a referral partner applies, we check automatically whether its email or website domain is the email domain of an existing customer’s owner (we keep each company’s owner email domain for this) and how many referral applications arrived recently; an application those checks hold waits for our review, and we keep which checks held it. A firm can choose to be listed in the public directory at bizisy.com/accountants: the listing shows its type, name, country, city, languages, a short description and one contact link (its website or its contact email), never a person’s name or email address.
A referral partner never gets access to any company. Any other firm sees a company’s data only once one of the company’s owners approves its access, on a page that lists exactly what the firm would see and do, and an owner can change or revoke it at any time (Settings → Partner access); a revocation ends the firm’s access at once. For each access we keep the firm, the company, its state (requested, active, declined or revoked), what the owner allowed, the firm’s note to the owner, who decided and when, and when someone of the firm last opened the company. While it is active, each person of the firm who opens the company gets a login there, with no password of their own, reached only from the partner console; they work with the role of the firm’s type that the owner approved (the read-only Accountant role, the HR partner role, or the Implementation partner role, which sets the company up but never connects integrations and whose access ends by itself after the period the owner chose), and everything they do is recorded in the company’s Activity under their own name, as “name (via firm)”. Owners are emailed when access is requested, when it is approved and the first time the firm opens the company. A firm’s people never get API keys or connected AI apps in a company through this access. While access is active, the firm’s console shows the company’s name, address, number of active people, plan, what needs attention (such as invitations waiting or time off waiting for a decision, as counts only) and when it was last used; without active access, only the company’s name and the access’s state.
A firm can set up a company for a client: it enters the company’s name and country and its future owner’s name and email, and we email the owner a link to confirm it. Nothing is created until the owner confirms, chooses the address and their password and so owns the company; the link works once and expires after 14 days, and its record is deleted 30 days later if it was not used. A company created through that link, or through a firm’s referral link or code typed at sign-up, is attributed to the firm. For an attributed company we keep which firm referred it, how and when, and, for the revenue share we pay the firm, a ledger of the company’s paid Bizisy invoices, credit notes and refunds for as long as the firm’s revenue share runs (with the percentage and terms that applied to each): the company’s name, the invoice number and month, the amount excluding VAT and the firm’s share. The firm sees these lines on its monthly statement; it never sees anything about the company’s people. A firm’s own company is never attributed to it. On bizisy.com, a referral code from a firm’s link is kept in your browser for 30 days so that a sign-up within that time is attributed.
What a partner does in the console is recorded in their partner Activity, which only they see. A partner can download everything we keep about their account (Account → Download my data) and delete it (Account → Delete, after confirming their email and a recent sign-in); a firm’s owners can download the firm’s data.
Learning platforms (TalentLMS, 360Learning, Docebo, Moodle)
An organization can connect its own learning platform with its own credentials. Bizisy then creates a learner account for each new joiner a few days before their first day (the organization chooses how many, at most 14, and by default HR confirms each one; people already working there when it is connected are only added once HR confirms them), sending the person’s name and work email and, where the platform has the field, their job title, their manager and their team’s groups, branches or cohorts as the organization mapped them. It never sends private or pay details. The platform sends the person how to sign in; Bizisy never knows their password there. When the details change in Bizisy, Bizisy updates them there on the day they take effect; the day after the person’s last day it switches the account off (never deletes it). When a checklist task is a course, Bizisy enrols the person in it and reads whether they completed it, every hour (360Learning and Docebo also tell Bizisy when it happens), then ticks the task. Bizisy keeps the link between the person and their account and enrolments there. The accounts and training records are the organization’s, in its platform, and stay there after the person’s data is erased in Bizisy or the platform is disconnected.
LinkedIn Learning
Where Bizisy offers it, an organization with a LinkedIn Learning enterprise licence can connect it with an API application the organization creates in LinkedIn Learning; Bizisy keeps its secret encrypted and never shows it again. LinkedIn Learning is the organization’s own tool, under its own agreement with LinkedIn. Bizisy sends LinkedIn nothing about people and never creates, invites or removes accounts there. It asks LinkedIn Learning for courses when someone searches its catalogue, and once a day reads its activity report: for each learner, their work email, the courses they started, how far they got and when they completed them. Bizisy matches the work email to the person in Bizisy and keeps only the progress and completion of the courses assigned to them (on their task) and, for a completed course, a training record as described under Training. Report rows about people Bizisy does not know are dropped at once and only counted; names and anything else in the report are not kept. A course the person completed without it being assigned is added as a record waiting for HR, which the person and HR see and their manager only once HR confirms it (unless the organization chose to leave such courses out or count them at once). Skills LinkedIn tags on a completed course may be suggested on the person’s profile, where their manager or HR accepts or rejects them. When the organization gives its LinkedIn Learning account ID, courses open through the organization’s own single sign-on. The activity stays the organization’s, in LinkedIn Learning, after the person’s data is erased in Bizisy or LinkedIn Learning is disconnected.
Checklist tasks done in other task tools and service desks
An organization can choose that some checklist tasks (for example “order a laptop” on an onboarding) are done in its own Jira (or Jira Service Management), Linear, Asana, monday.com, ClickUp, Microsoft To Do, Microsoft Planner, Trello or Notion, or raised in its IT service desk: Freshservice, Zendesk or ServiceNow. Once it has connected the tool, Bizisy creates the task there when the checklist starts, with what the organization’s template says: the task’s title and details, the due date, labels, and the public and job details of the person it is about that the template names (name, job title, team, location, manager, work email, start date or last day, and a link to the checklist in Bizisy). It never sends private or pay details, comments or skip reasons. To give the task to the right person, Bizisy asks the tool which of its users has the work email of the person doing it; HR tasks, and anyone not found, go to the tool’s default assignee. Microsoft To Do and Trello cannot be given an assignee this way, so no lookup is made there: To Do tasks go to a list of the account that connected it, and Trello cards stay unassigned. Freshservice tickets are raised for the requester email the organization enters when it connects. An offboarding task is sent only from the day the people doing it would see it in Bizisy, so a departure is not shown to colleagues early. When the task changes in Bizisy (ticked, skipped, reassigned, a new date, a cancelled checklist), Bizisy changes it in the tool, adding a short comment when it closes or reopens it; when it is done, closed or deleted in the tool, the tool tells Bizisy (or Bizisy reads it, at least once a day; every hour for tools that send no notices, such as Microsoft Planner, Freshservice and ServiceNow) and Bizisy marks it done or skipped. Microsoft To Do, Microsoft Planner, Trello and Notion are told “done” by completing, archiving or moving the page to the trash instead of a comment where they have none. Bizisy keeps, on the task, the tool’s identifier, key, address and status. The tools are the organization’s own, chosen and controlled by it: what Bizisy creates there stays there under the organization’s control, including after the person’s data is erased in Bizisy or the tool is disconnected.
Country obligations: statutory notices, reports and payroll tools
For each legal entity, Bizisy lists what its country asks of an employer when someone joins or leaves (for example a hire or leave notice to Portugal’s Segurança Social, the Spanish Social Security and SEPE, or France’s URSSAF) and yearly staff reports (Portugal’s Relatório Único). Owners, admins and HR can add the codes these need that Bizisy doesn’t otherwise hold: company codes (such as an employer’s social security number, activity code, profession codes per job title) and, for a person, their nationality, education level, place and département of birth, and, for Portugal’s Relatório Único, the official code for why they left or why their fixed-term contract was made. A person sees those reason codes only in their own data export. Bizisy keeps a record of each notice HR made or marked as not needed: the person’s identifier, the obligation, the date it concerns, when and how it was made, a receipt number when HR types one, and, if the authority refused it, the authority’s documented reason. Nobody else sees these: never members, managers, API keys or AI connections; a person’s country data and the notices about them are erased with them and included in the personal-data export.
Where an organization’s owners or admins enter its Segurança Social Direta access for a Portuguese legal entity, and only when HR confirms a notice after seeing exactly what will be sent, Bizisy sends that hire or leave notice to the Segurança Social interoperability services: the employer’s and the person’s social security numbers, the person’s date of birth, the contract type, start and end dates, profession code, monthly base pay, working time and workplace, or the last day and the reason the employment ended. The password is kept encrypted, never shown again, and removed when the organization removes it or closes its account. From 2027, under Portugal’s new reporting model, the same applies to a change of a person’s base pay: Bizisy sends the employer’s and the person’s social security numbers, the first and last day of the employment and every monthly base pay since it started. The Relatório Único files and Spain’s Contrat@ file are made for HR (or the organization’s accounting firm, when its owner gave the firm access to private details) to download and file themselves; Bizisy sends them nowhere and keeps only a record that they were made (who, when, which annexes, how many people, and a fingerprint of each file), never the files. Where the organization maps pay items to the report’s columns, October’s allowances and overtime from its locked payroll periods are included in the file.
For Portugal’s Relatório Único, owners, admins and HR, or a role the organization gives Payroll edit access (for example its accounting firm), also fill yearly forms for Anexos 0, D and F. Anexo 0 holds company figures (turnover, the number of union members on 31 October as a count, posted workers, employer associations, overtime, capital and, optionally, spending and accounts). Anexo D describes how health and safety at work is organised and names the organization’s occupational doctors, safety technicians, heads of service, external health and safety services and the employer’s representative, with their professional numbers and, for heads of service and external services, their tax number; the people named are kept as part of this statutory record, not linked to anyone’s Bizisy profile. Bizisy adds counts of work accidents and days lost, worked out from absences of the leave types the organization marks as work accidents (counts per establishment and sex: no names leave time off), shown only to owners, admins, HR and roles with access to private details. Where Bizisy has a person’s sex as other than male or female, HR records for the report only the sex registered with Segurança Social, since the report has just those two; it is kept as that person’s private country data, erased with them and included in their data export. Anexo F lists the organization’s service providers: tax number, name, social security number, activity and the months, hours or workers of each engagement, typed in or imported from a spreadsheet. A self-employed provider’s tax and social security numbers and name, the health and safety staff’s and external services’ names and numbers, and the work-accident counts are never given to API keys or AI connections. These forms and lists are kept with the organization’s data until it changes or deletes them or closes its account, and are included in its data export.
For Portuguese legal entities, Bizisy also makes the vacation map the law asks employers to post at each workplace (mapa de férias): each person’s name and the start and end of their approved vacation, from time off, never the type of leave or a note. When HR marks it as posted, Bizisy keeps that version (names, vacation dates, the day it was posted and who recorded it) with the organization’s data; erasing a person removes their name and dates from the kept versions, and their data export lists them. Owners, admins, HR and the organization’s accounting firm see it.
An organization’s owners or admins can connect a Dutch payroll tool it uses, Nmbrs (Visma) or Loket.nl, for one legal entity. Every hour Bizisy then sends that tool the people who join (first and last name, work email, first day; and, only if an owner or admin turns it on, date of birth, sex, home address, personal email and IBAN), changes to those details, and the last day of people who leave. Pay is never sent. Bizisy keeps which of its people matches which record in the tool until the person is erased or the tool is disconnected. Turning the extra details on or off is recorded in the organization’s Activity.
Okta
An organization that uses Okta can connect it under Integrations → Okta: an Okta administrator adds Bizisy’s integration in Okta and gives an owner or admin its client ID and secret, which Bizisy keeps encrypted with the organization’s Okta address. Bizisy then keeps Okta accounts in step with HR, as directory sync does: for people starting after Okta was connected it creates an account a few days before their first day (once HR confirms it, or automatically if the organization chose that), activates it on their first day so that Okta emails its activation link to their work email (unless the organization turned that off), sends changes to names, job title, team (as the department), manager and the Okta groups mapped to a team or a job family on the day they take effect, never earlier, and suspends the account the day after a person’s last day. It never deactivates or deletes an account, and never changes an Okta administrator’s account or the account of someone the organization excluded. To link people to their accounts, Bizisy looks up the Okta user whose login is a person’s work email, and reads what that account holds (names, title, department, manager, status) and whether it has an administrator role; it keeps the account’s identifier, login, status and what it last sent, with the organization’s data, until the person is erased or Okta is disconnected. Okta never receives pay, private details or future changes. Okta is the organization’s own tool, under its agreement with Okta.
The SCIM service for identity providers
An organization’s owners and admins can create a SCIM token (Integrations → SCIM) for an identity provider such as Okta to read the organization’s people and teams from Bizisy. With it, that tool reads, for everyone who works there today, starts within 14 days or left in the last 90 days: the work email, given and family name, the name they go by, job title, team, manager and whether they work there today; and each team with its members. It never receives private or pay details, or a change before the day it takes effect, and it cannot change anything in Bizisy. Bizisy keeps only a hash of each token, its name, who created it, when, and when it was last used; tokens are shown once and stop working the moment they are revoked. What the identity provider does with what it reads is under the organization’s agreement with that provider.
Hiring: careers pages, candidates and referrals
An organization that switches Hiring on publishes its open jobs on its own careers page (at its Bizisy address) and in a job feed that job sites such as Adzuna, Jooble or Talent.com can read; the feed and the page hold the job post only (title, place, contract, hours, the pay range and the text), never anyone’s personal data. A candidate applies by sending a CV (PDF, Word or a picture, at most 10 MB), their name, email address and, if they wish, phone number, with the answers to the job’s questions. To fill in the form for them, Bizisy reads the CV: the text of PDF and Word files on our own servers, and of pictures with Google Cloud Document AI, in the EU, which returns the text and keeps nothing; the text read is not kept, only the CV file and what the candidate sends. The organization is the controller of this data and Bizisy its processor: the organization uses it to take the steps the candidate asked for before a possible contract (GDPR art. 6(1)(b)). Its owners, admins and HR, and the job’s hiring manager, see the candidates of that job (notes HR marks private stay with HR); other employees never see candidates; API keys and AI apps never see pay expectations, private notes or CV files, and cannot move, reply to, reject or hire anyone. Bizisy keeps, per application, the step it is at, the notes, messages and interview records the hiring team adds, the emails sent (application received, the next step, a message from the hiring team, “not this time”), and the date the organization promised an answer by. Each candidate gets a private link to a status page where they see where they stand, what was sent to them and the data held about them, can download it, withdraw (their application is then deleted at once) or ask for a new link; Bizisy stores only a hash of that link. A candidate who opts in joins the organization’s talent pool for 2 years (on their consent, art. 6(1)(a)): they are emailed 30 days before it ends to renew, and can leave at any time from the link in their email. When someone applies again to the same job, or asks to join the talent pool, with an email address the organization already has, nothing about that person changes: Bizisy emails that address a link to confirm it, keeps what was sent apart until then, and deletes it if nobody confirms within 48 hours. If HR adds someone’s CV themselves, Bizisy emails that person the notice the GDPR requires (art. 14). Unless the organization links its own privacy notice, its careers pages, forms and these emails link a notice for candidates that Bizisy writes for it (arts. 13 and 14) from what it keeps in Bizisy: the name, country, tax ID and, if it adds one, the address of its legal entities, its retention period, whether it uses referrals, and a contact email for privacy questions if it sets one (Bizisy never fills in anyone’s personal email; without one, the notice points candidates to their status page). Applications that did not lead to a hire are deleted when the period for the organization’s country has passed since the job closed (by default 6 months; 4 weeks in the Netherlands; the organization can shorten it, never beyond 24 months), and a hired person’s application the same time after the hire, when their employee record takes over.
If the organization switches Referrals on, an employee can share a job with a personal link (Bizisy counts how many people applied through it and shows the employee only that count) or refer someone by giving their name and email address, and why they would fit, after ticking that the person agreed to be contacted; Bizisy then emails that person an invitation to apply in the organization’s name. An invitation nobody answers is deleted after 6 months. The employee only ever learns where their referral stands in one word (applied, in the process, hired, not this time). If the organization pays a referral bonus, Bizisy records its amount and when it is earned (pay data: the employee and HR only, never API keys or AI apps); when it is earned, HR pays it, or, if the organization prepares payroll in Bizisy, it is added to the employee’s pay period as variable pay.
If the organization runs interviews in Bizisy, its HR keeps interview groups (named sets of employees and teams), and each employee who interviews says when they can usually do it: windows of a usual week, in their time zone, with a weekly limit and a pause. Bizisy uses that, the interviews already booked and, if the organization uses Time off, the days that person is away or a public holiday applies (dates only, never the reason) to list the times when interviewers are free. HR or the job’s hiring manager books a time or offers the candidate a few times to pick from on their status page (held for 48 hours). Bizisy then keeps the interview (the job’s step, the time, the place or video link HR set, who interviews, and any personal line the hiring team adds for the candidate, which only the candidate’s email and status page show, never the interviewers’) and emails the candidate and each interviewer an invitation with a calendar file (or, when the organization connected its Google or Outlook calendar for interviews, an email without the file while the invitation comes from that calendar, as described under Calendar invites, with any Google Meet or Teams link it made), any change or cancellation, and a reminder the day before; the candidate’s file names only them and they see the interviewers’ first names only; interviewers see the candidate’s name and get a notice in Bizisy. Bizisy counts each person’s interviews to suggest the least busy, and to keep within their weekly limit. An interview is deleted with the candidate’s application; when an interviewer is erased, their usual week is deleted, they leave the groups, and the interviews they took part in keep only a count. There is no connection to an interviewer’s own calendar: only the organization’s connected calendar sends invitations, to work email addresses.
Each interviewer sees the candidate they interview (name, CV, answers to the job’s questions, the job post and the step’s scorecard) from the booking until 30 days after the interview, never the pay expectation, notes, who referred them or other candidates. They give feedback in Bizisy: a rating from 1 to 4 for each skill on the scorecard, their words, an answer to its question and a recommendation. A draft is visible only to its author; once sent, HR and the job’s hiring manager read it, and the other interviewers of that candidate after sending their own. Bizisy emails an interviewer when their feedback is due and a day later. Feedback is deleted with the candidate’s application and is part of the candidate’s access request; when an interviewer is erased, the feedback they sent stays with the candidate without their name, and their drafts are deleted. Bizisy never scores, ranks or compares candidates. To show who helps the organization hire, Bizisy counts each employee’s interviews and their hours, feedback sent on time, hires they interviewed, referrals and shares and the applicants from them, against their weekly limit: HR sees everyone, a manager the people below them, each person their own; it never names candidates. HR can thank someone for helping hire for a job, once per job, with an in-app notice and an email (and a copy to their manager if HR chooses); the thanks is counted.
Hires from Teamtailor or Greenhouse
When the organization makes a candidate a job offer in Bizisy, it keeps the offer’s terms (the job, employer, start date, contract and end date, probation, hours, place of work, pay and benefits, the last day to accept and who signs for the company), every version of it, and, when the pay is above the published range or the organization asks for it, who approved it and their comment. Owners, admins and HR, and the job’s hiring manager, see offers; API keys and AI apps never see their pay and cannot make, approve or send one. Bizisy writes the offer letter as a PDF from the organization’s template (a document template like any other when the organization uses Documents) and keeps it; the candidate gets an email with a private link to their offer page (Bizisy stores only a hash of it; it works until 30 days after the offer ends), a reminder two days before it ends, and an email if it is withdrawn. On that page the candidate reads the letter, asks the hiring manager a question (sent by email, kept with the application), declines (with a reason in their words and one picked from a short list, if they wish: the hiring report counts the picked reasons, never the words) or accepts it by typing their full name and confirming: a simple electronic signature (Regulation (EU) No 910/2014, art. 25). For that signature Bizisy records the name typed, the time, a SHA-256 fingerprint of the letter, a keyed one-way hash of the network address the candidate used (never the address itself) and their browser’s name, and adds them on a last page of the signed PDF. Accepting then adds the candidate to People with the offer’s terms, as a hire by the organization’s HR, so the usual onboarding starts; from then the accepted offer and its signed PDF belong to that person’s employee record (in their documents, visible to HR, when the organization uses Documents) and are kept and deleted with it. Offers not accepted are candidate data: deleted with the application, and part of the candidate’s access request.
An organization can also let the people who work for it apply for its jobs from My workspace (internal jobs, off until its HR turns them on). Jobs can be open to all, for its people first, or for its people only; jobs for its people are never on the careers page, the job feed or job sites. A person who applies sends the answers to the job’s questions and, if they wish, a note on why they want the job and a CV (checked by its content, at most 10 MB, stored in the EU with their application); their name, work email and current job come from their employee record, and they are not asked about their pay. The organization uses this to consider them for the job (GDPR art. 6(1)(b) and (f)). HR and the job’s hiring team see the application with the person’s current job title, team, location and how long they have worked there; never their pay, private details, reviews or ratings. The person’s manager is told only when the organization’s rule says (when they apply, when they are invited to an interview — the default —, when they are offered the job, or when the move is agreed), earlier only if that manager is on the job’s hiring team or approves job changes; the form says which before the person sends it. From then the manager sees a one-word stage (applied, interviewing, offer, moved), never notes or feedback; Bizisy sends them one email and a notice in Bizisy. The person follows their applications in My workspace and gets emails at their work address; they can withdraw at any time, and a manager who was not yet told then never learns. An offer to someone who works there is accepted in My workspace and becomes a change of their job under the organization’s approval rules, kept with their employee record like any job change. Internal applications are kept and deleted like other applications (a withdrawn one after 30 days), are part of the person’s data export and are deleted when the person is erased.
An organization that recruits with Teamtailor or Greenhouse can connect it under Integrations with its own API key or API credentials, which Bizisy keeps encrypted. When a candidate is hired there (Bizisy asks Teamtailor every hour; Greenhouse tells Bizisy when an offer is accepted, signed with a secret Bizisy made for that connection), Bizisy receives and keeps, for the organization’s owners, admins and HR to review: the candidate’s first and last name, their own email address, the job title, the department, the start date and the tool’s identifiers of the application, the candidate and the opening. It ignores everything else the tool sends (such as pay, CVs, notes or answers). HR then adds the candidate as a new starter (their email address is kept on their record as a private detail, and onboarding starts as for anyone hired), links them to someone already in Bizisy, or dismisses them; if the organization chose it, a hire whose every detail matches is added at once. Bizisy never changes someone already in Bizisy from a tool. Once HR has decided, the candidate’s name, email and job details are deleted from the review list and only the tool’s identifiers and the outcome stay, so the same hire is never taken twice; hires nobody reviewed are deleted after 180 days. Teamtailor and Greenhouse are the organization’s own tools, under its agreements with them.
Training register
If an organization switches on Ask HR, its employees can ask questions in their workspace and have requests prepared for them. To answer, Bizisy reads, as that employee and only what they can see themselves, their own details, time off, shifts, training, document titles and the policies published to them, and sends the question with that information to a language model on Google Cloud Vertex AI in the European Union, which does not use it to train models. Ask HR never reads other employees’ data and never decides anything: a request it prepares is only sent when the employee confirms it, and is then decided as any other request. Conversations are visible only to the employee, are kept for 30 days and are included in their data download; the organization sees only how many questions were asked. Each answered question uses the organization’s AI credits, by the amount of text the model reads and writes; Ask HR shows about how many before a question is sent. When a question looks like it is about harassment, discrimination, whistleblowing, a health or wellbeing crisis, or safety, Ask HR does not send it to the language model and does not keep it in the conversation; it shows the organization’s confidential channels and emergency numbers instead. Only if the employee chooses “Hand to HR” and confirms is their text sent to the organization’s owners, admins and HR, who see it with the employee’s name; it is deleted after 90 days, or earlier when the employee withdraws it, and is included in their data download. Reports about breaches of law (whistleblowing) are never handed over this way: Ask HR points to the organization’s own whistleblowing channel.
If the organization turns on Ask HR memory and an employee chooses to use it, Ask HR keeps topics between conversations so the employee doesn’t have to repeat themselves: preferences (for example how they like answers), what they are planning, requests to prepare later, and which policy section answered an earlier question. Each topic has a title, a one-line summary and a short text that Ask HR keeps up to date, merging in what the employee tells it rather than adding new notes. Ask HR shows every change under its answer with Undo, and the employee can see, change, keep, pause and delete every topic in their workspace, or turn memory off at any time. Ask HR never keeps topics about health or other sensitive matters, identification or bank numbers, or other people, and keeps nothing from questions about such matters. Topics are visible only to the employee — not to the organization, HR, managers or Bizisy staff — and are never used to assess the employee. A topic is deleted 12 months after it last helped an answer (or after another period of 3 to 24 months the organization chooses; “Keep” gives it another period), a request for later 30 days after its date, and every topic when the employee leaves the organization or when the organization turns memory off. Topics are included in the employee’s data download and stored with Bizisy’s other data on Google Cloud in the European Union.
With memory on, Ask HR also learns from the organization’s HR team, never from employees’ private conversations. When Ask HR can’t answer a question, or its answer looks wrong, the employee can choose to hand the question to HR (with Ask HR’s answer, if they want); HR sees it with the employee’s name and can reply, and the employee sees the reply in Ask HR. It is deleted 90 days after it was sent, or earlier when the employee withdraws it. From HR’s reply, and only HR’s own words, Ask HR may draft a company topic (for example “Parking at the Lisbon office”): it is used for everyone only after HR approves it, is shown to employees as “From HR”, contains no personal data and never the name or words of whoever asked, is part of the organization’s data export, and is deleted after the organization’s period unless HR pins it. When the published policies don’t answer a question, Ask HR records only a short generic label of what was asked (for example “Bringing a dog to work”) and how many times; who asked is never recorded, and HR sees a label once at least three questions share it. Before answering, a smaller language model on Google Cloud Vertex AI in the European Union sorts each question (HR, another team of the organization, not about work, sensitive, or an attempt to misuse Ask HR) and keeps nothing: questions for the organization’s other teams get the contacts HR set, questions not about work get a polite no, and attempts to misuse Ask HR are refused and counted for HR without recording who.
With memory on, Ask HR can also follow the organization’s skills: step-by-step procedures (for example “Someone moving to the Porto office”) that HR writes, copies from Bizisy’s guides, or approves from drafts Ask HR makes of the organization’s company topics. Skills contain no personal data, never give anyone more rights than they already have, are shown to employees as “From HR”, can be downloaded, are part of the organization’s data export, and are deleted after the organization’s period unless HR pins them. The organization’s own AI apps connected to Bizisy can read the same skills, with each person’s own permissions.
When someone in the organization approves or declines time off or a shift swap, give-away or claim, Bizisy keeps a decision record: what was asked (for example the leave type, the number of days and how far ahead), the outcome, who decided, and an optional one-line reason about the case. Ask HR may suggest that reason from the comment the decider wrote; the decider can change or remove it. A reason never mentions health or other sensitive matters, identification or contact details, ratings or feelings, or anyone’s name, which Bizisy checks before keeping it. The employee the decision is about can see every record about them in their workspace and in their data download; the people who decide and the organization’s HR team see them too. Records are deleted after the organization’s period (12 months by default), and those about an employee when their data is erased. If the organization chooses, after informing or consulting its workers’ representatives as the law requires and after Bizisy compares past approvals by sex and age band (totals only, never anyone’s own), the people who decide can be shown how similar requests were decided before; and, where the organization also chooses, requests that meet every condition of a rule its HR team wrote (for example one day of vacation asked two weeks ahead) are approved at once. Such approvals are made by that fixed rule, never by an AI system; nothing is ever refused automatically, and hiring, promotion, termination, pay, performance, discipline and task allocation are never decided this way. Each automated approval is recorded with its rule; the employee can ask a person in HR to look at it again, and the organization can switch it off at any time.
An organization that switches Training on keeps a register of the training its people do, under Manage → Training. For each course we keep its title, provider, hours, whether it is internal or external, how long its certificates last, the official codes Portugal’s Relatório Único asks for (area, modality, provider type, level, certificate type) and the learning platform courses it matches. For each training record we keep the person, the course or the training’s title and provider, the dates and hours attended, whether it was in working hours, the result, whether it was student-worker hours or training the person chose under their training credit, when its certificate expires, the certificate file (PDF or picture, at most 10 MB, if one is added), where the record came from (HR, a spreadsheet import, a learning platform or the person’s own report), whether HR confirmed or declined it and, for a declined report, HR’s reason. Where the organization’s country sets a minimum of training hours (in Portugal, Código do Trabalho art. 131–134), Bizisy works out each person’s hours owed, given and still open, their training credit and when it lapses, from their employment dates and these records; nothing is stored for that. The organization’s owners, admins and HR see every record; a person sees their own (with their certificates, their hours and credit, and why HR declined a report) and can report training they did; a manager sees the records of the people who report to them, without certificates or decline reasons. Certificates and decline reasons are never given to API keys or AI apps. When a learning platform the organization connected reports that someone completed a course the organization matched to one of its courses (or a LinkedIn Learning course it assigned), Bizisy adds a record with that course’s hours. A certificate about to expire is listed in the reminders the organization chose (to HR and, if switched on, the person’s manager), naming the course. For a Portuguese legal entity, the Relatório Único’s Anexo C is made from the register; it holds each worker’s Segurança Social number and name, and is made in the app only. When someone has a last day set, HR (only) sees the training hours the law says are paid on termination. Erasing a person’s data deletes their training records and certificates; a person’s data download lists their training and their hours.
The organization can make courses mandatory: for everyone, or for people in some teams, job titles, work locations or legal entities, due within a number of days of starting or of joining the group, or by a date, and renewed when a certificate expires or every few months. We keep these rules. From them, people’s employment dates and team, title, location and legal entity, and the training records, Bizisy works out who must do which course by when and whether it is done, overdue or due soon; nothing is stored for that. HR can exempt a person from a rule with a reason: we keep the exemption, its reason, who made it and when, and when it ended, as the person’s history; only the organization’s owners, admins and HR see the reason, never managers, API keys or AI apps; the person gets it in their own data download. When HR or a manager presses Remind, Bizisy emails the person (and their manager) the course and its due date, at most once a day per person, and keeps when it last did and who sent it. A person sees the mandatory training required of them; a manager sees that of the people who report to them. Erasing a person’s data deletes their exemptions and reminders; a person’s data download lists their mandatory training and exemptions.
Benefits
An organization that switches Benefits on keeps a catalogue of the benefits it offers (such as a meal card, health insurance, childcare or transport), which of its legal entities offer each one, who is eligible, the amounts and, optionally, flexible budgets per legal entity and the periods when people may change their choices. For each person we keep the benefits they chose or switched off, the amount of each and the day it applies from (their choices); the benefits the organization gives everyone are worked out from the catalogue and not stored per person. To show which amounts are exempt from tax, Bizisy uses each country’s published limits, with their source; these are estimates, and the organization’s payroll provider applies the final tax. A person sees and changes their own choices in their workspace; the organization’s owners, admins and HR see everyone’s; managers do not see their team’s, and API keys and AI apps never see anyone’s choices. When the organization uses Payroll, each pay period lists the benefits with their amounts, split into the tax-exempt and taxable parts, for its payroll provider, and keeps them with the period when it is locked. Activity records that a choice changed, never what was chosen or the amounts. An offer letter can name benefits from the catalogue (written out with their amounts, as the rest of the offer’s terms); when the candidate accepts and is hired, the benefits they would choose are switched on for them from their first day, and they can change them while their new-joiner window is open. The careers page can list the catalogue’s benefit names, never amounts. Erasing a person’s data deletes their choices; a person’s data download lists them.
Career paths
An organization that uses Performance and talent can set career paths: which of its job titles lead to which, with how long people usually spend in a job first and a note. These describe jobs, not people. Each person sees, in My career, the paths from their own job title, the skills each step needs against the skills they hold, courses from the training register that teach the missing ones, and open jobs inside the organization. A person can say they are interested in a job a path leads to: we keep who, which job title, whether they chose to share it with their manager, and when. The organization’s owners, admins and HR see it; their manager (and the managers above) only if the person shared it; nobody else, and never API keys or AI apps. The person can remove it at any time. It is kept with the organization’s data until the person removes it, their data is erased (it is then deleted at once) or the organization closes its account; a person’s data download lists it.
Talent profiles and finding people inside the organization
An organization that uses Performance and talent can turn on talent profiles. Each person’s profile shows their jobs and teams in the organization and the courses in its training register (from its records), the skills they, their manager or HR recorded, and what the person or HR adds: a headline and a few words about the person, their education (qualification, school, level, field, and whether it is done or in progress), certificates and licences (with their number, if given), and experience before they joined. HR can add entries to anyone’s profile and mark an entry as verified. Owners, admins, HR and the person’s managers see the profile; certificate numbers are seen only by the person and by owners, admins and HR. Where the organization allows it, the person can choose “Show my profile to colleagues”; only then do colleagues see the profile, and they see the headline, location, jobs and teams, skills, course titles and years, education and certificates, never certificate numbers, the few words about the person or their experience before they joined. API keys and AI apps see the profile of the person they act for without certificate numbers, and other people’s profiles only as colleagues see them. The organization uses profiles to find people inside it for jobs and projects (GDPR art. 6(1)(f)); whether colleagues see a profile is the person’s choice, and they can change it at any time. For people in Portugal, a completed degree on the profile is used to suggest the education code HR declares in the Relatório Único; HR checks it before it is set. Profiles are kept while the person works there and deleted 90 days after their last day, or at once when their data is erased; a person’s data download includes their profile.
Salary reviews
An organization that switches Salary reviews on can run salary review cycles under Manage → Salary reviews. For a cycle we keep its name, who takes part (the whole company, teams or legal entities, and who was employed on the cut-off date), its dates, the guideline (a % range per rating and position in the pay band), the budget as a % of base pay (and, when the organization sets them, a separate promotion budget as a % and a budget for one-off lump sums as an amount per currency) and when its criteria were published to staff. When HR launches it, Bizisy keeps for each person taking part a snapshot of their pay on the effective date (base pay, the same per year, working time, their pay band, where their pay sits in it and their rating from a review cycle when the organization uses one), their manager’s proposal (the % raise and new pay, an optional one-off lump sum as a % of base pay and its amount, a reason chosen from a fixed list when it is outside the guideline, and an optional private note to HR), HR’s decisions (who and when) and, once released, the letter. When the organization also uses Time off, Bizisy notes whether a person had protected family leave (maternity, paternity, parental or adoption leave) in the 12 months before the new pay date, so that their raise is at least what they would have had at work, as EU equal-treatment law requires; it reads only that yes or no from Time off, never the kind of leave or its dates, and managers see at most “Protected leave”. If HR gives such a person less, HR records an objective reason, which HR sees and the person finds in their data download after the release. Managers propose in percentages: they see their own team’s rows only, never salaries (unless the organization chooses, for a review, to show managers their team’s pay: then also each person’s current and proposed base pay and lump sum and the budget in money, while the review is open, each time recorded in Activity), never their own row, and a rating only where they could already see it. When the organization turns on a check by the manager’s own manager, that manager also sees the worksheets of the team leads who report to them (their indirect reports’ rows, in percentages, never salaries), may change a proposal and sends the worksheet on to HR or back. The organization’s owners, admins and HR see every row except their own; each row is decided under the same rules as a pay change (an HR member’s pay only by owners and admins, an owner’s only by another owner, never by the person or whoever proposed it). When the organization adds a final sign-off, its owners, or its employees with a role with Pay at Approve over everyone in the review, see the review’s totals by team and currency against the budget (not each person’s pay; teams of fewer than 3 people are shown together) and sign it off or send it back to HR with a note; we keep who did it, when and the note. Nothing is written to anyone’s pay and the person is told nothing until the release date: then the new pay is recorded from its effective date like any pay change (with an approved request in Approvals), and the person gets their letter in My workspace → Pay. A one-off lump sum becomes a “Salary review lump sum” item in Payroll for the pay period of the effective date; without Payroll, HR pays it by hand and records when it was marked paid. When the organization uses Documents, the letter is also made as a PDF among the person’s documents (from Bizisy’s “Pay review letter” template, or the organization’s own copy of it), visible to HR only until it is sent to the person a few minutes after the release, without an email of its own; that copy is kept and deleted like the person’s other documents. API keys and AI apps see a cycle’s name, dates and stage only, never pay, proposals or letters. A person’s data download lists their released letters and lump sums, and a review still open only as “in an open salary review”, without the proposal. Erasing a person’s data deletes their rows and letters (the pay already recorded follows the pay record). Rows and letters are deleted 3 years after the cycle’s release (evidence for equal-pay questions and requests about pay levels).
Bonus plans
An organization that switches Salary reviews on can also run bonus plans under Manage → Bonus plans. For a plan we keep its name, the performance period, the payout day, who takes part, the formula (a target as a % of base pay, also per job title, a company factor, a % for each rating level and for no rating, the share that comes from goals, a maximum, and whether unpaid leave reduces the share of the period) and when the formula was published to staff. Published formulas show as percentages, never amounts, to everyone at the organization in My workspace → Pay. When HR launches a plan, Bizisy keeps for each person taking part what the formula used: their annual base pay on the plan’s day, job title, working time, their final rating from a review cycle when the organization uses one, the average progress of their goals that HR marked as committed when the plan gives goals a share, the days they were employed in the period, the days of unpaid leave when the plan doesn’t count it as time worked, and whether they had protected family leave in the period (from Time off, a yes or no only: such leave always counts as time worked); then the amount the formula gives, any change by their manager (as a % of the formula, within the plan’s range, with a reason from a fixed list and an optional note to HR) or by HR (an amount or a different target, with a reason), and HR’s approvals (who and when). Managers see their own reports’ awards as a % of the formula only, never amounts or pay, and never their own. Before approving, the organization’s owners, admins and HR see the average award and the average award against target of women and of men in each category of workers, only for groups large enough that nobody can be singled out. Each award is approved under the same rules as a pay change. Nobody is told their award before the payout day: then each person gets a letter in My workspace → Pay (the amount and how the formula worked it out, never their base pay) and an email without amounts; the bonus becomes a “Bonus” item in Payroll for the pay period of the payout day, or, without Payroll, HR pays it by hand and records when it was marked paid. API keys and AI apps see a plan’s name, dates and status only. A person’s data download lists their released awards (amount and the formula’s inputs), and an open plan only as “in an open bonus plan”. Erasing a person’s data deletes their awards and letters. Awards and letters are deleted 3 years after the plan’s release.
Talent insights
An organization can switch on Talent insights. Bizisy then works out, for each employee, a band (low, elevated or high) that suggests a conversation may help keep them, from job data only: time in the company and since their last change of role or pay (never amounts), manager changes, counts of short-notice absences of the leave types the organization chose (never sick, health-related, parental or family leave), gaps in clocked time, overtime and shift patterns, review and goal progress, open or declined pay or role requests and the end date of a fixed-term contract. It never uses age, sex, nationality, health, family situation, address, free text or location. Bizisy can also suggest skills from a person’s position and certificates, which HR or a manager accepts or rejects; skills from completed training are added from the training record. Only people the organization chose (by default owners, admins and HR) see bands; the employee does not see their band in the app, but it is included when they download their data, and they can object or ask for an explanation in their workspace. Nothing is decided automatically. Before an organization switches it on, and every three months after, Bizisy tests it on the organization’s own past: for people who chose to leave in the last two years, the band it would have given 90 days before they left, compared with people who stayed, also split by sex and age band where the organization records them. This runs in memory; Bizisy keeps only the totals, for groups of at least 10 people, and the organization’s acknowledgement of them. Bizisy keeps a record of every band worked out, who looked at it and what they did, for 12 months. The organization is the controller and Bizisy its processor; Bizisy is the provider of this AI system under the EU AI Act.
Equipment and device management tools
An organization can keep a register of the equipment it hands to people (such as laptops, phones, monitors, badges and cars) under Manage → Equipment. For each item we keep its type, name, model, serial number, the organization’s own asset tag, its value and purchase date, its status (in stock, assigned, in repair, retired), notes, who holds it since when, when the holder confirmed they received it, and the dated history of who had it and how it came back. Who holds an item is seen by the organization’s owners, admins and HR, by the person themself (in My equipment, where they confirm they received it) and by their managers; the value, purchase date, asset tag and notes are seen by owners, admins and HR only. When someone leaves, the offboarding task “Collect equipment” lists what they still hold and ticks itself once everything is returned. An organization’s owners and admins can connect its own device management tool (Jamf Pro, Microsoft Intune or Kandji) or its equipment-as-a-service provider (Workwize): Bizisy then reads, every hour and read only, the organization’s devices from that tool (name, model, serial number, operating system, whether it is managed, when it last checked in, and the name and email of the user the tool lists) and matches them to people by work email, to add or update them in the register; it never locks, wipes or changes a device. From Microsoft Intune, devices the tool marks as personally owned are never read. The tool’s user name and email are kept with the device for owners, admins and HR only, so they can review devices whose user doesn’t match the register. For Jamf Pro on the organization’s own server, Bizisy calls only that server’s public address. Each tool is the organization’s own, chosen and controlled by it, under its agreement with that provider. Erasing a person’s data releases what they hold, removes them from the items’ history and clears their email from synced devices; a person’s data download lists the equipment they hold and held. Disconnecting a tool stops the reading; the devices already in the register stay as the organization’s records.
Time off
Where Bizisy offers time off to an organization, it keeps the days people book or request (dates, whole or half days or some hours of a day with how long and, if given, from when, the leave type, the status, who decided and when, a decline comment, and a note), each person’s balance (allowance, carried days, adjustments HR made with their reason) and the organization’s settings: leave types, allowance policies per location (pre-filled from each country’s legal minimum), working weeks, public holidays per country and region (from the open-source date-holidays data, kept in Bizisy), company days off and booking rules. Colleagues see only that someone is away (dates, half days, or “part of the day”, never how long or when), never the type or note, and the organization can hide even that; managers see their people’s requests and the type, except sick leave and any type the organization marks as health-related; notes and health-related leave are seen only by the person and HR. Sick leave is health data (GDPR art. 9): it is recorded by HR, shown as “Away” to everyone else, and never sent to API keys, AI connections, calendars, chat tools or webhooks, which only ever receive “Away” with dates. When HR records sick leave over leave already booked, those days go back to the person’s balance (sickness during annual leave, as EU law and each country’s rule require); the booking keeps a note of the days and the rule, which only the person and HR see. Payroll preparation (owners, admins and HR) lists each pay period’s approved absences with their type and leavers’ untaken days, so the payroll can apply sick pay and pay out leave. Bizisy emails approvers about requests (and reminds them after two working days), tells people about decisions and about time off HR recorded for them, and reminds people of untaken leave before it lapses; these emails are stored with ids only and written when sent. People can create private calendar links (ICS) that show “Away” only; only a fingerprint of each link is kept, and it stops working when revoked or when the person’s access ends. Optionally the organization puts “Away” out-of-office events in people’s Google or Outlook calendars and posts who is away today (names only) to its Slack or Teams channel. Time off records are part of the person’s data export and are erased with them.
Time off also keeps the organization’s work schedules (fixed hours, flexible hours with core hours, or rotating weekly patterns) and who follows which one from which date, with that history; they decide which days count as working days and how many hours a day is expected. Everyone in the organization can see a workplace’s work calendar (working days, hours, public holidays and company days), as the law asks some employers to display it.
Performance and talent
Performance and talent: review answers and ratings, feedback from colleagues (shown to the person only as a group of at least three, never with names), goals and their progress, potential assessments, calibration records, succession plans and skills. Kept for as long as the company sets, by default 5 years after a review cycle closes, and deleted when the person’s record is erased. Bizisy sends emails when a review cycle starts, when feedback is requested and when a review is ready to read; these emails contain no ratings or answers. If someone asks Bizisy to suggest measures for a goal, only the goal’s title and description are sent to a language model on Google Cloud Vertex AI in the European Union, which does not use it to train models; never ratings, reviews or anything about how a person performs. The suggestions are shown only to them, and nothing is saved until they accept one.
Surveys
An organization that switches Surveys on can send its employees surveys and forms: questions it writes (with choices, scales, text, dates, a location or, in named surveys, a colleague), sent to everyone or to teams, locations, legal entities or saved groups. Each survey is named (answers are shown with the person’s name to the organization’s owners, admins and HR, for example a sign-up or a menu choice), anonymous or confidential (the default). In a confidential survey Bizisy knows who answered, to send reminders and to count answers by group as of the day the survey opened (team, legal entity, location, manager line, time in the company, and the custom fields the organization marked for people analytics, never private ones), but nobody at the organization, owners included, ever sees one person’s answers, and no result, export, API or AI answer shows a group with fewer answers than the survey’s threshold (5 by default, never fewer than 3; comments need 10 by default, and names, email addresses and phone numbers in comments are masked), nor a group that could be worked out by subtracting other groups from a larger one. Results of a confidential survey change only in steps of that threshold, never with a single answer, and answering one leaves no entry in the organization’s Activity: the organization sees how many people answered, never who or when. In an anonymous survey nothing links an answer to a person, not even for Bizisy: when someone opens it, their device gets a one-time code; Bizisy keeps only a fingerprint of that code, the survey and the groups the organization chose to keep (at most the person’s top-level team, location and time in the company), records only that a code was given out, and stores answers with the day, not the time. Nobody knows who answered, so reminders go to everyone, answers can’t be moved to another device, and they can’t be found to erase or include in a person’s data download. If the organization turns on the manager view, a manager sees the results of everyone they manage, only above the threshold and never a smaller group within it that could be worked out. A survey can repeat (every week to every year); each round is kept as its own survey, and results compare rounds. To avoid too many surveys, the organization can set how many surveys a person gets a month; people over it are left out unless the organization sends to them anyway. Each survey says which kind it is before the first question, and answering is up to the person. To show questions that use the person’s name, team or location, Bizisy reads them from their profile; nothing new is stored for that. Answers saved to finish later are kept for 30 days after the last change and never counted in results; sent answers are kept until the retention period below ends, or sooner if the organization deletes the survey, erases the person’s data or closes its account. When a survey is sent, and for up to two reminders while the person hasn’t answered, they get an in-app notice, a push notification if they turned them on, and an email with the survey’s title (an optional email the organization can turn off in Settings → Notifications; held outside working time as below). Results by group, and for named surveys each answer, can be exported (CSV, Excel) and delivered to the organization’s data tools; confidential surveys only ever leave as group results above the threshold. Webhooks only say that a survey opened or closed. Erasing a person’s data deletes their answers and invitations; a person’s own data download includes their answers, confidential ones too, while an export made by the organization about a person says only that a confidential survey was sent to them.
If an organization switches on AI for surveys (off by default), its owners, admins and HR can have survey questions and translations drafted, the wording of questions checked, comments grouped into themes and questions about results answered. Bizisy sends a language model on Google Cloud Vertex AI in the European Union, which does not use it to train models, only what that feature needs: the description HR wrote, the survey’s own questions, the results the results screen already shows (never one person’s answers, never a group below the threshold) and, for themes, the text of comments of a confidential or anonymous survey only once enough people have written one (the comment threshold), with names, email addresses and phone numbers masked before sending. Themes are stored with the survey, made only from those comments, and change only in steps, never with a single answer. HR, or a manager in their own team’s results, can reply to a comment; its author reads the reply in My workspace and can answer without being identified: nobody, Bizisy included, shows the organization who wrote it, no notification or email is sent for it (so that none names the author), the author’s answers leave no entry in the organization’s Activity, and in an anonymous survey replies show only on the device that answered (its one-time code), with answers dated by the day. AI requests use the organization’s AI credits.
An organization can also send a survey to each person at a moment of their working life instead of to everyone at once: some days after their first day, before their last day (only once they have been told it, and while they can still sign in: Bizisy has no personal email for after they leave), after a change of team, location, title or manager, or after they come back from a leave of 28 days or more (Bizisy reads only that, and when, from time off, never the kind of leave). These surveys go to each person once and don’t count toward the monthly limit. At the time clock kiosk, after someone clocks in or out with their PIN, the kiosk can show their open named or confidential surveys (never anonymous ones) to answer there, with a session tied to that person and that kiosk that ends when they tap Done, after a minute without a touch, or when someone else types a PIN; answering there leaves no entry in the organization’s Activity. Where the organization connected Slack, it can have survey invitations and reminders sent as Slack direct messages from Bizisy’s app: Slack receives the person’s work email to find them and the survey’s title and link, never answers, and the message waits outside working time like the email. A survey’s results can be read in Google Sheets through a link the organization makes and can stop at any time: it serves only the group results the results page shows, never one person’s answers, even in a named survey. Exports can also be SPSS files and JSON, under the same rules as the other exports. Webhooks can say that someone answered a named survey (ids only, never the answers) and, when a survey closes, its group results as the results page shows them. Actions an organization plans from results (what to do, who, by when, for which group) are seen by their owner on their Home, with the same group results only.
An organization can also give a one-off anonymous or named survey a public link on its own address (…/f/…), so that people answer without signing in: candidates, customers, event guests, or employees without a login. For those answers the organization is the controller: every public form shows the organization’s name, links its privacy notice and ours, says whether answers are anonymous, and has a “Report this form” link to us. Public answers are anonymous unless the survey asks people to give their name (and, if they like, an email), which is kept with their answers as typed, not checked. Bizisy keeps nothing else about who answers: no account, no cookie and no IP address. To stop abuse it keeps a keyed fingerprint of the visitor’s network (never the address itself) to count requests, for about a day; and, with each answer, a keyed fingerprint of a random code the browser keeps in its own storage (so the form is answered once per browser) and of a short calculation the browser does before sending (instead of a third-party captcha), deleted with the answer. Public forms can’t ask for passwords, card numbers or bank details. When someone reports a form, we keep the reason, the optional note and a keyed fingerprint of their network (never who they are) to review it, and we can switch the form off. Public answers follow the survey’s retention below, are shown as their own group (“Public link”) in results, and never use the organization’s people data.
An organization can give its works council (or other employee representatives) a login with a role that reads surveys: for each survey, a pack saying what it asks, who sees what, the thresholds, how long answers are kept and where the data goes, and its results by group under the same rules as HR, never one person’s answers (in a named survey, counts and averages only, no comments). If the organization asks for it, a survey waits for a council member to approve it before it is sent; who approved it or sent it back, when and their comment are kept with the survey and shown to HR, who gets an email. Each survey’s answers, invitations and replies to comments are deleted some time after it closes (24 months unless the organization chooses between 6 months and 10 years); its group results, as the results page showed them, are kept to compare rounds.
Shift rotas
An organization that switches Shifts on plans who works when: rotas for a location or a team, made of shifts (a day, a start and end time, a break, the person or none for an open shift, a position such as “Till”, and an optional note about the work, which must not hold health or personal reasons). The organization also keeps its positions, which positions each person can work, shift templates and saved weeks. A rota is planned as a draft, seen only by the people who plan it (by default the team’s leads, and owners, admins and HR); people see their shifts only once it is published. To check a rota against the working-time rules of the person’s country (rest between shifts, weekly rest, the longest day, the 48-hour week, breaks), Bizisy reads the person’s work schedule, approved time off (as “away”, never its type) and public holidays; nothing new is stored for that. Each publish keeps a version: who published it and when, the shifts, what changed, the warnings the planner confirmed and, for changes made inside the notice period the law sets or below a rest rule, the reason they recorded (one of a short list, or their own words); this is the record of who works each shift that the law asks for. People can say when they can’t work (weekly times or dated days, with an optional private note) and ask to swap, give away or claim a shift (with an optional private message); the planners see the times, never the notes, and decide the requests. Each person sees their own published shifts and who else works that day (names only), and can subscribe a private calendar link to their published shifts; owners, admins and HR see everything, and a person’s managers see the published rotas they are on. API keys and AI apps can read rotas and prepare drafts, but never publish them, approve requests, or see availability notes, request messages or a reason written in someone’s own words. When a week is published or changed, a swap is offered to someone or a request is decided, the people concerned get an in-app notice, a push notification if they turned them on, and an email with the rota’s name and their own times that week (an optional email the organization can turn off in Settings → Notifications, and each person in My shifts; at most one per rota every 15 minutes and three a day per active person). Approved leave over a planned shift and a leaver’s shifts after their last day (once it was announced) become open shifts in the draft. In Portugal, Bizisy prints the mapa de horário de trabalho from the published rota with the details the organization fills in (employer, activity, addresses, rest days, collective agreement). Webhooks only say that a week was published or a request approved (identifiers and the week). Erasing a person’s data deletes their availability, positions, requests and calendar links, and removes them from every shift and version, which keep their times; a person’s data download includes their shifts, availability with notes, requests with messages and calendar links.
Time clock
Where Bizisy offers the time clock and an organization switches it on, people record their working time: when they clock in and out and start and end a break, whether they work on site or remotely when they say so, and how each clocking was made (the app, the phone, a shared kiosk, a door terminal, a clocking sent later by a phone that was offline, a correction, or an import of records from the organization’s previous time-and-attendance system). Imported records are checked day by day like a correction, never merged into days Bizisy already holds, kept with who imported them and when, and shown as imported in the records, the month summary and the exports. Bizisy keeps each clocking with the time it happened and the time it reached Bizisy; nothing is overwritten: a late or wrong clocking is corrected with a reason, and the correction keeps the day before and after, who asked, who decided and when, and, where the person disagreed with a correction made by their manager or HR, their comment. Totals (worked, breaks, expected hours from the work schedule, overtime, night and holiday hours) and notes such as a missing clock-out or a short rest are worked out from these records; time off shows there only as “time off”, never its type. From the same records Bizisy also works out, when they are read, warnings about the legal working-time limits of the person’s country (the 48-hour average week, the weekly rest and the yearly overtime cap, with the law): they are shown to the same people who see the records, never stored or sent elsewhere, and never block clocking. HR can close a month: the month’s summary is kept with a fingerprint (SHA-256) and, where the organization asks for it, the person’s acknowledgement (when, and with which login). The person sees their own records, their managers see their reports’, and owners, admins and HR see everyone’s; HR (and an accountant the organization gave payroll access) can export them for a labour inspection or for payroll. API keys and AI apps see other people’s records only when an owner, admin or HR member allowed that connection to receive private data, and never locations. Webhooks only say that someone clocked or that a correction or a month close happened (ids), never times or places.
Overtime approval is off unless the organization turns it on. Then overtime is asked for before it’s worked: Bizisy keeps each request with the person it is for, the day, the hours, the reason, who asked and when, each approval step with who decided, when and their comment, and, when it is asked, a warning if it would take the person’s overtime this year near or over their country’s yearly limit (worked out from the same records). Hours worked beyond plan without approval are worked out when the records are read, never stored, and wait for a manager or HR to approve them or say, with a reason, that they aren’t overtime; until then that month can’t be closed, and payroll and the payroll export count only approved overtime. The person sees the requests about them and is told in the app when one is decided; their managers see their reports’, and owners, admins and HR everyone’s. Requests are kept, exported, erased and deleted with the person’s time clock records. Webhooks only say that overtime was approved, declined or withdrawn (ids, the day and the outcome), never the hours or the reason.
Location is off unless the organization turns it on, and the clock button says so before the browser asks for permission. It is taken only at the moment of clocking, from the person’s own phone or computer, never continuously and never at a shared kiosk. In “record” mode Bizisy keeps the position rounded to about 100 metres with its accuracy, seen only by HR; in “workplace” mode it keeps only whether the person was inside one of the workplaces the organization set (and which), not the position. Refusing location is recorded as such.
At a shared kiosk (a tablet the organization sets up), people pick their name and type a 6-digit PIN they chose themselves; Bizisy keeps only a salted hash of the PIN, never the digits, and counts wrong PINs for a short time to lock out guessing. The tablet keeps a device key, of which Bizisy stores only a fingerprint; HR can revoke it at any time.
At a door terminal the organization connects (a ZKTeco terminal, or another brand through the organization’s own software), Bizisy receives only the badge number or terminal user id, the time and, where the terminal has keys for it, whether it was in, out or a break. Fingerprints, faces, photos and the terminal’s user list stay on the terminal: Bizisy never asks for them, and anything else a terminal sends is discarded unread. Terminal punches are processed like other clock records. The organization maps each badge number to a person (seen only by owners, admins and HR). Punches with a badge nobody has yet, or that a rule held back, wait for HR to match or dismiss them and are deleted after 92 days. For each terminal Bizisy keeps its name, place, serial number, the internet addresses it may call from, when it last called and from which internet address (and the one before, to warn HR when it changes). Its server address works like a password: Bizisy stores only a fingerprint of it, and HR can replace or revoke it at any time. Punches sent through the organization’s own software more than 15 minutes after they happened, and punches of an unknown badge that HR later attributes to a person, are treated as the organization’s change to the person’s record: where the organization asks people to confirm such changes, they wait for the person’s confirmation, as corrections do.
Bizisy reminds people in the app (and by push, if they turned it on) when they seem to have forgotten to clock out, when a correction waits for them and when their month is ready to acknowledge. These notices hold ids only. Time records are part of the person’s data export and are erased with them.
Push notifications
People can turn on push notifications for a browser or for My workspace installed on their phone, and choose which kinds they get (approvals and decisions, time clock reminders, documents, reminders). Bizisy keeps, per device, the address the browser’s push service gave it, the keys to encrypt messages for it, a label such as “Chrome on Android”, and when it was added and last used; it never shows the address to anyone. Each message is encrypted for that device and carries no names or details, only the kind of notice and the page to open; it travels through the push service of the person’s browser or phone (Google, Mozilla, Apple or Microsoft), which the person’s device chose and which cannot read it. A device is removed when the person turns it off, signs out, or the push service says it no longer exists, and with the person’s data when they are erased; messages waiting to be sent are deleted a day after they were due.
Right to disconnect
Where the organization’s policy or the law of the person’s country asks for it, Bizisy holds non-urgent emails and push notifications to an employee while they are outside their working time and sends them at the start of their next working period. To work that out it reads the person’s work schedule, published shifts, approved time off (as “away”, never its type), public holidays and their location’s time zone; nothing new is stored about the person. A held push waits in Bizisy’s queue and is deleted a day after it was due. A few work emails (about an interview, an offer or a document template) keep their content in Bizisy’s email queue while held, and it is removed when the email is sent. Sign-in and security notices, billing notices, decisions on the person’s own requests and urgent announcements (marked by the organization, with a reason it records) are never held.
Webhooks
An organization’s owners and admins can register web addresses of their own systems (webhook endpoints) to be told when something changes in Bizisy, for example a hire, a job change, a leaver, a new team, a new login, an open position, a change request approved or rejected, a checklist that started or a document added. Each notice contains identifiers, the type and time of the change and, for a person, their public and job details as an HR API key sees them (such as name, work email and phone, pronouns, job title, team, manager, location and contract terms); for an open position, its title, team, location, who it reports to and its contract terms, never its budget or notes, and nothing while it is a draft. Notices about change requests and checklists carry only identifiers, the kind and dates, never the change proposed; a change request is notified only once it is approved or rejected, never while it waits or when it is withdrawn, and pay change requests send none; notices about documents carry only identifiers, never a document’s title, file name, category or contents. A notice never contains private details (personal contact details, address, birthday, emergency contacts, payroll identifiers) or pay. The organization chooses where notices go; once received, that data is in the organization’s own systems, under its responsibility.
Only owners and admins signed in to Bizisy can add an endpoint or change its address, and every owner and admin is emailed each time, with who did it. For each endpoint we keep its address, a description, the events chosen, its health, who added it and a signing secret, stored encrypted. For each notice we keep identifiers only (its type and time, the identifiers of the people or records it is about, and the endpoint) and the outcome of each attempt (the answer’s status code, duration and the first 1 KB of the answer the organization’s system sent back), for 30 days. Names and other details are filled in when each notice is sent and are not kept with it. When a former employee’s data is erased, every stored answer of the organization’s systems is cleared at once. Bizisy only sends notices to public internet addresses over HTTPS.
API keys
For each API key: its name, who created it, what it may access, its last four characters and when it was created and last used. The key itself is shown once and stored only as a hash.
Accounting tools
An organization can connect its own accounting tool (Xero, Exact Online, Holded, Odoo or Moloni ON). Bizisy then keeps the tool in step with the organization’s structure: it sends the names of its teams (as tracking options, cost centres, analytic accounts or line tags) and, for each company in the tool, which legal entity it is; it reads the tool’s companies, accounts and journals so that HR can choose where costs go, and keeps that list. Only when an owner or admin switches it on, Bizisy also creates a supplier or contact for each person working for the matched legal entity, with their name and work email only, so the tool can reimburse their expenses. Bizisy sends pay only in a monthly headcount-cost journal, and only after an owner, admin or HR allowed pay to be sent to that tool in Payroll: Bizisy totals the month’s pay per team (never per person; teams of fewer than three people, and people without a team, share one line, so no line shows one person’s pay), shows HR the preview, and sends it only after HR approves it, as a draft where the tool has drafts (Xero, Odoo), as an open entry the accountant can delete (Exact Online), or as a booked entry (Holded, which has no drafts). Bizisy keeps each journal it prepared (the month, the totals per team and the number of people in each, the accounts, who approved it and where it was sent); journals are shown only to owners, admins and HR and never to API keys or connected AI apps. A journal prepared while one account of the tool was connected is never sent to another account connected later. Suppliers and journals Bizisy created in the tool stay there under the organization’s control after it disconnects or a person’s data is erased in Bizisy; Bizisy then forgets its link to them. For Odoo, Bizisy connects to the organization’s own Odoo address with the database, user email and API key it was given (kept encrypted).
AI apps you connect
When someone connects an AI app (such as Claude, ChatGPT, Cursor or VS Code) by signing in to Bizisy and pressing Allow, we keep a record of that connection: who connected it, the organization, the app’s name as the app gives it, where it comes from and where it sends you back to (web addresses, or that it is an app on your computer), whether it may use Manage or the person’s own workspace, and when it was connected, last used and disconnected. The tokens the app uses are stored only as hashes. A connected app works as the person who connected it, with their role’s permissions and the same limits as an API key: it never receives other people’s private details or pay. Apps that register themselves with Bizisy leave a record of their name and the addresses they asked to be sent back to. When an app identifies itself with a public metadata address (as Claude and ChatGPT can), Bizisy reads that document from the app’s own server; it holds the app’s name and addresses, not personal data. Owners and admins see every app connected in their organization and can disconnect any of them.
To show you, while you set an app up, that it is working, we also record on each connection when the app first used Bizisy, when it first made a change, and the last kind of action it used (for example “List people”), never what it read. The setup page remembers, for each person, when they first saw it, which apps they chose, whether they chose to do it later, and which of its steps have already been counted. To learn how many organizations complete the setup, we keep daily counters per organization: for each day, how many times each step happened (page seen, app chosen, connected, first use, first change, done later), with the app’s general kind (such as Claude or Cursor). Each person and each connection is counted once per step. The counters hold no name, email, user, login or connection identifier and no time other than the day; they are deleted about 13 months after their day.
Activity records
Every change saved in Bizisy leaves an activity record for the organization: which action, when, through which channel (app, API or AI assistant), an internal identifier of who made it (not their name) and a short summary that does not name anyone. For actions on people’s personal data (hiring, profile changes, terminations, imports and the like) the record keeps only which fields were sent, never their values. Other actions keep what was sent, with secrets such as passwords and tokens removed; for example, the record of a company’s sign-up keeps the company name and the owner’s name and email address.
Change history
When a change is saved to an organization’s records (a profile, a job, pay, a document’s details, a team, a setting and the like), Bizisy also keeps what changed: for each record, the values before and after, tied to its activity record. Previews and failed attempts keep nothing. Each value is seen only by the people allowed to see that information in Bizisy: pay and private details only by the person and the organization’s owners, admins and HR, in the app; API keys and AI assistants never receive other people’s private or pay values. A person sees, in My history, the changes to their own profile, job, pay, documents and requests about pay levels, and who made them, but never what HR keeps to itself (such as HR’s notes and approval requests). It also records who has which access: each login’s role, custom role, status and end date (never its email or sign-in details) and each custom role’s definition, seen by owners, admins and HR in the app; a person sees their own login’s changes in My history. A custom role sees the values of the records it can read in Bizisy (for example HR’s note on pay, with Pay at View), never over API keys or AI assistants. Passwords, tokens and keys are never kept. The change history about a person is kept while their record exists and is deleted when their data is erased; the rest is deleted with the organization.
Billing
Bizisy has a Free plan and one price per active person, with every module included: billing starts on 4 November 2026, and we email each organization’s owners and admins at least 30 days before its billing start date. The plan adds no personal data: we keep the modules an organization has switched on, when they were last changed and which owner or admin changed them, and for each month the number of active people, to bill that month. For emails and AI credits we keep a ledger per organization: each month’s included amount, each pack bought or refunded, and each use with its kind (such as “reading a CV”) and when. It holds no names, no document contents and nothing that says whose CV or which person’s bank proof it was; it is kept for 400 days, is included in the company export and is deleted when the organization is deleted. The plan and these monthly records are company data: only owners, admins and HR see them, they are included in the company export, and they are deleted when the organization is deleted. To pay, an organization’s owners and admins enter billing details: the company’s legal name, tax number (NIF or VAT number), billing email and address. We keep them with the organization, together with the number of active people we bill for, the storage limit owners and admins chose (its highest each month), the packs of emails and AI credits bought, the subscription status and whether invoices are paid by card or by invoice, each invoice with its due date, the reminders sent and its certified invoice and receipt numbers, the credit note (nota de crédito) Moloni issues for any refund, credit or cancelled invoice, and, while an invoice is overdue, that the account is paused and since when. Payments are made through Stripe: card details go straight to Stripe and Bizisy never sees or stores card numbers; we keep only the card brand, its last four digits and its expiry date to show them to owners and admins. Certified invoices (faturas) are issued through Moloni with the billing details. An EU VAT number outside Portugal is checked with the European Commission’s VIES service, and we keep the result and VIES’s reference as evidence. Billing details are company data, not part of anyone’s HR record, and only owners and admins see them. Billing emails go to the organization’s owners and admins.
Closing a company
An owner can close the organization’s Bizisy account in Settings → Close account, after confirming the company name and a recent sign-in. From that moment nobody can sign in, sessions end, API keys, connected AI apps and invites stop working, and webhook endpoints are turned off. For 14 days the data is kept unchanged so that an owner can reopen the company with the link we email to its owners; an owner who lost that email can sign in on the company’s page to get a new reopen link, and every owner gets a reminder 3 days before the deletion. After those 14 days everything else is deleted for good: people, jobs, pay, documents and their files, open positions, approval requests, changes prepared for review, custom fields, profile photos, the company logo and the careers page’s cover photo, teams and locations, reminder and approval settings, reminder records, checklists and checklist templates, logins (and the sign-in accounts of people who belong to no other organization), API keys, connected AI apps and the apps registered with it, the marketplace apps it installed (the developer organization linked to it is unlinked and stays with its developers), the AI setup counters, invites, webhook endpoints and their delivery records, email delivery records, in-app notifications and their settings, optional email counts, activity records, the change history, connections to other tools with their links and logs, and headcount-cost journals.
What remains, and for how long:
- The billing records the law requires: the company’s legal name, tax number, address and amounts, with each invoice, certified invoice and credit note, for 10 years (Portuguese tax law). The billing email is erased from them.
- A minimal record that the organization existed: its internal identifier, its address and the closing and deletion dates, plus the billing references needed to match late payment notifications (the Stripe and Moloni customer identifiers and the subscription’s identifier and status). The address (such as acme.bizisy.com) stays reserved for 90 days so that nobody else can take it straight away; after that it is released.
- Stripe keeps the customer record (legal name, billing email, address, VAT number and the saved payment method) and Moloni keeps the customer record used on the certified invoices, under their own legal duties, for as long as those invoices must be kept.
- Resend keeps its own delivery logs of the emails we sent (recipient, subject and content) for the retention period its terms set.
- The final deletion notice to the owners is recorded like any email (recipient and company name) and deleted after 60 days.
- Database backups: point-in-time recovery data for 7 days; we have no other backups, so deleted data is gone from them within 7 days.
Email delivery records
For each email Bizisy sends (welcome, invite, password reset, email confirmation, role change, access removed, payroll details changed, HR reminders, approval requests, checklist tasks, the yearly reminder of the right to ask about pay levels (only in organizations that set up pay equity); to owners, admins and HR: a person added a document of their own; to a person: HR shared a document with them, HR sent them their written statement of working conditions or a change notice to confirm, and a document waits for their signature in Bizisy (click-to-accept or Autenticação.gov); in organizations that run salary reviews: to a manager, their proposals are due or their worksheet was sent back, to a manager’s own manager, a worksheet from their team to check (when the organization uses that check), to those who sign a review off, that it waits for their sign-off, and to a person, their salary review letter is in Bizisy; in organizations that run bonus plans: to a manager, that they may adjust their team’s awards until the payout day, and to a person, their bonus letter is in Bizisy (these emails hold the organization’s and the review’s or plan’s names and dates, never an amount, a % or anyone’s name); in organizations that require approval to open positions: to each approver, a position waits for them, and to whoever asked, it was approved or not (with the comment); in organizations that make training mandatory: when HR or a manager presses Remind, to the person and their manager, the course and the date it is due by (the manager’s email names the person); to owners and admins: billing start notice, a warning when the organization reaches 8 and again at 9 active people (above 9, Core is charged), warnings when the month’s emails or AI credits or the storage are running out, the monthly invoice and its reminders, failed payment, payment confirmation needed, missing billing details, the account paused and unpaused for an unpaid invoice, warnings before it is closed for one, and subscription ended; and to owners: the closure confirmation with the reopen link, a new reopen link when an owner asks for one, a reminder 3 days before the deletion, the final deletion notice, and to owners and admins of a closed company a link to pay an invoice still due; to owners and admins, a notice that a webhook endpoint was added, now sends to another address, or was turned off after a day of failed deliveries; and to developers: the link to confirm their email, a password reset link, an invitation to join a developer organization, a warning that their unused sandbox will close, and Bizisy’s review decision on an app they submitted with its reason, or that the app was suspended or reinstated; to people of partner firms: the link to confirm their email, a password reset link, the receipt of their firm’s application and our decision with its reason, an invitation to join a firm, a company’s approval of the firm’s access, the end of that access, and the monthly revenue share statement; to a company’s owners: a partner firm asks for access, the access was approved, the firm opened the company for the first time, and the firm ended its access; and to the future owner of a company a firm set up: the link to confirm it): the recipient, the type of email, its delivery status and times, and for some types the details shown in the email (such as the organization name and the recipient’s name). Reminder emails, the pay-rights reminder, approval request emails, the summary of a payroll-details import and the “a person added a document” email store only internal identifiers and dates; names are filled in when the email is sent, and the document email never includes the file name. Links that carry a secret are never stored. These records are deleted automatically 60 days after they are created. The “HR shared a document with you”, “HR sent you a document to confirm” and “a document waits for your signature” emails store only internal identifiers and never include the title, the file name or anything the document says (the signature email names the document’s category). Reminders, approval requests, the “a person added a document” and the “HR shared a document with you” emails are optional: an organization’s owners and admins can turn their email off, and they are then shown only in Bizisy’s notifications. Each email is written in the recipient’s language: the one they chose, otherwise the organization’s default, otherwise English; nothing extra is stored for that. We do not send marketing email.
Technical and security data
When your browser or an API client talks to Bizisy, our servers and our providers receive technical data such as your IP address, the requested address, the time and the browser’s user agent. We use it to deliver the pages, to keep Bizisy secure (for example, rate limits on sign-up and its company-address check, invites, password resets, careers pages and on each API key’s requests; for these limits, and on a CV upload not yet sent, we keep only a fingerprint of the network address, for at most a day) and to find faults. Our server logs are kept for up to 30 days.
API requests
For requests made with an API key we keep a request count per key for each minute (the key’s identifier, a number and a time, no request content), to enforce the per-key limit; these counters are deleted after about an hour. When an API client sends an Idempotency-Key with a change, we keep a fingerprint of the request and its outcome so a retry can’t apply it twice; the result itself is kept only when it holds no personal data and no secret. Results with secrets (such as invite links or API keys) and results of changes to personal data are never stored there. These records are deleted after 24 hours (up to 48 hours including deletion delay).
Usage counts and Bizisy’s own view of organizations
To understand what running Bizisy costs, we count, for each organization and each day, how many requests its people and API keys made and how many actions they ran. These counts hold no personal data (an organization identifier, a day and two numbers) and are deleted automatically after about 400 days, or with the organization.
A few Bizisy staff can open an internal administration page, signed in with their Google account. It shows each organization’s name, web address, country, status and creation date, its owners’ names and email addresses (so we can contact them), how many logins it has per role, how many active people it has, its subscription, billing status and invoices, the usage counts above and when it was last used. It never shows the people records an organization keeps in Bizisy, their private details or their pay. For partner firms it shows what each firm gave when it applied, its people’s names, email addresses and roles, the names of its client companies with the state of each access, and its revenue share terms and statements, so that we can review applications and pay the share; never anything about a client company’s people. Every page opened there is recorded (which staff member, which page and when, no organization data), and these records are deleted after one year.
Data processing agreement
When an owner accepts Bizisy’s data processing agreement in Settings → Data & privacy, we record which version they accepted, when, the name and title they typed, the company’s legal name and registration or VAT number, the login that accepted it and a SHA-256 fingerprint of the exact text accepted. It is a contract record of the organization: it is in the organization’s full export, the accepting person’s own data download includes the versions they accepted, and it is deleted with the organization; erasing a person’s data does not remove it.
Promotions
When an organization redeems a promotion code (at sign-up or in Settings → Plan & billing), or Bizisy staff apply one for it, we keep which promotion and code, when and how it was redeemed (and, for one applied by our staff, which of them did it), when it started and ended, the discount each month’s invoice carried and, for programmes that ask for one, whether we received the organization’s review and case study. This is company data about billing: it is in the organization’s full export, and it is deleted with the organization (discounts printed on invoices are kept with the billing records).
Status updates by email
Anyone can ask for an email when Bizisy posts an incident on status.bizisy.com. We keep the email address, when it was confirmed and a code for its unsubscribe link; we are the controller of this data, and the basis is your consent (art. 6(1)(a)). We send nothing but a confirmation until you confirm; an unconfirmed request is deleted after 48 hours. Each incident email has a link to stop them, which deletes the address at once.
Research surveys
We sometimes ask people who do HR to answer a short survey on surveys.bizisy.com, to learn how to explain Bizisy and what people think of AI in HR (product research). You don’t sign in and we set no cookies. Your browser keeps a random code and your answers so far (in its local storage, on your device), so you can carry on later; each step is saved on our side under a fingerprint of that code, so answers count even if you stop early. We keep your answers (multiple choice, ratings and anything you type in the comment boxes), the language, the order the pages were shown in and when you started and finished. We do not store your IP address or anything about your device with them, and we never show your comments to other respondents: the thank-you screen shows only average ratings, and only once at least 20 people have finished. The answers are anonymous, unless you write something that identifies you in a comment; the basis is our legitimate interest in improving the product (art. 6(1)(f)), and we keep them for as long as they are useful for research. If you choose to leave your email and tick the box, your answers are no longer anonymous to us: we keep the email in a separate place, linked to your answers (so we can delete both if you ask), use it only to send you the results and invite you to try what we build, and delete it after 12 months at the latest; the basis is your consent (art. 6(1)(a)), which you can withdraw at any time by writing to privacy@bizisy.com (we then delete your email). Only a few Bizisy staff see the results, in our internal administration page. Answers are stored with the rest of Bizisy’s data on Google Cloud in the EU; no other company receives them.
Messages you send us
If you email privacy@bizisy.com, hello@bizisy.com or security@bizisy.com (vulnerability reports), we receive your address and what you write.
3. Google user data
If you choose Continue with Google, Google shares your name, email address and profile picture with Bizisy (the openid, email and profile scopes). Bizisy requests nothing else from your Google account: no Gmail, Drive, Calendar or contacts.
- We use this information only to sign you in to your organization in Bizisy (or, for people of partner firms, to the partner console) and to show who is signed in. In practice Bizisy uses your email address (and Google’s confirmation that it is verified) to match you to the login your organization created for you, and stores an identifier of your Google sign-in with that login. We do not use or keep your profile picture.
- We never sell it, never use it for advertising, and never share it with anyone except the service providers listed in section 6, who help us run Bizisy.
- You can disconnect Bizisy from your Google account at any time in your Google Account settings.
Bizisy's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. Microsoft sign-in
If you choose Continue with Microsoft, Microsoft shares your name and email address with Bizisy. We use them only to sign you in to your organization and show who is signed in, in the same way as Google sign-in above, and we never sell them or use them for advertising.
5. Why we use it, and on what legal basis
- To provide Bizisy: accounts, sign-in, sessions, invites, API keys, the webhooks an organization sets up, the in-app notifications, and the emails the service needs (welcome, invites, password resets, confirmations, role and access changes, payroll-change notices, and the approval requests, HR reminders, checklist task and document emails an organization keeps on). Basis: performance of our contract with you or with your organization, and our legitimate interest in providing the service your organization chose (GDPR art. 6(1)(b) and (f)).
- To count storage: the size of each organization’s files, to apply its storage limit and bill storage above the included amount. Basis: performance of our contract with the organization (art. 6(1)(b)).
- To keep Bizisy secure and working: technical logs, rate limits, activity records, investigating faults and abuse. Basis: our legitimate interests in security and reliability, and those of our customers (art. 6(1)(f)).
- To bill for Bizisy: billing details, payments, invoices and billing emails. Basis: performance of our contract with the organization (art. 6(1)(b)); keeping invoices is a legal obligation under Portuguese tax law (art. 6(1)(c)).
- To answer you when you write to us. Basis: our legitimate interest in replying, or steps you ask for before a contract (art. 6(1)(b) and (f)).
- To meet legal obligations, for example answering lawful requests from authorities (art. 6(1)(c)).
- HR data is processed on each customer’s instructions; the customer decides why and on what basis it is used.
We do not sell personal data, do not use it for advertising, and do not use it for automated decisions that have legal or similarly significant effects on you.
6. Service providers (subprocessors)
We use these providers to run Bizisy. Each handles personal data only to provide its service to us. The same list, grouped by the role each plays and with the date it last changed, is at bizisy.com/subprocessors; the data processing agreement for customers is at bizisy.com/dpa.
| Provider | What for | Where |
|---|---|---|
| Google Cloud (Google) | Cloud Run (our application servers), Firestore (our database, where all Bizisy data is stored), Cloud Storage (profile photos, company logos, documents and the CVs candidates send) and Document AI (reads the text of bank account proofs, for organizations with Verified bank details, of CVs sent as pictures, for organizations that use Hiring, and of the policies and contracts HR adds to Renewals from a document; nothing is kept by Google) | europe-west1, Belgium (EU); Document AI in the EU multi-region |
| Google Identity Platform (Google) | Sign-in: passwords, Google and Microsoft sign-in, in one sign-in tenant per organization and separate tenants for developer accounts and for partner accounts (the people of partner firms) | Google’s global infrastructure |
| Google Cloud Secret Manager, Cloud Logging, Cloud Monitoring, Cloud Scheduler (Google) | Service credentials (no personal data), server logs, alerts to us about failed background jobs (no personal data), scheduled jobs | Google’s infrastructure |
| Firebase Hosting (Google) | Serves the files of the web app, the developer site and the partner console | Google’s global network |
| Google Fonts (Google) | Serves the Geist typeface the Bizisy app uses (on your organization’s address); your browser fetches it from Google. The bizisy.com website serves its own fonts. | Google’s global network |
| Cloudflare | DNS, content delivery, edge routing and security, and forwarding of email sent to our @bizisy.com addresses | Cloudflare’s global network |
| Resend (a US company) | Sends Bizisy’s transactional email | eu-west-1, Ireland (EU) |
| Stripe (Stripe Payments Europe, Ireland) | Takes payments, by a saved card or on its invoice payment page, and keeps the payment method when an owner or admin saves one. For fraud prevention and its legal and regulatory duties Stripe also acts as an independent controller, under its own privacy policy | EU, with transfers to Stripe, Inc. in the United States |
| TalentLMS, 360Learning, Docebo or the organization’s own Moodle, only when an organization connects them | Receive learner accounts (name, work email and, where the platform has them, job title, manager and team groups) and course enrolments, and tell Bizisy who completed a course. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processor | Where the organization’s platform keeps its data |
| Atlassian (Jira, Jira Service Management), Linear and Asana, only when an organization connects them | Receive the checklist tasks the organization chose to have done there (title, details, due date, labels, and the public and job details of the person the template names) and are asked which user has a work email, to assign them. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processor | Where the organization’s Atlassian site, Linear workspace or Asana workspace keeps its data |
| Xero, Exact Online, Holded, Odoo and Moloni ON, only when an organization connects one | Receive the names of the organization’s teams, and when the organization turns them on, people’s names and work emails as suppliers and the monthly pay totals per team it approved. Each is the organization’s own accounting tool, under its agreement with that provider: a recipient chosen by the organization, not our processor | Where the organization’s account with that tool keeps its data |
| Slack (Salesforce) and Microsoft Teams (Microsoft), only when an organization connects them | Receive the announcements the organization chose (name, job title, team, manager) in the organization’s own Slack workspace or Teams channel; Slack is also asked which member has a person’s work email, to mention them. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processor | Where the organization’s Slack workspace or Microsoft 365 tenant keeps its data |
| Google Chat (Google), Mattermost, Discord and Rocket.Chat, only when an organization connects them | Receive the announcements the organization chose (name, job title, team, manager) at the webhook the organization created in its own Google Chat space or Mattermost, Discord or Rocket.Chat channel; nothing else is sent to them. Each is the organization’s own tool, under its agreement with that provider (or on its own server, for self-hosted Mattermost and Rocket.Chat): a recipient chosen by the organization, not our processor | Where the organization’s Google Workspace, Discord server or Mattermost or Rocket.Chat server keeps its data |
| Google Calendar (Google Ireland) and Outlook Calendar (Microsoft Ireland), only when an organization connects one | Receive the invitations for a new hire’s first-day meetings (and, if turned on, onboarding task due dates): meeting title, the hire’s name, time, the organization’s note, and the invited people’s names and work email addresses, on the organization’s own calendar account. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processor | Where the organization’s Google Workspace or Microsoft 365 account keeps its data |
| Staffology (IRIS Software Group), Xero Payroll (Xero Limited) or Silae (Silae SAS), only when an organization connects its own account and sends a locked pay period | Receive what HR reviewed and sent: employees’ names, contact and payroll details, pay and variable pay (Silae: variable pay only). The organization’s own payroll tool, under its agreement with that provider (the organization’s processor, not ours) | United Kingdom (Staffology), Xero’s hosting (Xero Payroll), EU (France, Silae) |
| Yousign (Yousign SAS, now Youtrust), only when an organization connects its own account | Receives the documents HR sends for signature and each signer’s name, email address, language and, for advanced or qualified signatures, phone number; sends back the signed copy, the audit trail and status updates. The organization’s own e-signature provider, under its agreement with Yousign (the organization’s processor, not ours) | EU (France) |
| Pleo, Moss (Nufin GmbH), Payhawk and Spendesk, only when an organization connects them | Receive what the organization’s spend management sync sends (names, work email, team, team lead as approver, card blocks for leavers, as each tool’s API allows), and answer Bizisy’s reads of their people and teams. Each is the organization’s own tool, under its agreement with that provider: a recipient chosen by the organization, not our processor | Where each tool keeps the organization’s data |
| Segurança Social (Instituto da Segurança Social, Portugal), only when an organization enters its access and HR sends a notice | Receives the hire and leave notices HR confirms for the organization’s Portuguese legal entities, as the law requires of the employer; a public authority and separate recipient, not our processor | Portugal (EU) |
| Nmbrs (Visma Nmbrs) and Loket.nl, only when an organization connects them | Receive the joiners, changes and leavers of the legal entity the organization chose (pay never). Each is the organization’s own payroll tool, under its agreement with that provider: a recipient chosen by the organization, not our processor | Where the organization’s payroll tool keeps its data |
| Okta, Teamtailor and Greenhouse, only when an organization connects them | Okta receives the accounts the organization keeps in step with HR (name, work email, job title, team, manager, groups, whether the account is active or suspended); Bizisy reads from Teamtailor or Greenhouse the candidates hired there (name, own email, job title, department, start date). Each is the organization’s own tool, under its agreement with that provider: a recipient or source chosen by the organization, not our processor | Where the organization’s Okta, Teamtailor or Greenhouse account keeps its data |
| Jamf Pro (Jamf), Microsoft Intune (Microsoft), Kandji and Workwize, only when an organization connects them | Bizisy reads the organization’s devices or equipment from its own tool (device details, and the name and email of the user the tool lists); nothing about people is sent to them. Each is the organization’s own tool, under its agreement with that provider: a source chosen by the organization, not our processor | Where the organization’s tool keeps its data |
| DocuSign (DocuSign, Inc. and its affiliates), Dropbox Sign (Dropbox, Inc.), Signaturit (Signaturit Solutions, S.L., a Namirial company) and Skribble (Skribble AG or Skribble Deutschland GmbH), only when an organization connects its own account | Receive the documents HR sends for signature and each signer’s name, email address, language and, where the chosen level needs a code by SMS, phone number; send back the signed copy, the audit trail and status updates. The organization’s own e-signature provider, under its agreement with that provider (the organization’s processor, not ours) | Where the organization’s account with that provider keeps its data (for example DocuSign’s EU environment, Signaturit in Spain, Skribble in Switzerland or Germany) |
| VIES (European Commission) | Checks that an EU VAT number is valid (the VAT number only); a separate recipient, not our processor | EU |
| Moloni (Portugal) | Issues certified invoices (faturas) with the billing details, as Portuguese tax law requires | Portugal (EU) |
Mail sent to our @bizisy.com addresses is forwarded by Cloudflare to a mailbox hosted by Google.
7. International transfers
Bizisy’s database and application servers are in the EU. Google, Cloudflare and Resend are companies based in the United States, and parts of their services (for example sign-in, content delivery and support) may involve processing outside the European Economic Area. Stripe’s European entity shares payment data with Stripe, Inc. in the United States. Where that happens, the transfer is covered by the European Commission’s Standard Contractual Clauses included in each provider’s data processing terms, or, for providers certified under it, by the EU-U.S. Data Privacy Framework.
8. How long we keep it
- Account data: as long as your login exists in your organization. Your organization can disable it; to have it deleted, ask your organization or write to us.
- Sessions: they stop working after 7 days or when you sign out.
- Invites: links stop working after 14 days, when accepted or when revoked; the invite record stays with the organization’s data.
- People invited by email: kept until they are registered (then as any employee record) or until the organization withdraws the invitation, which erases them.
- Chat announcements (Slack, Teams, Google Chat, Mattermost, Discord, Rocket.Chat): the connection until the organization disconnects it; the record of each announcement (identifiers and days only) for 90 days, or until the person is erased or the tool is disconnected. Posts in the chat tool stay there under the organization’s control.
- Directory sync: the connection until the organization disconnects it; links between people and accounts until the person is erased or the directory is disconnected; first passwords until seen, at most 7 days.
- Calendar invites: the connection until the organization disconnects it; which invitation belongs to which person or interview until the meeting has been over for 30 days, the person is erased or the calendar is disconnected; the log of runs (no names) for 30 days. Invitations stay in people’s calendars under the organization’s control.
- E-signature: each e-signature tool’s connection until the organization disconnects it; each signature request record (identifiers, statuses, dates and which tool it went through) with the organization’s documents, until the document’s person is erased (an open request is then canceled in its tool first); signed copies and audit trails as any other document; for signatures made in Autenticação.gov, what each check read from the signing certificates, with the request.
- Document templates and contract clauses: each template and clause, its draft and published versions (and who approved them, where required) with the organization’s data, until the organization deletes its account (archiving keeps it); a Word file uploaded to start one, until the draft is made, and never more than two hours; documents made from them, their filled text and Word copies, and acceptance records made in Bizisy, as any other document of the person.
- Prepared documents and consent to electronic documents: written statements, change notices and drafts waiting for HR, sent or discarded ones with their dates and proof of delivery, and a person’s consent to receive documents electronically, until the person is erased or the organization deletes its account; a background generation’s progress record, 30 days.
- Checklist tasks done in another tool: the tool’s identifier, key, address and status are kept on the task, as long as the checklist is kept; the tasks created in the tool stay there under the organization’s control.
- Data exports and BI tools: each export’s settings and its last delivery until the organization disconnects it or closes its account; the delivery log (no names) for 30 days; the BI token’s hash until it is replaced or revoked. Files and tables delivered to the organization’s own storage are kept there for as long as the organization decides.
- Spend management tools: the connection until the organization disconnects it; what Bizisy keeps about people’s accounts in the tool until the person is erased, the tool is disconnected, or another account of the tool is connected.
- Country obligations: notice records, country data, records of Relatório Único files made, the Relatório Único yearly forms and service providers, and posted vacation maps are kept with the organization’s data; a person’s notices and country data are erased with them, and their name and dates are removed from posted vacation maps. Segurança Social access until the organization removes it or closes its account.
- Okta: the connection until the organization disconnects it; which account belongs to whom, and what Bizisy last sent it, until the person is erased or Okta is disconnected.
- SCIM tokens: a hash of each token until it is revoked or the organization closes its account.
- Candidates: an application not hired until the organization’s period for its country has passed since the job closed (by default 6 months, 4 weeks in the Netherlands, never more than 24 months), or at once when the candidate withdraws or deletes it from their status page; a hired person’s application the same period after the hire (the offer they accepted and its signed PDF stay with their employee record); offers not accepted, with the application; talent pool membership for 2 years from the candidate’s consent, unless renewed or left earlier; a referral invitation nobody answered, 6 months. What happened to an application is then kept without any personal data.
- Internal applications (people who work for the organization applying from My workspace): as candidates’ applications; a withdrawn one after 30 days; an agreed move stays with the person’s employee record as a job change.
- Hires from Teamtailor or Greenhouse: the candidate’s details until HR decides (then only the tool’s identifiers and the outcome stay), at most 180 days; the identifiers until the person is erased or the organization closes its account.
- Accounting tools: the list of the tool’s companies and accounts, and the headcount-cost journals Bizisy prepared, until the organization closes its account.
- Other connected tools: the connection until the organization disconnects it or closes its account; links between Bizisy records and the tool’s records until the person is erased or the tool is disconnected; the log of what Bizisy did (no names) for 30 days; the identifiers of notices already handled for 7 days.
- Time clock: clockings, corrections, overtime requests and closed months are kept for the period the law of the person’s country sets for working-time records (4 years in Spain, 5 in Portugal, 2 in Germany, otherwise 4), counted from the end of their month; the organization can choose 1 to 10 years per country. They are then deleted by a daily job, and everything is deleted when the person’s data is erased or the organization closes its account. Wrong-PIN counts are deleted after 2 hours.
- Door terminal punches waiting to be matched (an unknown badge, or held back by a rule): deleted 92 days after they arrived, whether HR applied them (they are then ordinary clock records), dismissed them or did nothing; badge numbers are kept until HR removes them or the person’s data is erased.
- Time off: bookings, requests and balance adjustments are kept while the person works for the organization and for 5 years after their last day (the organization can choose 1 to 10 years, to meet its country’s record-keeping rules), then deleted; everything is deleted when the person’s data is erased or the organization closes its account. Calendar links are kept until revoked; the reminder records that stop an email going twice are deleted after about 13 months.
- Surveys: answers saved to finish later are deleted 30 days after the last change; sent answers, invitations and replies to comments are deleted 24 months after the survey closes (or the period the organization chose, 6 months to 10 years), sooner if the organization erases the person’s data or closes its account; surveys and their group results are kept until the organization deletes them or closes its account.
- Shift rotas: rotas, shifts, positions, templates and availability are kept until the organization deletes them, erases the person’s data or closes its account; each published version of a rota week is kept for the period the law of the rota’s country sets for working-time records (4 years in Spain, 5 in Portugal, 2 in Germany, otherwise 4), then deleted by a daily job; shift requests are kept until the organization closes its account (they end when the shift starts); the counters that limit shift emails are deleted after two days.
- Performance and talent: review results, potential assessments and calibration records are deleted when the period the organization sets has passed after a review cycle closes (by default 5 years; it can choose 1 to 10), by an hourly job; goals, succession plans and skills are kept until the organization deletes them, erases the person’s data or closes its account.
- Training register: kept with the organization’s data until it deletes a record, erases the person’s data (their records and certificates are then deleted at once) or closes its account. The law sets no period of its own; we suggest organizations keep them for as long as the person works there and 5 years after, the limitation period for labour fines.
- Benefits: a person’s choices are kept with the organization’s data, including after a change (as the history payroll needs), until it erases the person’s data (they are then deleted at once) or closes its account.
- Bonus plans: each person’s awards and letters, 3 years after the plan’s release, then deleted automatically; a plan cancelled before release stays with the organization’s data, read-only, until it closes its account. Erasing a person’s data deletes their awards and letters at once.
- Salary reviews: each person’s rows, proposals and letters, 3 years after the cycle’s release, then deleted automatically; a cycle cancelled before release stays with the organization’s data, read-only, until it closes its account. Erasing a person’s data deletes their rows and letters at once. A letter’s PDF copy in Documents follows the person’s documents.
- Talent insights: a person’s current band while the organization uses Talent insights, the person works there and has not objected or been excluded; it is deleted at once when the organization switches it off, the person objects, their leaving is announced or their data is erased. The record of every band worked out, who looked at it and what they did is kept for 12 months (as the EU AI Act asks of the provider and the organization), then deleted; erasing a person’s data deletes it at once.
- Equipment register: kept with the organization’s data until it deletes an item (a device synced from a tool is retired instead) or closes its account; when a person’s data is erased, what they held is released and they are removed from the items’ history. Devices read from a connected tool stay in the register after the tool is disconnected.
- Team history, scheduled team changes, reorg plans and dotted lines: kept with the organization’s data. Erasing a person deletes their dotted lines and empties the plans that name them.
- Saved groups: kept with the organization’s data until an owner, admin or HR deletes them. Erasing a person removes them from the groups that name them as a manager.
- Email delivery records: deleted automatically after 60 days.
- In-app notifications: deleted automatically 90 days after they are created, read or not, or, when the person they are for or about is erased, emptied at once and deleted within a day. Optional email counts (per organization and month, no personal data): about 13 months.
- Reminder records (which reminder was sent for whom, identifiers and dates only): deleted automatically after about 400 days; when the person’s data is erased, unlinked from them at once and deleted within a day.
- Webhook delivery records (identifiers, never names, and the outcome of each attempt): deleted automatically after 30 days; the stored answers of the receiving systems are cleared when a person’s data is erased. Webhook endpoints: until the organization deletes them or closes its account.
- Installed marketplace apps: while installed, and 30 days after they are uninstalled. Apps and their review history: until their owner deletes them. Developer accounts, their public profile, memberships and developer Activity: until the developer deletes their account (the apps they own themselves with it). Developer organizations: until an owner deletes them. Organization invitations: 14 days. Developer sessions: up to 7 days. Developer access tokens: until 30 days after they expire (at most a year after they are created) or are revoked, or until the developer deletes their account. Sandbox sign-in codes: 60 seconds. Developer sandboxes: until deleted, or closed after 120 days without use (a warning is emailed after 90).
- Partner accounts and firms: until the partner deletes the account or the firm is closed; a firm’s invitations 14 days. Partner access: while active, and 2 years after it ended or was declined (deleted with the company if it closes sooner); a firm’s logins in a company are deleted the moment its access ends. One-time links to open a company from the partner console: 60 seconds. Companies set up for a client: until confirmed (then kept with the access), or 30 days after the link expired or was cancelled. Referral and revenue share records (company name, invoice numbers, months and amounts, never people): 10 years, with the invoices.
- API request counters: pseudonymous (key identifier only), deleted after about an hour.
- AI setup counters: about 13 months (400 days) after their day, then deleted within a day; sooner if the organization is deleted.
- Connected AI apps: as long as the app is connected. A connection stops working when it is disconnected, when it is not used for 30 days, or at once when the person’s login is turned off. Its record is deleted about 30 days after it was disconnected or last used (for a turned-off login, up to 60 days after its last use), within a day of that date. Requests to connect that nobody answered stop working after 10 minutes and are deleted within a day. Apps that registered themselves stop working 24 hours after registering if they never connected, and 180 days after they were last used otherwise; they are deleted within a day of that.
- Idempotency records (API retries): non-personal results only, deleted after 24 hours (up to 48 hours including deletion delay).
- Server logs: up to 30 days.
- Usage counts (per organization and day, no personal data): deleted automatically after about 400 days, or when the organization is deleted.
- Records of Bizisy staff opening the administration page: deleted after one year.
- HR data, activity records and the change history: as long as the customer keeps its Bizisy organization (the change history about a person is deleted when their data is erased), unless the customer deletes them earlier (for example, Bizisy can erase a former employee’s personal data). When an owner closes the organization, all of it, including its people’s photos and the company logo, is deleted for good 14 days later, unless an owner reopens the company before then (see “Closing a company” above).
- Documents: until the organization deletes them, the person’s data is erased, or the organization is closed and deleted. A deleted document’s file is removed from our storage straight away (at the latest within an hour), and we keep no earlier versions. An upload that is never finished is deleted within a day. Download links stop working after 5 minutes.
- Profile photos and company logos: until they are replaced or removed, or the person’s data is erased. A replaced or removed image is deleted from our storage straight away, and we keep no earlier versions. Copies that were already shown can stay in a browser’s cache for up to an hour (a logo, up to 5 minutes, also in shared web caches) before they disappear.
- Imports of people from a file: deleted 30 days after they were started (within a day of that), when discarded, or with the organization; a file larger than 1 MB is deleted from our storage once it has been read, and rows about a person when their data is erased.
- Exports for another HR tool: the file 7 days after it was made (or when someone in it is erased, or with the organization); the record of the export 30 days after it was made.
- Moves from another HR tool: deleted 30 days after they started (within a day of that), or with the organization; uploaded files once they have been read; an API key connected for the move when the move ends or within 24 hours of being connected, whichever comes first; rows about a person when their data is erased.
- Approval requests: with the organization’s HR data; deleted when the person they are about is erased, or with the organization.
- Payroll preparation: locked pay periods, their copies of each person’s details, variable pay, net pay, notes, comments and export fingerprints stay until the organization closes; a person’s part of them is deleted when their data is erased (comments they wrote keep only that a comment was made). The files of unfinished payslip uploads are deleted within a day.
- Pay equity: pay bands, job evaluations, categories, pay gap reports and requests about pay stay with the organization’s HR data. Variable pay imported for a pay gap report is deleted when the report is finalised (or the draft report is removed). A person’s requests about pay are deleted, and their sex for equal-pay reporting cleared, when their data is erased.
- Checklists and open positions: with the organization’s HR data; a person’s checklists are deleted when their data is erased, and everything with the organization.
- Erasing a former employee: when an organization erases someone’s personal data, their pay history, profile photo, documents (with their files), the approval requests about them, their requests about pay levels, variable pay imported for a pay gap report, their payroll lines, variable pay, net pay and employee number, and their checklists (and comments they wrote on others’ tasks) are deleted and their payroll details, custom field values (including those on their jobs) and personal details are cleared, and fields on colleagues, teams or open positions that name them are emptied. Their job dates, titles and contract terms stay, without their name, so the organization’s headcount history adds up.
- Billing records (billing details as printed on each invoice, invoices and certified invoices): 10 years, as Portuguese tax law requires, also after the organization leaves Bizisy (reduced then to the legal name, tax number, address and amounts: the billing email is erased); erasing a person’s data does not remove them, because they are company data we must keep. Records of Stripe notifications (an event identifier and type, no personal data) are deleted after 90 days.
- Data processing agreement acceptances: with the organization’s data, until it is deleted; kept when a person is erased (a contract record of the organization).
- Promotion records: with the organization’s data, until it is deleted.
- Research survey answers: kept anonymous for as long as they are useful for research; an email given with consent is deleted 12 months after you gave it, or sooner when you ask.
- Status update subscriptions: until you unsubscribe; a request never confirmed is deleted after 48 hours. The status page’s health checks hold no personal data and are deleted after about 90 days.
- Backups: our database keeps point-in-time recovery data for 7 days, so deleted data disappears from it within 7 days. We have no other backups.
9. Security
- All traffic is encrypted with TLS, and Google Cloud encrypts stored data at rest.
- Passwords are held by Google Identity Platform; session tokens, invite secrets, API keys and the tokens of connected AI apps are stored only as hashes. Webhook signing secrets and the access and secrets of connected tools are stored encrypted; the BI token for data tools is stored only as a hash. Connected apps sign in with OAuth 2.1 and PKCE; their access lasts an hour at a time, works only on the organization’s own address and can be disconnected at any time. Marketplace apps install with OAuth 2.1, PKCE and a client secret stored only as a hash; their tokens work only for the organization that installed them.
- The session cookie is HttpOnly (page scripts cannot read it), valid only on your organization’s own address, and sent only over HTTPS.
- Document files are uploaded and downloaded through links that work only for that one file and only for minutes (15 minutes to upload, 5 to download); each file is checked before it is accepted, previews run in an isolated viewer, and downloads are always saved as files.
- Pay has a stricter visibility than other job details (the person and HR only), and payroll details can only be changed in the app, with an email to the person and their HR team on every change.
- Access inside an organization follows roles, private details are limited as described in section 2, and sign-up, invite and password-reset requests and API keys are rate limited.
No system is perfectly secure. If we confirm a personal data breach affecting an organization’s data, we tell its owners and admins without undue delay and within 48 hours, and, where the law requires, the supervisory authority and the people affected. Every measure, and what we have not done yet, is described at bizisy.com/security; Bizisy’s current health and past incidents are at status.bizisy.com. To report a vulnerability, write to security@bizisy.com.
11. Your rights
Under the GDPR you have the right to access your personal data, to have it corrected or erased, to restrict or object to its processing, and to receive it in a portable format. Where processing is based on our legitimate interests, you can object to it at any time.
In Bizisy you can see and correct most of your own details in your profile, and download a copy of everything Bizisy holds about you (your profile and photo, the documents shared with you, job and pay history, invites, logins, activity, your checklists as the app shows them to you, the reminder emails sent about you, your occupational health-check dates, the notifications addressed to you, decided approval requests about you, your requests about pay levels with their answers, the history of changes to your information, any variable pay imported for a pay gap report that is not yet finalised, and the payroll periods you were in with your variable and net pay) with Download my data. When HR downloads your data to answer a request, it also lists the webhook notices sent about you and the records about you linked to a connected tool.
If you applied for a job at an organization that uses Bizisy, the link in your emails opens your status page: there you can see the data held about you and download it, withdraw your application (it is deleted at once) and ask for a new link. For anything else, write to the organization (it decides about your application) or to us, and we will help it answer.
A developer can download everything about their developer account in the developer console (Account → Download my data: the account, their public profile, their organizations and roles, invitations, their access tokens (never the tokens themselves), the apps they created, the versions they submitted and their developer Activity) and delete the account there (Account → Delete).
To exercise these rights, write to privacy@bizisy.com. We answer within one month. We may ask you to confirm your identity. For HR data that a customer controls, we pass your request to that organization and help it respond.
12. Complaints
If you think we handle your data wrongly, please tell us first at privacy@bizisy.com. You also have the right to complain to a data protection supervisory authority, in particular in the EU country where you live or work. Our lead authority is the Comissão Nacional de Proteção de Dados (CNPD).
13. Children
Bizisy is a tool for businesses and is not meant for children. We do not knowingly collect personal data from anyone under 16 for their own use of Bizisy.
14. Changes to this policy
We will update this policy when Bizisy changes, and show the date of the last update at the top. If a change is significant, we will tell customers by email or in the app before it takes effect.
Questions? Write to privacy@bizisy.com about privacy, or hello@bizisy.com about anything else.