Provider
Leonardo Antonio Carta (Nema)Controller
c/o Emperon Studio GmbH, Sachsenring 51a, 50677 Köln, Deutschland
This notice supplements the Privacy Policy for Nema Crew for the Harvest module. It does not repeat what the policy says for all modules. That includes the runtimes (Section 6), pseudonymisation and field masks (Section 7), the framework for modules (Section 11), backups (Section 17.6) and your rights (Section 18).
1. Provider and controller
This module is provided and operated by Leonardo Antonio Carta (sole proprietor), c/o Emperon Studio GmbH, Sachsenring 51a, 50677 Cologne, Germany, support@nema.im. It runs as a separate service on our server in Germany. We are the controller. If you use the module in an organisation, we process the data on behalf of the organisation under the Data Processing Agreement.
Harvest is not the provider of this module. Harvest processes the data in your Harvest and Forecast account under its own responsibility and its privacy policy.
2. What data the module processes
You connect the module in one of two ways:
- Connect with Harvest (OAuth): You sign in to Harvest ID and allow the "Nema Crew" app access with the scope
all. That is read and write access to all Harvest and Forecast accounts your person has access to, each with your role there. Harvest gives us an access token (valid for 14 days) and a refresh token for this. After sign-in, the module asks Harvest for your accounts (identifier, name, product) and, in the first Harvest account, for your person (identifier, first and last name). It stores the identifier and name of that account, identifiers and names of further accounts, and your identifier and name in Harvest. You can switch the account in the settings using the "Account ID" field. - Own access token: You enter the credentials below yourself.
Credentials you enter when setting up with your own token:
- a personal access token from Harvest ID (id.getharvest.com/developers). It acts with your role in Harvest: as a regular member, agents see and change only your own time; as an Administrator or Manager, also the team's. The same token works for Forecast, Harvest's resource scheduling;
- the account ID of the Harvest account and, if you use Forecast, that of the Forecast account;
- settings for the triggers: "Events for" (only you, or
all= the whole team), budget thresholds, utilisation limits and milestone lead time.
If an account ID is missing, the module asks Harvest for the token's accounts (identifier, name, product). If the token has exactly one account, it enters its identifier and name into the stored configuration.
The module receives from Harvest:
- the account (company name, the account's address, settings such as time tracking, week start, currency, enabled features) and your person (identifier, name, roles, time zone, weekly capacity);
- time entries with identifier, date, person, client, project, task, hours, notes, billability, billing and approval status, running timer, start and end time, times of creation and change, and link;
- projects with name, code, client, billing method, budget and duration, the tasks per project and your project assignments;
- clients (name, status, currency) and the account's task types;
- people in the account with names, email addresses, roles, contractor flag, status and weekly capacity (only as far as your role allows);
- budgets and time reports (hours and billable amounts per client, project, task or person);
- invoices with number, status, client, subject, amounts, tax, discount, notes, purchase order, period, line items, dates and link, and payments on them with amount, date, who recorded them, notes and payment gateway;
- expenses with date, person, client, project, category, notes, amount, units and status. The module does not retrieve receipts themselves, only whether one exists.
The module receives from Forecast:
- assignments (who is scheduled on which project on which days with how many hours, with notes, who last changed it, and whether it is time off);
- people with names, email addresses, roles, admin flag, weekly capacity and working days, placeholders, projects, clients, milestones, remaining budgeted hours and, calculated from these, the utilisation per person.
The module does not create invoices, estimates, payments, expenses, projects, clients or tasks and does not send anything.
3. What for
Exclusively for the functions of Nema Crew that you use and for the tasks that you or members of your organisation give an agent. The agent acts with your token or sign-in and your role in Harvest:
- reading: check the account, list time entries and running timers, read projects, clients, tasks, people, budgets, time reports, invoices and expenses; in Forecast read assignments, utilisation, people, projects, milestones and remaining budgeted hours;
- writing: log time and change time entries, start and stop timers; delete a time entry only when the agent explicitly confirms (otherwise it only shows what would be deleted); in Forecast schedule yourself or placeholders and change such assignments; schedule other people, change their assignments or delete an assignment only with explicit confirmation.
Triggers: Harvest and Forecast have no webhooks. If you have set an agent to one of the following triggers, we query regularly:
- new time entries, started and stopped timers (every five minutes), changed time entries (every ten minutes);
- new invoices and new payments (every 15 minutes), projects reaching a budget threshold (hourly);
- new or changed Forecast assignments (every 15 minutes), over- or under-planned people this or next week, and upcoming milestones (hourly).
Unless "Events for" is set to all, time entries, timers, assignments and milestones only concern you; with all, the whole team, as far as your role can see it. Up to 25 events per query, each of which starts the agent. Without an agent that uses the trigger, the query does not take place. In an organisation, the organisation can block such triggers for the module.
4. Whom the data goes to
- to the module's service on our server;
- to Harvest (id.getharvest.com, api.harvestapp.com and api.forecastapp.com) when an agent reads or writes or a trigger queries;
- as a result or event to the language model of the runtime you chose, to the extent an agent needs the data for the task (Privacy Policy Section 6);
- to people in your Harvest and Forecast account, who see what an agent logs, changes or schedules there, according to the rights Harvest gives them;
- to other members and agents in the channel in which an agent uses the data;
- to the data centre operator on whose hardware our server runs and where our backups are kept, as our processor (Sections 17.6 and 20).
The module uses no further service providers.
Countries outside the EU: Harvest (Bending Spoons S.p.A., Italy) may also process data outside the EEA, including with cloud providers in the USA, according to its own information on the basis of standard contractual clauses, adequacy decisions or binding corporate rules (Arts. 45–47 GDPR). Harvest is not certified under the EU-US Data Privacy Framework; Harvest does not state where its own hosting is located. For the service providers of the runtimes, Section 16 of the Privacy Policy applies.
5. Storage and protection
- Credentials: We store the token, or the access and refresh tokens of the sign-in, the account IDs, the settings and the account names added by the module encrypted (AES-GCM) in our database. The module receives them from our server with each call and does not store them itself.
- Content: The module does not permanently store content from Harvest or Forecast. What an agent makes of it, meaning responses, memories, knowledge entries, the steps of its run and the card for an event that triggered it, we store like other content (Privacy Policy Sections 4 and 5).
- Caches and state: Only in the module's memory, not on disk, and deleted whenever the module restarts:
- account and person data from Harvest for up to one hour, and people, projects, clients, placeholders and the account from Forecast for up to ten minutes, so that not every request fetches them again;
- for the triggers, identifiers and times of entries, timers, invoices, payments and assignments already reported, budget thresholds reached, and utilisation alerts and milestones already reported;
- the times of the latest requests per token, to stay within Harvest's limits.
- Transmission: The connection to Harvest and between your apps and our server is encrypted with TLS.
- Pseudonymisation: In organisations that have switched on pseudonymisation, the module's results and the events that trigger an agent go to the language model pseudonymised, unless the organisation has switched this off for the module. For events, the organisation can hide or replace individual fields with field masks, such as person, client, notes, subject, amount, "recorded by" and "changed by". Both are off by default, and pseudonymisation has limits (Privacy Policy Section 7).
6. Retention, disconnecting, revoking
- Disconnecting: If you disconnect the module in the app, we delete the credentials from our database immediately. After that, no agent retrieves data from this account any more. If an Admin or Owner set up the module for an organisation, only the organisation can disconnect it.
- Revoking at Harvest: You can revoke your own token at any time at https://id.getharvest.com/developers. Disconnecting in the app only deletes it with us; at Harvest it stays valid until you revoke it there. We therefore recommend doing both. For a sign-in through the "Nema Crew" app, disconnecting does not revoke anything at Harvest; we delete the access and refresh tokens with us, and the access token expires at Harvest after 14 days at the latest. Harvest's public help does not name a place where you can withdraw an app's authorisation yourself; contact Harvest support for this.
- What remains: What an agent has taken over from Harvest data into messages, memories or knowledge entries remains stored after disconnecting until you delete it (Privacy Policy Section 17.1). Time entries and assignments an agent created or changed stay in Harvest or Forecast.
- Deleting your account: With your account we immediately delete your credentials and content (Privacy Policy Section 17.5). Modules set up for an organisation remain until the organisation disconnects them or is deleted.
- Backups: The data, including the encrypted tokens, remains in our backups for up to about 6 months (Privacy Policy Section 17.6).
7. Legal basis
Art. 6(1)(b) GDPR, because the module carries out the connection you set up. For third parties' data, such as team members, clients and people in assignments, Art. 6(1)(f) GDPR applies, limited to the task you give the agent. In organisations we process on their behalf (Privacy Policy Section 2). Your confirmation of this notice is not consent. To end the processing, disconnect the module.
Documents
- This notice
- Data Processing Agreement
- Harvest Privacy Policy
This notice supplements the general privacy policy for this module. In the app you confirm it before connecting.