LAST UPDATED AUGUST 11, 2026

Privacy Policy

This policy explains how the Presence beta service and Presence for Chrome extension operated by Arron Hartt collect, use, share, retain, and delete information.

Information collected

Presence stores basic profile information supplied by your sign-in provider; labels and encrypted credentials for calendars you connect; calendar information needed to calculate status; manual overrides; custom status labels, messages, colors, durations, and selected core behaviors; named places and sharing choices; browser-extension device labels and limited meeting, recording, or streaming state; organization membership; public and device-link settings; limited analytics; and requests you submit.

Custom statuses

You may save custom status names, short messages, colors, default durations, and a selected core Presence behavior. When you activate one, its name, message, and color may appear anywhere you have chosen to share your status, including private family links, device and office displays, Reception and Group Views, and a connected TRMNL output. The selected core behavior—not the custom wording—continues to control compatible Digital Knock, Alexa, integration, analytics, and recap behavior. Do not put confidential, medical, financial, or other sensitive information in a custom status intended for shared views. You may delete a saved custom status from the dashboard.

Calendar information

Presence uses read-only access to calculate whether you are available, busy, approaching a meeting, focused, recording, or out of office. Event titles may be evaluated privately to classify a status. For an organization owner-designated team Out of Office calendar, Presence may transiently compare an event creator email or an owner-confirmed name term against organization members so it can mark only the intended person Out of Office. Invited attendees are never assumed to be out merely because they received an invitation. Event titles, descriptions, attendees, meeting links, and calendar names are not returned through public pages, display pages, Reception Views, or the TRMNL endpoint. Presence does not edit calendar events.

Microsoft Teams availability

If you connect an eligible Microsoft work or school account and approve presence access, Presence reads your own Teams availability and activity, such as available, busy, in a meeting, on a call, presenting, or away. Presence uses that signal only to calculate the simplified status shown through the service. It does not request organization-wide presence, messages, meeting names, participant lists, call identities, call content, recordings, audio, or video.

Zoom and Webex availability

If you connect Zoom or Webex, Presence stores encrypted OAuth credentials and periodically reads your own account's simplified presence or status. Presence uses that signal only to calculate your displayed availability. It does not request Zoom or Webex meeting names, participant lists, chat, recordings, transcripts, call identities, call content, audio, or video. You can disconnect either service from the dashboard.

Google API data

When you explicitly connect Google Calendar, Presence requests read-only access to your calendar list and events on the calendars you select. Calendar names and identifiers are used to present and remember your selection. Presence receives event start and end times, availability and cancellation state, event type, event title, creator email, the connected user's own response state, and whether conferencing information exists. Presence does not request attendee email addresses for this feature. This raw data is processed transiently to classify current and upcoming availability, recognize native Google Out of Office events, and—only for a calendar explicitly designated by an organization owner—match a team OOO event to its creator or an owner-confirmed name term. Presence stores encrypted OAuth access and refresh credentials, the connected Google account label, selected calendar identifiers, the designated OOO calendar identifier, and confirmed name terms, but does not persist copies of Google Calendar events, titles, descriptions, attendee lists, or meeting links in its database.

Presence uses Google Calendar data only to provide and improve the user-facing live-status, meeting-soon, focus, recording, out-of-office, display, and sharing features the user chooses. Derived output is limited to a simplified status, generic message, and expected change or return day; raw calendar content is not disclosed through shared views. Presence does not sell Google user data, use it for advertising or advertising profiles, use it for credit or lending decisions, or transfer it to data brokers or advertisers.

Presence does not use raw, aggregated, anonymized, or derived Google Workspace API data to develop, improve, or train generalized AI or machine-learning models. It does not transfer Google Workspace API data to third-party AI or machine-learning services for model training. Presence's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Chrome meeting, 3CX, recording, streaming, and Digital Knock extension

The extension checks whether Google Meet or Microsoft Teams in-call controls, or supported YouTube Live Control Room, StreamYard, Riverside, and Restream Studio recording or live controls, are active. A user may also explicitly approve their own 3CX web-client site; on that approved origin the extension checks only whether a visible end-call control indicates an active call. It sends only start/end state, the supported service name, and whether an active studio mode is recording or live. Its popup can also send a temporary status and expiration that you explicitly choose. If you enable Digital Knock, the extension may retrieve the requester name and random request identifier for an active Reception View request and display a Chrome notification while your status is Available or Available if needed. Your acceptance or decline is returned to the Reception View and disappears there after a short period. Presence stores a random device identifier, a Chrome-profile label you choose, extension version, last check-in, limited active state, and short-lived Digital Knock request and response records. It does not request your Chrome profile email or collect caller names, phone numbers, contacts, meeting or broadcast titles, attendees, guests, destinations, chat, general browsing history, recordings, audio, or video.

