Privacy Policy

This policy explains how WorkplaceSignatures (orgsigs.com, "we", "us") handles personal information. WorkplaceSignatures is operated by SQUEEZEIT LLC, doing business as OrgSigs, 2250 Grand Ave, Baldwin, NY 11510, United States.

WorkplaceSignatures is a business service: a company (our "customer") connects its directory so that every employee gets an email signature built from their directory profile. For the employee and directory data a customer brings, the customer decides what is processed and we process it on their behalf and on their instructions. For our own website, accounts and billing, we decide how the data is used.

#Information we collect

#Directory data

When a customer's administrator connects Google Workspace, Microsoft 365 (Microsoft Entra ID) or a SCIM identity provider such as Okta, OneLogin or JumpCloud, we read, with read-only permissions, the profile fields a signature can use:

• name, work email address and email aliases
• job title, department and employee ID
• work and mobile phone numbers
• office location (city, state or region, country)
• profile photo
• manager, and group or organizational unit membership
• whether the account is active or suspended

We only read user profiles, groups and the organization's verified domains. We do not read email content, calendars, files or contacts.

#Information people give us

• Account information: name, email address and password (stored only as a hash by our authentication provider) of administrators and members, or the identity returned when they sign in with Google or Microsoft.
• Signature content: templates, logos, banners, links, disclaimers and any profile fields an administrator or employee edits in the app.
• Billing details: company name, billing address and tax details. Card details are entered directly with our payment processor; we never see or store full card numbers.
• Support requests and messages you send us, including questions you type into the help assistant.

#Information collected automatically

• Usage and security records: sign-ins, audit log entries for privileged actions, directory sync results and signature deployment status.
• Campaign banner clicks: when a recipient clicks a banner in a signature, we count the click for the employee who sent the email. We do not identify the recipient.
• Server logs: our hosting provider records standard request data (IP address, browser user agent, time and page requested) to run and secure the service. Images in signatures are fetched from our servers by mail clients; we do not use them to track whether an email was opened.

#How we use information

• To provide the service: build signatures from directory data, keep seats in step with the directory, deploy signatures to Gmail and Outlook, and show analytics to the customer.
• To secure the service: authenticate users, enforce two-factor authentication, prevent abuse and keep an audit trail.
• To bill customers and send service emails (invitations, sign-in links, sync failures, receipts and, if you opt in, product update digests).
• To answer support requests.

We do not sell personal information, we do not use it for advertising, and we do not use customer data to train AI models.

#Google user data

Our 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.

When a Google Workspace administrator connects their organization, WorkplaceSignatures requests these Google scopes:

• https://www.googleapis.com/auth/admin.directory.user.readonly: to read user profiles (the directory fields listed above) so we can build each person's signature and keep seats in step with the directory.
• https://www.googleapis.com/auth/gmail.settings.basic: to read and update the signature setting of each user's Gmail send-as addresses. We do not read, send, modify or delete email messages.

When someone signs in with Google, we receive their name, email address and profile picture to create and secure their account.

Specifically, data we receive from Google APIs:

• is used only to provide and improve the user-facing features described above (signature building, directory sync and signature deployment);
• is not transferred to others except as needed to provide those features (through the service providers listed below), to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to users;
• is not used or transferred for serving advertisements, including retargeting, personalized or interest-based advertising;
• is not sold, and is not used to determine creditworthiness or for lending purposes;
• is not used to develop, improve or train generalized artificial intelligence or machine learning models;
• is not read by humans, except with the user's or customer's affirmative agreement (for example a support request), when necessary for security purposes such as investigating abuse, to comply with applicable law, or when aggregated and anonymized for internal operations.

#Microsoft and SCIM data

For Microsoft 365 we use the Microsoft Graph application permissions User.Read.All, GroupMember.Read.All and Organization.Read.All (read-only) for the same directory fields and to verify the organization's email domains. The Outlook add-in inserts the signature into the message being written and does not send message content to us. SCIM identity providers push the same profile fields to us. We use this data only to provide the service, under the same commitments as Google user data above.

#Service providers (sub-processors)

We use these providers to run WorkplaceSignatures. Each processes data only to provide its service to us:

Provider	Purpose	Data
Supabase	Database, authentication and file storage	All service data, including directory data and uploaded images
Vercel	Application hosting, content delivery and server logs	Request data; all data passes through it in transit
Vercel AI Gateway, with Anthropic as model provider	The help center assistant, and drafting company pages for our own sales outreach	The questions you type into the assistant and help center text; for company page drafts, a prospect company's name, public website text and our staff's notes
Resend	Sending service emails	Recipient email address, name and email content
Stripe	Payments, invoices and tax	Billing contact, billing address and payment method
Google and Microsoft	Directory access and sign-in, when a customer connects them	Data the customer's own directory already holds

We will update this list before adding a provider that processes customer data.

#Retention and deletion

• While a workspace is active, we keep its data so the service works. People who leave the directory lose their seat; their records stay with the workspace's seat history until the workspace is deleted or the customer asks us to remove them.
• Records of completed sync jobs are deleted after 30 days.
• After a customer cancels, the workspace and its directory data are permanently deleted, normally within 24 hours and at most 7 days. A workspace suspended for non-payment is deleted after 90 days unless reactivated.
• Invoices and payment records are kept as long as tax and accounting law requires.
• Backups roll off on our database provider's schedule, typically within 30 days of deletion.
• Disconnecting Google Workspace, Microsoft 365 or SCIM stops all further reads immediately. A Google Workspace administrator can also remove our access at any time in the Admin console (Security → API controls → Domain-wide delegation), and a Microsoft administrator in Entra ID (Enterprise applications).

Administrators can export their data at any time from Settings → General → Export data.

#Cookies

We use only cookies that the service needs: the sign-in session, the "keep me signed in" choice, the workspace you last opened, the sign-in method you last used and small interface preferences such as a collapsed sidebar. We do not use advertising cookies or third-party analytics cookies, so there is nothing to opt out of. Blocking cookies will stop you from signing in.

#Security

Data is encrypted in transit and at rest. Row-level security keeps every workspace's data separate, API and SCIM tokens are stored only as hashes, and every privileged action is recorded in the customer's audit log. Support staff only enter a workspace for a stated reason, for a limited time, with two-factor authentication, and every visit is visible to the customer. More detail is in Security and privacy.

#Your rights

Depending on where you live, you may have the right to access, correct, delete or export your personal information, or to object to or restrict how it is used. If you are an employee of one of our customers, your employer controls your directory data: please contact them first, and we will help them respond. Otherwise email us at hello@orgsigs.com and we will respond within 30 days. You may also complain to your local data protection authority.

#International transfers

We and our providers are based in the United States, so your information may be processed there. Where the law requires it, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses.

#Children

WorkplaceSignatures is a business service and is not directed to children under 16. We do not knowingly collect their information.

#Changes to this policy

We will post any change on this page and update the date above. If a change materially affects how we use personal information, we will tell workspace owners by email before it takes effect.

#Contact

Questions about this policy or your data: hello@orgsigs.com, or SQUEEZEIT LLC (OrgSigs), 2250 Grand Ave, Baldwin, NY 11510, United States.