Privacy Policy

This policy explains what data Tempry collects, how it's used, how long it's kept, and how you can access, transfer, or delete it - including data accessed through Tempry's Slack integration.

Tempry is absence management, performance reviews, and 1-on-1s software used by a company (the "workspace admin" or "customer") to manage its own employees ("users"). If you're an employee using Tempry through your employer, your employer controls your account; contact them first for anything covered here that they can resolve directly, or contact us using the details below.

What data we collect

Depending on how your organization uses Tempry, we collect:

• Account and directory data - names, work email addresses, roles, and avatars for people your admin adds to Tempry.
• Leave, review, and 1-on-1 records - time-off requests and balances, performance review content, and 1-on-1 notes entered into Tempry.
• Slack workspace data, when your admin connects the Slack integration:
  • Your Slack team ID, team name, and a bot access token, so Tempry can post to your workspace.
  • The list of public and private channels visible to the bot, so an admin can pick a digest channel.
  • Workspace member directory data (Slack user ID, name, email address) via Slack's users:read and users:read.email scopes, used only to match a Slack account to the corresponding Tempry account by email. We do not use this email address to send marketing and we do not contact you by email using it without your consent.
  • Messages sent directly to the Tempry bot in a DM, and slash command text, used only to interpret and respond to that request (for example, requesting or approving time off from Slack).
  • If a user individually connects "Slack status sync," a per-user Slack token (scoped to users.profile:write only) used solely to update that user's Slack status text and emoji while they're on leave.
• Usage and log data - basic technical logs (timestamps, error traces) generated by using the app, used only for debugging and security.

We do not request or receive any Slack data beyond what's listed above. We don't read message content outside of DMs sent directly to the Tempry bot, and we don't use Slack data for advertising or sell it to third parties.

How we use it

• To operate the core product: tracking leave, reviews, and 1-on-1s.
• To post absence digests, approvals, birthday/anniversary shout-outs, and reply to slash commands and DMs in Slack, on your admin's behalf.
• To match a Slack account to a Tempry account so messages reach the right person.
• To keep a connected user's Slack status current while they're on leave, if they opted in.
• To operate, secure, and troubleshoot the service.

How long we keep it

We retain account, leave, review, and Slack integration data for as long as your organization's Tempry account is active. Slack bot access tokens and every per-user status-sync token in the workspace are deleted when a workspace admin disconnects Slack from within Tempry - and automatically, without you contacting us, if the app is removed from Slack's own app management page instead. An individual user's status-sync token is deleted when that user disconnects status sync, revokes the authorization from their own Slack settings, or has their account removed.

When an organization's Tempry account is closed, we keep its data for 30 days so an admin can request an export, then delete it from production systems, aside from what we're required to retain for legal, tax, or security purposes.

Access, transfer, and deletion

You can request a copy of your data, ask us to correct it, transfer it, or delete it, by emailing us at the address below. For employees of a customer using Tempry, we'll generally route account-level requests through your organization's admin, since they control the account; we'll still help directly wherever we can. If applicable law (such as GDPR or the CCPA) gives you additional rights over your data, those rights apply and we'll honor them.

Sharing

We don't sell your data. We share it only with the third-party providers we use to run Tempry - hosting and database, email delivery, file storage, and the AI provider behind the optional review Insights and 1-on-1 summary features - under contracts limiting them to processing it on our behalf; with Slack and Google where a customer connects those integrations; or when required by law. Our sub-processor list names each one, what it processes, and where.

Tempry's servers and database are in Germany. Some of those providers are based in the United States, so using the features that depend on them involves transferring personal data outside the EU/EEA, relying on transfer mechanisms such as the EU Standard Contractual Clauses.

Security

Data is transmitted over encrypted connections (HTTPS/TLS). Access to production data is limited to what's needed to operate and support the service. Slack webhook requests are verified using Slack's request-signing scheme before we act on them.

Changes to this policy

If we make material changes to this policy, we'll update the effective date above and, where required, notify affected customers.

Contact us

For any request or question about your data, email [email protected].