Mac call companion

The optional Mac companion observes an on-device Continuity activity label indicating that a nearby iPhone call has started or ended. It sends only that boolean call state, a random device credential, a user-visible device name, and a last check-in time. It does not access or transmit caller identity, phone numbers, call history, microphone data, conversations, or audio. The feature is experimental because Apple does not document this Continuity signal as a public API.

Focus App automation

You may choose and confirm one application on a connected Mac and select a one, five, or ten-minute sensitivity. The Mac companion sends the confirmed application name and bundle identifier, whether that selected application has remained frontmost long enough to trigger Focus, and connection health. Presence does not collect window titles, document or spreadsheet names, file contents, keystrokes, mouse activity, screenshots, screen content, lists of other open applications, app-usage history, or productivity scores. The automation can be paused without removing the selection, and the selected app can be changed or deleted from the dashboard.

Todoist Focus integration

The optional Todoist UI Extension lets a user start a timed Focus status from a Todoist task. Todoist supplies a short-lived authorization token and account identity so Presence can verify that the request belongs to an approved Presence user; Presence uses that token only for immediate verification and does not store it. Presence uses only the requested Focus duration. Although Todoist may include the current task or project in its extension request, Presence deliberately ignores and does not store task names, projects, descriptions, labels, due dates, comments, attachments, or task history. The integration currently runs in Todoist web and desktop clients and can be removed from the user's Todoist integration settings.

OBS Studio connection

The optional Mac companion can connect to OBS Studio's local WebSocket server on the same computer. It reads and sends only whether OBS is connected, recording, or streaming. The OBS WebSocket password remains on the Mac and is never sent to Presence. Presence does not access scenes, sources, cameras, microphones, audio, video, recordings, broadcast destinations, stream keys, titles, or chat.

VoIP, 3CX, and work-phone connections

Optional VoIP connections receive only call-state events, a provider label, a one-way hash of the provider's call identifier, and a last-event time. For the optional 3CX Direct API beta, a connector operated on a customer-controlled computer uses a customer-created 3CX API client to read whether the specifically configured extension has a connected participant. The 3CX PBX address, client ID, API secret, and raw participant records remain on that computer and are not sent to or stored by Presence. Presence deliberately ignores and does not store caller names, caller or destination phone numbers, contacts, recordings, transcripts, conversations, or audio. Private webhook URLs act as device credentials and should be replaced if exposed.

Amazon Alexa beta

If you link the optional Alexa beta, Presence stores encrypted connection credentials and provides Alexa with a simplified availability signal and the spoken status you request. Alexa routine triggers may identify statuses such as Available, In a Meeting, On a Call, Focus, Recording, Busy, or Away. Presence does not send Amazon calendar titles, meeting descriptions, attendees, caller information, email, location, audio, video, or conversation content. Routine actions and connected smart-home devices are configured and operated through the user's Amazon Alexa account. You can disconnect Alexa from the Presence dashboard and may also need to disable the Presence skill in the Alexa app.

Named places and location

You can name places such as “Studio,” enter an address, and choose a geofence area. Presence sends address searches to Google Maps Geocoding, then encrypts the saved address and geofence coordinates at rest. When you tap “Share my place” and approve the browser prompt, the browser sends one current-location reading so Presence can match it against your saved areas. That reading is not stored as location history. Presence stores only the matched place, your sharing choice, and its expiration. There is no continuous or background tracking, and shared views receive only the place name—never its address or coordinates.

Organizations and groups

If you voluntarily join an organization, its Reception View or a Group View may show your name, profile image, simplified status, group membership, group role, broad workplace label, expected availability, and an optional scheduling link you provide. If you enable Digital Knock, a visitor may provide a short name and ask to talk only while your status is Available or Available if needed. Requests expire automatically, are rate limited, and do not include a free-form message. Group-lead labels organize a view; they do not provide access to private calendar or activity information. You can disable Digital Knock, remove your scheduling link, or opt out of Reception View from your dashboard. Meeting titles, attendees, calendar names, precise location, productivity scores, hours worked, and activity histories are never included. Anyone with an enabled Reception View or Group View link can open it, so organization owners must share those links only with authorized people.

Presence is designed to answer whether now is a good time to communicate, not to measure productivity, attendance, performance, or time at a location. An organization is responsible for giving its members any legally required workplace notices and obtaining any legally required permission before using Presence. Members can control whether they appear on an organization board and can review the information their organization view is permitted to show about them.

Scheduling links open the third-party scheduling service chosen by the user. Presence does not control that service's availability rules, booking flow, privacy practices, confirmations, cancellations, or data handling.

Organization invitations

When an organization owner invites you, Presence stores your email address, the inviting organization and person, selected starting groups and roles, a random invitation token, and its expiration and acceptance status. Invitations expire after seven days and can be cancelled by the organization owner. You must sign in using the exact invited email address before accepting.

