Review draft. This Shopify-specific privacy supplement is being prepared for review before public launch. It has not taken effect. It describes the current app behavior and identifies retention and deletion details that still need to be finalized.
Scope and responsibilities
Fennec Forms is operated by Adam Greenwell. The operator's mailing address is 4707 Perie Wood Lane, Kent, Ohio 44240, United States. Privacy and support inquiries can be sent to [email protected].
This supplement explains how Fennec Forms handles information when a merchant connects a Shopify store, staff use the app, or a visitor submits a Fennec form on the merchant's storefront. Read it with our Privacy Policy, Data Processing Summary, and proposed Shopify Merchant Agreement.
The merchant decides what their forms ask, why the information is needed, and how submitted requests are used. Fennec Forms hosts and processes responses on the merchant's behalf to provide the service. We separately handle Fennec account administration, support, security, and service operations as described in our general Privacy Policy.
Information from Shopify
The app processes the following information for the connected store:
- Store and installation information: the store's
.myshopify.comaddress, Shopify store identifier, authorized permissions, installation and access status, and the identifiers needed to keep the connection working. - Access credentials: app access and refresh credentials and their expiry information. These credentials are encrypted in storage and are not included in public forms or support messages.
- Staff connection information: a Shopify staff identifier linked to the staff member's Fennec account and workspace access. Pairing does not fetch the staff member's Shopify email address.
- Customer sync information: where the required permissions are available, customer identifiers and the customer name and email information needed to link a suitable response or review a name change.
- Privacy and uninstall requests: store, customer, request, and order identifiers supplied by Shopify, together with receipt and processing records we create to handle those requests.
The app does not import the store's full customer list, product catalog, carts, orders, or payment details for the Product Request workflow.
Information from merchants and staff
We process Fennec account details, workspace membership and permissions, form names and questions, product choices, conditional rules, publication settings, and requests reviewed through the app.
If you contact support, we receive the name, reply email, message, and context you provide. Shopify support context can include a store address, form name, and failed step. These entered details help us investigate; they do not establish that the requester owns the store or workspace.
Information from storefront respondents
We receive the answers submitted to the form, including contact details when the merchant asks for them. The current Shopify theme form does not support file-upload questions. Other Fennec form surfaces can collect uploads, and supported forms can collect signatures when enabled. The merchant controls the questions and should collect only what their stated purpose requires.
We also process technical and submission information, including submission time, IP address, browser information, the source of the request, form and store attribution, and identifiers used to prevent duplicate submissions and manage customer sync attempts. Enabled form analytics can record interaction events, completion time, location and device information, referrer, language, and campaign attribution. The information available depends on the form settings and workspace features.
A published form's name, identifier, Fennec service address, and publication status are stored with Shopify to support selection and display in the theme block. Respondents' submitted answers are not stored in those public form listings. The storefront loads the form from Fennec Forms, and submissions are stored in the merchant's connected Fennec workspace.
How information is used and shared
We use this information to authenticate store and staff access, connect the approved workspace, display forms, collect and review requests, provide customer sync, respond to support and privacy requests, and secure and maintain the service.
Authorized workspace members can review responses according to their permissions. A merchant can export responses or enable other Fennec features that send information to services they choose. Copies held by a merchant or a chosen recipient must also be considered when handling a privacy request.
Customer information sent to Shopify
For a suitable storefront response, the customer sync flow uses the submitted email address to look for an existing Shopify customer. It can link the response to that customer or create a customer using the submitted email and name. An existing customer's name change is presented for review before an authorized merchant applies it. The flow records the customer identifier and sync result, including information needed to investigate or retry eligible failures.
This flow sends name and email information rather than the full form response. Submitting a form or creating a customer record is not marketing consent; this flow does not set email or SMS marketing consent.
Merchants must provide the notices and obtain any consent required for the information they collect and send to Shopify. Shopify handles the information it receives under its own Privacy Policy and the merchant's agreements with Shopify.
Service providers and locations
Service providers help us host the app, store data and files, deliver email, monitor reliability, and prevent abuse. They may process information needed for those services. If the form's CAPTCHA protection is enabled, Cloudflare Turnstile processes the verification signals needed for that check. The general Privacy Policy describes the provider categories and relevant Fennec features.
The following services are confirmed in the current production configuration:
| Service | Purpose | Location and retention review |
|---|---|---|
| Laravel Forge-managed infrastructure | Application hosting, database, cache, sessions, and queues | The application, PostgreSQL, and Redis servers show New York 1. The underlying hosting contract, backups, and other retained copies still need verification. |
| Cloudflare R2 | Uploaded files and form assets | The configured S3 region value is auto; it does not establish physical location or jurisdiction. Dashboard buckets named for Fennec production and staging show Eastern North America (ENAM), Standard storage, and private access. Only a seven-day incomplete multipart-upload abort rule was observed; no completed-object expiry rule was observed. The effective production bucket mapping and retained-copy coverage remain unconfirmed. |
| Resend | Transactional email | The applicable account plan, provider deletion process, and retained email/backup copies remain under review. A sending region is separate from a storage location. |
| Sentry | Error monitoring | The applicable organization region, event categories, provider retention, and deletion process remain under review. |
| Cloudflare Turnstile | Abuse prevention and verification | Applicable processing locations, signal retention, and deletion assistance remain under review. |
| Google Workspace | The [email protected] mailbox |
The selected region, mailbox/Vault rules, forwarding, and retained copies remain under review. |
An enabled Chaskiq support-chat configuration also needs confirmation of its hosting arrangement and retention. Public form pages exclude the support chat. The named services above are a working inventory; identifying a service does not confirm its contractual safeguards or prove that all copies can be erased within a required deadline.
The provider list, processing locations, and any required international transfer safeguards for this Shopify offering are still being confirmed before publication. This draft does not promise that information remains in a particular country. Contact us if you need these details before using the app with personal information.
Cookies, analytics, and consent
Fennec account pages use session and security cookies. Fennec form analytics send interaction information to Fennec separately from the Google Analytics and Umami website analytics described in our general Privacy Policy. The form's analytics disclosure explains the collection; a disclosure does not by itself establish consent.
Shopify's storefront privacy choices are not currently connected to Fennec's form analytics in this version. Collection and consent behavior must be reviewed before this supplement is finalized for public launch.
The planned launch controls have been implemented for review and still require release and development-store verification. They read Shopify's privacy choices without granting consent and keep optional analytics disabled for Shopify-linked forms, including hosted and embedded entry points. Request answers, submission processing, abuse controls, notifications, and applicable customer sync remain available. These planned controls are not a claim that the current production release has changed.
The merchant is responsible for the notices and consent choices required for their storefront and chosen features. Do not assume that installing the app, submitting a request, or pairing an account gives consent for marketing or optional tracking.
Retention, uninstall, and deletion
Form responses remain in the Fennec workspace for review and are subject to available workspace retention and deletion settings. Installation records, customer sync history, support messages, security logs, and privacy request evidence are separate categories of information and may have different retention needs.
Uninstalling the app revokes store access and staff pairings. It does not automatically delete the separate Fennec account or workspace, and it does not confirm that all Shopify-related information has been removed. Shopify can send a subsequent store-data deletion request.
Customer access and deletion requests received from Shopify are recorded for review. Supported processing can provide a private response export or remove specifically approved local response data. Receiving a request or deleting a local response is not confirmation that every related copy has been erased.
The operator has approved the following operational targets for launch:
- Application logs: retain up to 14 dated daily-log files. This rotation limit counts files; it does not establish an exact 14-day expiry for every log copy. Existing single-file, admin, security, and infrastructure logs require separate review.
- Database-backed failed jobs: prune records older than 7 days (168 hours) through an hourly scheduled task. Actual removal depends on successful task execution.
- Temporary Shopify privacy exports: retain the existing 24-hour expiry, with hourly cleanup and separate delivery/removal evidence.
- Rolling backups: retain generations for 14 days or less, with reviewed deletion and isolated restoration safeguards. The operator reports no existing backups as of October 7, 2026; a backup service, its expiry, and a restore test still need to be established. A legacy R2 backup bucket's relationship to Fennec data remains unconfirmed. This does not confirm the absence of copies retained by other service providers.
These targets do not change active form-response retention or prove that production settings have been applied. Complete handling of store-wide deletion and copies in exports, connected services, support records, logs, file-processing records, and providers remains under review before public launch. Provider-specific periods, successful cleanup, and independent deletion safeguards for restored backups must be verified before this draft is published as the app's final privacy policy.
Access, correction, and other requests
Depending on applicable law, you may have rights to access, correct, delete, restrict, or obtain a copy of your personal information. Merchants and staff can contact us about their account or Shopify app information. Respondents should usually contact the merchant identified on the form because the merchant decides the purpose of collection; we can help route a request if the merchant is unclear.
We may need information to verify the requester and identify the relevant store, workspace, or submission. A store address alone does not establish authority over a workspace or another person's information. Request acknowledgement and completion are separate steps, and any response must account for applicable law and Shopify's requirements.
Contact
For Shopify app privacy, deletion, or support questions, email [email protected] or use our Shopify support form. Include your store address and relevant request reference if you have one. Do not send passwords, app credentials, or unnecessary sensitive information.
This draft will be updated after the remaining provider, privacy, and publication review. Any final supplement will show its own published date.