APPLICATION PRIVACY
Application privacy notice
This notice explains how Spearis Marketing, based in Miami, Florida, handles information in its business automation application at app.spearismarketing.com. It is separate from the public marketing website's privacy policy.
Information the application handles
- Business setup: business name, review link, timezone, message templates, scheduling choices, and workflow approvals.
- Google account information: account identifier and email address used to verify the authorized connection, granted permissions, and authorization tokens used to maintain that connection. Google handles Google sign-in; the application does not receive your Google password.
- Completed-job information: spreadsheet identifiers, tab names and headings, and row data read from configured source ranges. This can include job identifiers, customer names, email addresses, completion dates, status, language preference, and permission indicators. Include only data needed for the service in the configured tab; other cells in a fetched range may also be processed during mapping or preview.
- Operational records: permission evidence, opt-outs, source snapshots, schedules, email content and recipients, sending attempts, provider responses or identifiers, exceptions, and audit history.
- Access and technical records: operator and invited client account email addresses, business assignments, password hashes (not readable passwords), invitation and revocation records, setup confirmations, sign-in and session information, request and service logs, and technical information processed by hosting providers to operate and secure the service.
Google permissions and purpose
Google identity permissions identify the account giving consent. Gmail send-only permission lets the application send the configured initial post-completion email and an explicitly initiated owner-mailbox test. It does not grant permission to read, modify, or delete inbox messages. Spearis does not use this connection to read incoming replies.
A separate agency connection requests access to specific files selected through Google Picker (the drive.file permission). Google permits viewing and changing those selected files within the authorized account's existing rights; Spearis uses the connection only to read configured spreadsheet sources, not to create, edit or delete files. Client spreadsheets should be shared with the agency account as a Viewer. The application does not request access to all Drive files. A short-lived file-access token is provided to Google Picker in the signed-in operator's browser; refresh tokens and the OAuth client secret remain server-side.
Spearis uses this information to configure and deliver the agreed service, confirm account identity and permission, prevent duplicate or unwanted messages, apply pauses and opt-outs, resolve failures, and maintain operational and security records.
Optional Google Calendar connection
A separate read-only connection retrieves calendar identifiers, names and access roles to verify that the configured calendar is readable. It reads event identifiers, titles, descriptions, dates, times, recurrence and cancellation information from that calendar within a configured date window. Descriptions may include customer names, phone numbers and appointment notes.
Google's permissions can cover calendars accessible to the connected account. Spearis limits event reads to the calendar configured for the business and the requested date window. Some nonmatching events are processed to apply the operator's filters. Matching events are saved as appointment records, including names, phone numbers, times and status; the current hosted preview does not retain complete event descriptions. Refreshing the preview updates saved records and identifies cancellations or events that no longer match.
Calendar authorization tokens are encrypted server-side, separately from Gmail and spreadsheet grants. Saved appointments are stored in the Render-hosted database and scoped to the business. Authorized Spearis operators and invited users assigned to that business can review the appointment information within their permitted access. Spearis does not create, edit or delete Google Calendar events through this connection and does not send Calendar data to AI providers.
Importing an appointment or finding a phone number in an event does not grant permission to text that person. Messaging requires separate recipient permission and service activation. The hosted Calendar preview uses fictional verification data and has texting disabled.
Revoking Google access stops further authorized reads but does not automatically delete stored appointments. The retention and deletion process below also applies to Calendar data and authorization records.
Limits on use and sharing
Spearis Marketing's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Google user data is not sold, used for advertising or unrelated marketing, or used to train generalized artificial intelligence or machine-learning models. The email service does not send Google user data to an AI model.
Authorized Spearis personnel access information only as needed to provide support with permission, operate the requested service within permitted access, investigate security or abuse, or meet applicable legal obligations. Google user data is not browsed for unrelated purposes.
Google processes account authorization, spreadsheet and Calendar requests, and email delivery. Render hosts the application and its database. These providers process information needed to supply their services. Email recipients and their mail providers receive the content addressed to them. Spearis may disclose information where required by law or necessary for security, subject to the restrictions applicable to Google user data.
Social Content service
When a business uses Social Content, Spearis stores its content profile, uploaded media references, notes, permission confirmations, caption versions, approvals, schedules and publishing results. Photos and videos are stored privately in Cloudflare R2 under client-specific references. Short-lived links allow authorized viewers to retrieve selected media. At an approved photo’s publishing time, a separate unguessable link makes only that exact image available to the publishing provider for up to seven days; the media library remains private. Withdrawing permission or archiving the client revokes this link.
When a Spearis operator requests AI drafting or photo-batch preparation, the approved brand brief, relevant written context and reduced-size copies of permitted photos may be sent to OpenAI to describe visible content and suggest captions and layouts. This feature does not read Gmail or use customer spreadsheet records. Photo observations are recorded separately from verified business facts. Inspiration-only files are excluded from automatic publishing selection. Generated wording requires human review; it is not published automatically. Spearis requests that generated responses are not stored through the API response-storage option; provider security retention may still apply.
Buffer receives the approved captions and temporary media links to publish to the business's configured social channels. Published content is visible according to those channels' settings. Withdrawing permission or pausing Spearis stops future handoffs but cannot recall a post already handed to Buffer; removal may require action in Buffer or the social account.
Optional Square connection
When a business authorizes Square, Spearis receives account and location identifiers, authorization tokens and the permitted customer, booking, service/catalog, order, payment and refund information needed to check the connected source. Square handles sign-in; Spearis does not receive your Square password. Read-only API permissions do not authorize changing appointments, charging customers or using Square Messages.
Spearis stores encrypted source snapshots and authorization tokens in its Render-hosted database, scoped to the connected business. Authorized Spearis operators can refresh the source and review connection activity. This connection does not send Square customer records to an AI provider or grant permission to contact a customer.
Disconnecting in Spearis blocks further reads and requests revocation from Square. If revocation cannot be confirmed, access remains blocked locally and the application displays the pending revocation. Historical snapshots and audit records remain subject to the retention and deletion process below. Contact Spearis for deletion or access questions.
Optional Inbox phone notifications
If you enable phone notifications, Spearis stores an encrypted browser push subscription, device label, account and business association, and notification outcomes. Your browser's push provider (Apple, Google or Mozilla) processes the notification delivery. Alerts contain generic Spearis text and a link requiring sign-in; customer names, phone numbers and message contents are not included in the alert. The application does not cache Inbox content for offline use.
You can turn off a device in Phone notifications or revoke permission in your browser or phone settings. Signing out disables devices enrolled in that session. Subscriptions expire after 90 days; expired or revoked subscription secrets are cleared, and notification outcome records are removed after 30 days. These settings do not change customer SMS permission or subscription choices.
How we protect Google user data and other sensitive information
Spearis uses technical access controls and encryption to protect Google account information, authorization credentials, imported Calendar appointments and configured spreadsheet records. The hosted application stores service records in its Render-hosted database. Our safeguards include:
- Protection in transit: HTTPS encrypts information exchanged between your browser and the hosted application. Connections to Google's authorization and API endpoints also use HTTPS.
- Encrypted authorization credentials: saved Google access and refresh tokens are encrypted before they are written to the database, using AES-256-GCM. Encryption keys are held separately in server hosting configuration. Calendar credentials use a separate encryption key from Gmail and spreadsheet credentials. Google refresh tokens and the OAuth client secret remain server-side.
- Restricted access: private records require a signed-in account. Server-side checks restrict invited client accounts to their assigned business and permitted features. Calendar connection setup is restricted to authorized operators; a client cannot select another business's credentials or records through a form.
- Protected sessions and authorization: hosted sign-in cookies are Secure and HttpOnly. Session checks and request-validation controls protect authenticated actions. Calendar connection callbacks must match the initiating session and a short-lived, single-use authorization state.
- Limited Calendar collection: event reads are limited to the configured calendar and date window. Filters determine which appointments are saved; the hosted Calendar preview does not retain complete event descriptions. Calendar permission is read-only and does not authorize editing events.
These controls protect access to stored service records; the token-specific encryption described above does not mean that every service record is separately encrypted by the application. Authorized access is limited to the purposes described in this notice. No system can guarantee absolute security.
Revoking a portal account does not itself disconnect Google or pause an automation; contact Spearis for those changes. Google access revocation and service-data deletion are described below.
Retention, disconnection, and deletion
Information is retained as needed to provide the service and maintain permission, suppression, duplicate-prevention, audit, security, and legally required records. The application does not currently apply a universal automatic deletion period. Disconnecting Google does not automatically delete previously stored job or activity records.
You can revoke Google access using Google Account connections. You can also ask Spearis to pause the service, disconnect an account, correct information, or delete service data by emailing spearismarketing@gmail.com. We verify the requester's authority and review what can be removed, what must be retained and why, and any applicable backup retention. Revoking access stops further authorized Google API access; it does not recall email already sent.
Business and recipient requests
Businesses are responsible for supplying accurate job data and appropriate permission for the messages they request. Customers may contact the business that sent their message or Spearis with questions or opt-out requests. This service is intended for businesses and is not directed to children.
We may update this notice when the service or its practices change. Questions and requests can be directed to Spearis Marketing, Miami, Florida, at spearismarketing@gmail.com.