How information is used

Information is used to authenticate accounts, maintain connections, calculate and display statuses, operate organizations and shared views, respond to requests, detect abuse, diagnose errors, maintain security, and understand product adoption. Presence does not sell personal information, calendar information, extension activity, or location labels.

Private weekly recaps

If weekly recaps are enabled, Presence keeps a limited timeline containing your simplified status, its general source, selected status personality, and observation times. It does not add calendar titles, descriptions, participants, caller information, file names, application content, conversations, audio, video, precise location, or productivity scores to that timeline. Presence uses the timeline only to estimate time in broad statuses, choose the personality style used most during the week, and email a private recap to your own account address through Resend. Recaps are not sent to an organization, manager, team, or Reception View. You can turn weekly recaps off from the dashboard.

Service providers and disclosures

Information may be processed by providers needed to run Presence, including Render and PostgreSQL hosting, Google and Google Maps, Microsoft, Amazon and AWS when you enable Alexa, Todoist when you enable its Focus integration, calendar providers you select, Resend, GitHub, Google Analytics, and a future payment processor. Information may also be disclosed when reasonably necessary to comply with law, protect users or the service, investigate abuse, or complete a business transfer subject to appropriate protections.

Public and device links

Public status, display, Reception View, and Shortcut links contain unguessable tokens but should be treated like private links. Anyone possessing an enabled viewing link can see the simplified information authorized for that link. Anyone possessing a Shortcut action link may be able to change its associated status or place signal. Replace or disable a link if it may have been exposed.

Analytics

Presence records limited product analytics including page views, referral source, campaign tags, account activity, connection counts, and approximate state or region and country. When the hosting network does not supply a region, Presence may send the request IP address to an IP geolocation provider solely to obtain a country and state or region. Presence does not retain that raw IP address or request city-level or precise-location fields. Cities, precise coordinates, calendar titles, and meeting details are not stored in internal analytics. Internal analytics are available only to the Presence owner and are retained for up to 13 months.

The public homepage also uses Google Analytics 4, which can process page views, device information, general location, and referral information under Google's terms. Presence does not intentionally send calendar data, connection data, shared statuses, requests, or CEO-dashboard activity to Google Analytics.

Retention

Account and integration information is retained while your account is active and as needed to provide requested features. Google Calendar events are fetched when Presence calculates status and are not retained as event records after that calculation; encrypted Google OAuth credentials remain until you disconnect Google Calendar or delete your account. Manual overrides expire automatically. Saved custom statuses remain until you delete them or your account. The limited status timeline used for weekly recaps is retained for up to 30 days. Delivery records are retained to prevent duplicate emails and rotate recap writing. Internal analytics are retained for up to 13 months. Error records are retained only as needed to diagnose and secure the service. Limited records may remain when required for security, fraud prevention, legal compliance, dispute resolution, or in encrypted backups until those backups expire.

Your privacy rights and choices

You may ask to access, correct, delete, or receive a portable copy of personal information associated with your account. You may disconnect integrations, withdraw optional sharing, replace private links, opt out of an organization board, and object to or restrict certain processing where applicable law provides that right. Presence does not sell personal information or precise location information and does not use personal information for targeted advertising. Where applicable law provides an appeal right, you may appeal a denied privacy request by replying to the decision or emailing the address below with “Privacy appeal” in the subject line. Presence will verify requests as reasonably necessary and will not discriminate against a user for exercising applicable privacy rights.

Account deletion and provider access

You can disconnect calendars, disable or replace public links, opt out of an organization board, remove devices, and permanently delete your account from the dashboard. Account deletion removes your profile, encrypted calendar credentials, statuses, places, device links, organization membership, and requests stored under your email. Presence attempts to revoke connected Google access before deletion. Because Microsoft, Zoom, or Webex may require the user or an organization administrator to remove an authorization directly, the deletion confirmation provides a checklist for reviewing those provider accounts after deletion. Previously anonymized analytics and short-lived encrypted backups may not be immediately identifiable or removable.

Security

Presence uses HTTPS, encrypts provider credentials and private calendar-feed URLs at rest, limits shared views to simplified information, and monitors service health and errors. No online service can guarantee absolute security. Notify Presence promptly if a private link, device action, or account may have been compromised.

Children

Presence is not directed to or offered for use by children under 13. A child under 13 may not create a Presence account or submit personal information to the service. If Presence learns that it collected personal information directly from a child under 13, it will take reasonable steps to delete it.

Changes and contact

Material changes will be posted here with a revised date. Privacy, access, correction, deletion, appeal, and security requests may be submitted through the Presence contact form or emailed to presence@arronhartt.com. A business mailing address will be added when available.