Silver Owl JournalAnalysis & editions
← Back to home

Privacy Policy

Last updated: October 13, 2026

This Privacy Policy is provided by Silver Owl Studio LLC ("Silver Owl", "we", "us"), 7901 4th St N, Ste 300, St. Petersburg, FL 33702.

This notice covers the marketing website, optional Journal reader-account features when enabled, project enquiries and the support interactions described below. Reader-account features may be available in a protected review version. Browsing the website does not create a Silver Owl Workspace account. A separate application or customer deployment needs a notice that describes its actual accounts, records, connections and data handling; this website notice is not a complete description of every proposed workspace feature.

What we collect

When you submit the contact form on this website, we collect your name, email address, and the message you provide. We may also collect a budget range, company details and a project timeline if you choose to provide them.

The current marketing website does not load an analytics service or advertising trackers. Our hosting provider processes technical request information to deliver and protect the site.

How we use your information

Contact form submissions are used to respond to your inquiry and discuss a potential project. Our email workflow uses Microsoft Azure Communication Services. If customer-management integration is enabled, enquiries are stored using Supabase and may be passed to our Mahon customer-management system. Our service providers process this information on our behalf as described below. We do not sell or rent your personal information.

If we begin working together, we may retain project-related communications for business record-keeping purposes.

Journal reader accounts

Optional reader sign-in uses the shared Silver Owl identity service through Supabase. The enabled options shown may include Google, Apple or an emailed sign-in link. Supabase processes the identity and session information needed to sign you in; Google or Apple also processes your sign-in when you choose that provider. Reader sign-in does not grant customer-workspace or editorial access.

When reader storage is enabled, the reader features can store your account identifier with your chosen display name, saved article identifiers, edition preferences and a history of preference changes, including related timestamps. These records support your profile, reading list and preference history. Signing in alone does not confirm that reader storage is available or create a newsletter subscription.

Workspace data and AI services

The proposed workspace brings business information into areas such as customers, content, research and, where included, finance and purchasing. The data used depends on the features and connections actually enabled for that deployment. Do not send customer records, financial account details, health information, passwords or access tokens through a general enquiry form.

Before sensitive information is connected to an AI workflow, the applicable notice and written scope need to identify the model and service providers, what information they receive, processing locations, retention and any use for model training. Hosting a model in your own environment does not by itself keep all data there: external tools, communications and integrations may process information elsewhere. This explanation does not authorize new uses of information already collected or change our existing privacy and confidentiality commitments.

Email communications

Contact emails respond to your inquiry or relate to an active project. Journal newsletter signup is not yet open. When it opens, newsletter subscriptions will require email confirmation and include an unsubscribe option.

Email sign-in links authenticate your account. Newsletter signup is separate: signing in or saving edition preferences does not enroll you in newsletter delivery.

Text messaging (SMS)

If you text our support number, +1 (681) 441-3286, we collect your mobile number and the content of your messages, and use them only to answer your question or support request. Replies may be generated with the help of an AI assistant; requests that need a person are forwarded to our team by email.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. Our messaging provider (Twilio) processes messages only to deliver them on our behalf.

Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. See the SMS program terms.

Third-party services

The services below support the website or the optional interaction identified. Listing a provider does not mean every visitor uses it or every integration is enabled:

  • Vercel — hosting and infrastructure. Privacy policy
  • Microsoft Azure Communication Services — email delivery for contact form submissions and reader sign-in links when email sign-in is enabled. Privacy policy
  • Microsoft Azure Database for PostgreSQL — Journal profiles, saved article identifiers, edition preferences and related audit records when reader storage is enabled. Privacy policy
  • Supabase — reader identity and session processing when sign-in is enabled, and enquiry storage when customer-management integration is enabled. Privacy policy
  • Twilio — SMS and voice delivery for our support line. Privacy policy
  • Calendly — scheduling tool. Used only if you choose to book a call. Privacy policy

Data retention

Contact form submissions are retained for 12 months. To request deletion of contact form submissions, email info@silverowl.dev and we will delete them within 30 days.

When Journal reader storage is enabled, we retain your profile, saved article identifiers and current edition preferences until you request deletion. Email info@silverowl.dev to request deletion of your Journal reader data. After verifying the request, we erase those active records and their detailed preference history within 30 days. Preference change history is otherwise retained for 90 days. Minimal records of verified deletion and related security or audit activity are retained for 90 days; reader database backups expire within 35 days.

Deleting Journal reader data does not automatically delete your shared Silver Owl sign-in identity or records in other Silver Owl applications. Later use of reader features can create new reader records. If a reader database backup is restored, completed deletions must be reapplied before reader storage is made available again.

Security

This website is served over HTTPS. Contact form submissions are transmitted securely. We do not store payment information — all payments are processed through Stripe or bank transfer.

Your rights

You have the right to request access to, correction of, or deletion of any personal data we hold about you. Contact us at info@silverowl.dev.

Cookies

This marketing website does not set advertising or analytics cookies. Optional reader sign-in uses necessary host-only cookies marked HttpOnly and Secure on this HTTPS site. Your display preference may be stored locally in your browser. See our Cookie Policy for the current site scope and links to third-party services.

Questions about a particular deployment

If you use a Silver Owl application through an organization, ask the organization and Silver Owl for the notice and contact route that apply to that workspace. The project must identify who handles access, correction and deletion requests for its records.

Changes to this policy

If we make material changes to this policy, we will update the date at the top of this page.

Contact

Questions about privacy: info@silverowl.dev

Join our newsletter ↗