Organicaly
Search Engine OptimizationContent MarketingAI VisibilityCommunity EngagementFeed & CatalogMarketplace VisibilityOrganic SocialClient PortalPricingCompanyCareersBlog
Sign inGet a Free Audit
Legal

Privacy Policy

Last updated October 1, 2026

This Privacy Policy explains how Organicaly ("Organicaly", "we", "us") collects, uses, stores, shares, and deletes information in connection with the Organicaly platform and the Organicaly app for Shopify (the "Service"). By connecting a store or using the Service, you agree to the practices described here.

Who we are

Organicaly provides SEO, content, and online-store optimization software used by businesses and by agencies on behalf of their clients. When a merchant connects a Shopify store, Organicaly acts as a data processor that carries out the store-content changes the merchant or their agency requests.

Store data we access

When you install our Shopify app and approve access, we access only the catalog, content, and online-store resources needed to operate the Service on your behalf:

  • Store profile and settings (store name, primary domain, locales, markets, locations).
  • Products, variants, collections, and product media (including image alt text).
  • Pages, blog articles, and their SEO fields.
  • Online-store metadata: SEO titles and descriptions, metafields, metaobjects, URL redirects, navigation menus, and translations.
  • Theme information and, where you enable it, theme files used for SEO output.
  • Store performance and analytics reporting used to measure the impact of changes.

Our Shopify app does not request or access your customers' personal information, orders, checkout, or payment data. We do not hold any customer records from your store.

Account and connection data

To connect your store we store the store's myshopify.com domain and an access credential issued by Shopify so the Service can make the content changes you request. Access credentials are encrypted at rest. We also keep a log of connector activity (for example, which content items were created or updated) so changes can be reviewed and rolled back.

Google user data

If you connect a Google account to Organicaly (Google Search Console, Google Analytics or Google Merchant Center), you approve each connection on Google's consent screen, and we access only what that connection needs:

  • Search Console (read-only): the sites you've verified, and search performance for the site you choose (queries, pages, clicks, impressions and position), URL inspection results and sitemaps.
  • Indexing (optional): when you ask us to, we submit URLs from your own site to Google for crawling.
  • Google Analytics (read-only): the list of your GA4 properties, and reports for the property you choose (for example sessions, landing pages, conversions and revenue).
  • Merchant Center: the list of accounts you manage and, for the account you choose, its products, product statuses and issues, data sources and performance reports. We write to your Merchant Center account only when you approve a specific change in Organicaly (for example an improved product title), and every change can be rolled back.
  • Your Google account's email address and account identifier, to show which account is connected.

How we use it. Only to provide the features you use in Organicaly: your dashboard, reports, recommendations, and publishing the changes you approve. We do not sell Google user data, use it for advertising, or use it to develop, improve or train generalized AI or machine-learning models. When we use AI providers to generate the recommendations and content you request, we use their business APIs, which do not train on the data we send. People at Organicaly do not read it, except with your permission, for security purposes, to comply with the law, or when it is aggregated and anonymized for internal operations.

Who we share Google user data with

We share, transfer or disclose Google user data only as needed to provide the features you use, and only with:

  • Our infrastructure providers, which host and store it on our behalf: Render (application hosting) and Supabase (database).
  • AI providers OpenAI and Anthropic, which process it through their business APIs to generate the recommendations, reports and content you request. Their API terms do not allow them to train their models on the data we send.
  • Other service providers that supply data for features you use, under contracts that limit their use of it to providing that service to us.
  • People you give access to your workspace, such as your team members or the agency managing your brand, who can see that brand's dashboards and reports.
  • Google itself, when you approve a change we write back to your Merchant Center account, or ask us to submit URLs for indexing.
  • Others only when required: to comply with the law or a valid legal request, to protect the security of the Service, or as part of a merger or acquisition, in which case this policy continues to apply.

We never sell Google user data, share it with advertisers or data brokers, or transfer it for any purpose other than providing and improving the features you use.

How we protect Google user data

  • Encryption in transit: all traffic to Organicaly and to Google's APIs uses HTTPS (TLS).
  • Encrypted credentials: the refresh token Google issues is encrypted with AES-based Fernet encryption before it is stored; the encryption key is kept outside the database, in our server's protected environment.
  • Encryption at rest: our database provider encrypts all stored data at rest.
  • Locked-down database access: every table denies access by default; only our application server, using a restricted service credential, can read or write Google data. Public and client-side keys cannot read it.
  • Access controls: every request requires sign-in; role-based permissions and per-brand isolation mean a user only sees the brands they're granted. Passwords are stored as salted PBKDF2-SHA256 hashes, and sessions use secure, HTTP-only cookies.
  • Least privilege: we request only the permissions each connection needs (read-only for Search Console and Analytics), and you choose which site, property and account we use.
  • Audit and staff access: automated actions are logged, and access to production systems is limited to authorized Organicaly staff.
  • Revocation and deletion: disconnecting stops our access immediately, and we revoke the authorization at Google once no brand in your workspace uses that Google account; stored data is deleted on request.

Storage. Report data we read is stored in our database so your dashboard can show trends over time.

Disconnecting and deletion. You can disconnect any Google connection on the Connections page at any time; we then stop reading your data, and revoke our access at Google once no brand in your workspace still uses that Google account. You can also remove Organicaly's access atmyaccount.google.com/permissions. To have stored data deleted, contact us at the address below.

Limited Use. Organicaly's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.

How we use information

  • To provide, operate, and secure the Service.
  • To perform the specific content, catalog, and SEO changes you or your agency request.
  • To measure the performance of those changes and report on results.
  • To communicate with you about the Service, including support.
  • To comply with legal obligations.

We do not sell your data, and we do not use it for advertising.

Service providers (sub-processors)

We share information with a limited set of service providers strictly to operate the Service, each bound by their own data-protection terms:

  • Cloud hosting and application infrastructure.
  • Managed database and storage.
  • AI providers used to generate and optimize content you request.
  • Web analytics (for example, Google Analytics) used to measure store traffic and performance.

We do not share your store data with third parties for their own marketing purposes.

Data retention and deletion

You can disconnect the Service or uninstall the app at any time. When you uninstall the app, we revoke and delete the stored access credential for your store. We honor Shopify's mandatory data-privacy webhooks, including customer redaction, customer data requests, and shop redaction: on a shop-redaction request we delete the connector's stored credentials, connection settings, publishing targets, connect telemetry, and the content records created for your store through the connector. Backups and logs are purged on a rolling schedule.

Your rights

Depending on where you live (including under the GDPR and the CCPA/CPRA), you may have the right to access, correct, export, or delete personal data we hold, and to object to or restrict certain processing. To make a request, contact us using the details below; where Organicaly acts on behalf of an agency or merchant, we will coordinate the request with them as the controller of the data.

Cookies

Our marketing website uses essential cookies and privacy-respecting analytics to understand site usage. It does not use advertising cookies.

International transfers

We and our service providers may process information in countries other than your own. Where required, we rely on appropriate safeguards for such transfers.

Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above.

Contact us

Questions or requests about this policy or your data:privacy@organicaly.ai.

Grow with us Organicaly

Optimize every channel your customers interact with.

Explore pricingGet a Free Audit
PlatformEnginePricingClient Portal
ChannelsSearch Engine OptimizationContent MarketingAI VisibilityCommunity EngagementFeed & CatalogMarketplace VisibilityOrganic Social
CompanyAboutCareersBlogContact
Organicaly
Privacy Policyorganicaly.ai · 2026