Privacy policy

Last updated: October 27, 2026

This policy covers tekraid.com and every TEKRAID app. Part 1 applies to everything. Part 2 has a section for each app explaining exactly what it uses. Jump to: Porchday, Sizeday, Stockday, Editday, Printday, Ruleday, or Bundleday (coming soon).

Part 1: TEKRAID as a whole

Who we are

When this policy says "TEKRAID", "we" or "us", it means TEKRAID LLC. We run tekraid.com and the TEKRAID apps, and we're responsible for the data they handle. Business address: TEKRAID LLC, 1561 West Hamlin Road, Rochester Hills, MI 48309. Contact: hello@tekraid.com.

This website

tekraid.com is a simple informational site. We don't use advertising or tracking cookies, and we don't run analytics. Our website host, Vercel Inc. (United States), processes standard server logs (like IP address and browser type) to deliver the site and keep it secure.

Website forms

tekraid.com has two forms: the contact form and the Launch Partner application. When you send one, we get what you type into it. That's your name, your email address, your store or brand details (such as your store URL, what you sell, and your product), your message, and the answers you pick from the lists (for example rough monthly sales, margins, budget or timing). Every field is something you fill in yourself, and we don't add any other data about you.

To stop spam and abuse, the form server also looks at your IP address and counts how many forms come from it in a short window. That count is held in memory only for about 10 minutes. We don't put your IP address in the email and we don't save it anywhere else. Vercel's standard server logs, described above, still apply.

Your submission is sent as an email to hello@tekraid.com through Postmark, an email delivery service run by ActiveCampaign, LLC (United States). Postmark handles it only to deliver it to us, as our service provider (a processor, in GDPR terms), and keeps a copy of the message and its delivery details for up to 45 days before deleting it. Opens and clicks aren't tracked. We don't store submissions in a database.

We use what you send only to read it, reply to you, and follow up about your enquiry or application. We don't sell it, we don't use it for advertising, and we don't add you to a mailing list. The email stays in our mailbox for as long as we need it for the conversation and for our normal business records. To have your submission deleted, email hello@tekraid.com from the address you used and tell us.

When you email us

If you write to hello@tekraid.com, or ask to hear when an upcoming app launches, we keep your email address and message so we can reply and, if you asked, tell you when that app is ready. Ask any time and we'll delete it.

What we never do

We don't sell personal data, we don't use it for advertising, and we don't share one merchant's data with another merchant.

Why we're allowed to use your data

If you're in the EEA or UK, the law asks us to say why we can use your data. For merchants using our apps, it's to provide the app you installed (a contract). For website forms and emails, it's to answer what you asked us (steps you asked for before any agreement, and our legitimate interest in replying to people who contact us). Server logs and spam checks rely on our legitimate interest in keeping the site and apps secure.

Your rights

We follow Shopify's privacy requirements and support requests under laws such as the GDPR, UK GDPR and CCPA. Depending on where you live, you can ask us to tell you what we hold about you, give you a copy, correct it, delete it, or stop or limit how we use it. Email hello@tekraid.com to ask. We may need to check it's really you first, and we won't treat you differently for asking. We answer within the time the law allows. If you're in the EEA or UK, you can also complain to your local data protection authority.

If you shop at a store that uses one of our apps, that store is in charge of your data and we process it on its behalf. Please contact the store first. If you contact us, we'll pass your request to the store and help it respond.

Where data is processed

We and our providers are in the United States, so your data is processed there. Where the law requires it for data from the EEA, UK or Switzerland, we rely on our providers' standard contractual clauses or similar safeguards.

Where the apps run

Our apps and their databases are hosted by Render Services, Inc. in the United States (Virginia). The databases are Render Postgres, which encrypts data at rest, backups included, and every connection to the apps uses HTTPS. Each app section below lists exactly which other providers it uses.

Our service providers

• Vercel Inc. (United States): hosts tekraid.com and runs the website forms.
• Render Services, Inc. (United States): hosts the apps and their databases.
• Shopify Inc.: the platform the apps run on, including sign-in and billing.
• Postmark (ActiveCampaign, LLC, United States): delivers website form submissions to us, and the transactional emails some apps send. Each app section says whether that app uses it.
• GitHub, Inc. (United States): holds our source code and runs tests. It doesn't receive merchant data.

Requests from Shopify about your customers

Shopify sends every app three privacy requests, and each TEKRAID app handles them the same way:

• customers/data_request: one of your customers wants to know what we hold about them. We gather it and send it to you within 30 days.
• customers/redact: we delete what we hold about that customer's orders.
• shop/redact: sent 48 hours after you uninstall. We delete your store's data.

We keep a short record of each request (which store, which request, the order numbers it covered, and when we finished it) so we can show the work was done. That record holds no names, emails or addresses, and we delete it after 365 days.

Security

Our full security practices, including how we handle incidents, are on our security page. In short:

• We only ask for the Shopify permissions each app needs.
• Connections and stored data are encrypted.
• We log when our systems read protected customer data, plus certain changes and deletions, and keep that log for up to 365 days (93 days for Printday).
• We check that every request really comes from Shopify.
• Access keys and passwords stay out of our code.
• Only staff who need access have it.

If a security incident affects your data, we'll let you know without undue delay.

Children

TEKRAID apps are business tools and aren't meant for anyone under 16. We don't knowingly collect children's data.

Changes

If we change this policy, we'll update the date at the top. For significant changes to an app's section, we'll also email the store's contact address and post a notice in the app.

Part 2: App by app

Porchday: Delivery Dates

Porchday shows shoppers an estimated delivery date on your storefront and saves the promised date on each new order. It needs very little personal data to do that. Here's what it uses:

• Store information: your shop's domain, your Porchday plan, when you installed, your time zone, and an access token Shopify gives us so the app can work with your store.
• Your delivery settings: cutoff times, processing and shipping times, holidays, warehouses, rules, and design choices. These are also saved to your store so your theme can show the date.
• Product details: product and variant IDs, tags, collections, and whether an item is in stock, so the right rule applies. We don't change your products, prices or stock.
• The promised date on each order: when an order comes in, we work out the date that was promised and save it on the order as an app field (promised_date), along with the rule and warehouse used. We keep a copy of that row, plus the date the order was delivered (from fulfillment updates), so the app can show you how accurate your dates have been.
• Delivery region: the order's shipping country. We don't read the ZIP code, street address, name, email or phone number from your customers' orders.
• Storefront events: Porchday's web pixel sends us a small event when a date is shown, when someone adds an item to the cart after seeing it, when a countdown runs out, and when a checkout completes with a promise attached. Each event carries only an event ID, time, page type, product and variant ID, rule, and date. The checkout event carries only the promise itself. We keep the event IDs (to avoid counting anything twice) and running totals. Nothing that identifies a shopper is stored. We look at the sender's IP address in memory to stop abuse, and don't save it.
• Feedback you send us from inside the app, such as a feature request and an optional screenshot, plus whether it was an idea or a problem report.
• Your store's contact email and name, from Shopify when you install, so we can reply to feedback, tell you when something you asked for ships, send one reminder if setup isn't finished after three days, and send one short note if you uninstall.
• Small markers that a message was sent or a prompt was shown (for example "setup reminder sent"), so nothing is sent or shown twice.
• Why you left, if you tell us: the reason you click in the uninstall note and any comment you add.

We use this only to show delivery dates, report on how accurate they are, run your plan through Shopify billing, answer support requests, and keep the app secure.

Shopify permissions

• write_products: to save the app-owned edd_enabled flag on a product for the Free plan product gate, and to read products, tags and collections for your rules. Porchday does not edit other product data.
• read_inventory: to tell in-stock, out-of-stock and preorder items apart.
• read_locations: to match your warehouses to Shopify locations.
• write_orders: to save the promised date on new orders. Porchday doesn't change anything else on an order.
• read_fulfillments: to see when an order was delivered, for the accuracy report.
• write_pixels and read_customer_events: to run the web pixel described above.
• unauthenticated_read_product_listings and unauthenticated_read_product_tags: so the storefront can look up the products in a cart.

Porchday doesn't ask for read_all_orders. Orders count as protected customer data under Shopify's rules, and we only use the parts listed above.

Providers

Shopify Inc. (platform, sign-in and billing), Render Services, Inc. (hosting and database, United States), GitHub, Inc. (source code and testing, no merchant data), and Postmark (ActiveCampaign, LLC) to send the emails above from mail.tekraid.com. Postmark sees your contact email and the message, nothing else. We don't track email opens or clicks, and we never send marketing email.

Retention and deletion

We keep Porchday's order-promise copies (country code, promised and delivered dates) for 13 months, then delete them. Other Porchday data stays while the app is installed. When you uninstall, we end your session and stop processing. When Shopify sends shop/redact 48 hours later, we delete your settings, order rows, storefront event records, totals, feedback, your contact email and name, the message markers, and your uninstall answers. Two things stay: the record that your store already used its free trial (so a reinstall doesn't start a new one), and the privacy-request and access records described in Part 1, which are deleted after 365 days. For a customers/redact request, we delete our rows for those orders and remove the promised_date field from the orders themselves while the app is still installed. Database backups at Render then age out on their own schedule.

Sizeday: Size Chart & Guide

Sizeday shows a size chart on the product page. The chart is chosen in your theme, so a shopper viewing a product does not contact Sizeday's servers.

• Store information: your shop's domain, when you installed, and the access token Shopify gives the app.
• Charts and rules you create: titles, measurements, notes, an optional image link, and which tag, collection, product type, vendor or product each chart belongs to. The same data is saved on your store so the theme can read it. A product metafield stores the override when you assign one product its own chart.
• Product details used to assign a chart: product ids and titles you pick, plus tags, collections, product types and vendors read while you edit rules. Sizeday doesn't change your products, prices or stock.

We don't store your customers' names, emails, phones or addresses. A customer privacy request is recorded and answered within 30 days, and there is no customer record to return or delete.

Shopify permissions

• write_products: to read products, tags, collections, types and vendors for your rules, and to save the chart metafield on a product when you set an override. Sizeday does not request theme file access.

Providers

Shopify Inc. (platform and sign-in) and Render Services, Inc. (hosting and database, United States, Virginia, on the shared TEKRAID database server). GitHub, Inc. holds the source code and runs tests, and doesn't receive merchant data. There is no email provider, because Sizeday doesn't send mail.

Retention and deletion

We keep Sizeday's data while the app is installed. Uninstalling ends the session. When Shopify sends shop/redact 48 hours later, we delete the shop's charts, rules, product overrides and session. Shopify also removes the charts from your store. The privacy-request record described in Part 1 is deleted after 365 days. Database backups at Render then age out on their own schedule.

Stockday: Forecast & POs

Stockday is a Shopify app that forecasts demand and helps you create purchase orders. Here's what it collects when you install it:

• Store information: your shop's domain, store name, Shopify plan, currency, timezone, and the store's contact email (used for account, billing, and service messages).
• Products and inventory: products, variants, SKUs, product costs (if you've entered them in Shopify), and current inventory quantities (available and on hand) at each location.
• Order data: order dates, line items, quantities, prices, whether an order was cancelled, its refunds, whether it is a test order, and the location it was sold from, so we can work out how fast each item sells. We don't store your customers' names, email addresses, phone numbers, or shipping addresses.
• Supplier information you give us: supplier names, contact names and emails, lead times, minimum order quantities, case pack sizes, and any notes or payment terms.
• Purchase orders you create, edit, send, and receive in the app.
• Why you left, if you tell us: the reason you click in the one email we send after you uninstall Stockday, and any comment you add.
• Usage and technical information: which staff account did what in the app, error logs, and basic technical data like browser type.

We use it only to forecast demand and suggest what, how much, and when to reorder; to create, send, and track purchase orders; to manage your subscription through Shopify billing; to answer support requests; and to keep the app secure.

Your forecasts use only your store's data. We don't train models on data from other stores, and we don't use your data to train anything for other merchants.

Shopify permissions

These are all the permissions the app requests, and why:

• read_products: to see your products, variants, SKUs, and costs.
• read_inventory: to see current stock levels.
• write_inventory: to update stock levels when you mark a purchase order as received. The app only changes inventory when you receive a PO.
• read_locations: to forecast stock at each location.
• read_inventory_transfers and write_inventory_transfers: to show and create stock transfers between your locations when you ask the app to.
• read_inventory_shipments, write_inventory_shipments and write_inventory_shipments_received_items: to track incoming shipments for transfers and purchase orders, and to record items as received.
• read_orders: to learn from your sales. Forecasts use the order history Shopify makes available under this permission, which is normally your most recent orders, not your full history.

We may later ask for read_all_orders (older orders), but only if Shopify approves it. If we do, we'll update this policy first and you'll be asked to approve the new permission in Shopify. Orders count as protected customer data under Shopify's rules. We only use the product and sales details in them.

Sub-processors

That's the complete list. Backups stay inside Render. You can send a purchase order in two ways: from inside Stockday (any plan), which goes through Postmark above, or from your own email, where the app opens a pre-filled message and no email service of ours sees it. If we ever add a provider, we'll update this list before we start using it. We may also share information if the law requires it.

Storage, retention, and deletion

Your data is stored with Render in the United States (Virginia region), encrypted in transit and at rest. We keep it while the app is installed. Sales data from orders is kept in two forms. Rows for each order (the order id with its units and revenue per product) are deleted after 93 days for every store, whether it's active, uninstalled, or has lapsed billing. Daily totals per product, which aren't linked to any order or customer, are deleted once they are 365 days old. Nothing from orders is kept past 365 days, even while the app is installed. Forecasts are kept for 14 days, forecast accuracy for 120 days, and stock snapshots for 90 days. Purchase orders and other store data stay while Stockday is installed, and are deleted on shop/redact. When you uninstall, we stop scheduled forecasts and close your session right away. After you uninstall Stockday, we send one short email asking why you left. No marketing. It goes once, to your store's contact email, and nothing follows it. 48 hours later, Shopify sends us a data-erasure request (shop/redact). For Stockday, after that request we keep only your shop's domain and the date its free trial started, solely to make sure each store gets one free trial. Everything else is deleted, apart from the privacy-request and access records described in Part 1, which go after 365 days. Render keeps continuous point-in-time recovery for a rolling window of no more than 7 days, and keeps any manual export for 7 days after it is created. We don't download exports or keep other backup copies. Deleted data can therefore remain in Render-managed backups for up to about 7 days after deletion. Deleting a database instance removes all of its backups. Background job records, including queued supplier purchase-order emails, are deleted automatically within 15 days. Postmark keeps message content (including email bodies), recipient metadata and delivery/bounce activity for 45 days, then deletes it; aggregated statistics and any hard-bounce or spam-complaint suppression entries are kept until removed.

• customers/data_request: if one of your customers asks what we hold about them, we tell you within 30 days (usually nothing beyond order references).
• customers/redact: we delete our records of that customer's orders. Daily sales totals per product stay, because they can't be linked to anyone.
• shop/redact: we delete your store's data. Stockday also keeps your shop's domain and trial start date, only so each store gets one free trial.

Editday: Order Editing

Editday lets a customer correct their own order. To do that it reads, on the Shopify order and not as a copy in our database, the shipping address, the name and phone on that address, and the email used to send one edit link. What we store is the order id and name, the kind of edit, a short summary such as "Shipping address updated", before and after totals, a price preview for up to 30 minutes, and the time a link was sent. The street, name, phone, and email are not in those rows.

We use this only to show the customer their order, apply the change they confirm, send that one edit link, and show you an activity log of totals. We don't send marketing, and a price change is not refunded automatically.

Shopify permissions

• read_orders and write_orders: to show the order and save an address the customer confirms on that same order.
• write_order_edits: to change a quantity, a variant, or a line on the existing order.
• read_products: to load the other variants of a line.
• read_merchant_managed_fulfillment_orders and read_third_party_fulfillment_orders: so an edit can be locked once a fulfillment service has the order.

Editday doesn't ask for read_all_orders.

Providers

Shopify Inc. (platform, sign-in, and billing), Render Services, Inc. (hosting and database, United States, Virginia), and GitHub, Inc. (source code and testing, no merchant data). When email sending is turned on, Postmark (ActiveCampaign, LLC) sends the one edit link. Postmark sees that order's email address and the message. We don't store the address, we don't track opens or clicks, and we don't send marketing. If Postmark isn't set up, the link isn't sent and the order status page is the way in.

Retention and deletion

The address, name, phone, and email stay on the Shopify order. The price preview is kept for up to 30 minutes and deleted when the edit is saved. Expired previews are not reused. customers/data_request returns the activity rows for the orders named in the request (order name, kind of edit, summary, and totals), with no address or email. customers/redact deletes the activity, the preview, and the link row for those orders. Uninstalling ends the session. When Shopify sends shop/redact 48 hours later, we delete the shop's activity, previews, links, and session. The privacy-request record described in Part 1, and the access log of protected customer data, are deleted after 365 days. Database backups at Render then age out on their own schedule.

Printday: Invoices & Documents

Printday reads the name, billing and shipping address, email, and phone already on an order at the moment a document is rendered, and does not store those fields. What we store is your document templates, the business details you type for branding, an invoice number with the order id, link outcomes with a hash of the IP address (the hash is cleared after 30 days), staff permission flags, and bulk-print order ids. Staff flags are the staff id and what that account may do. They don't include an email address.

We use this only to fill a document you print, or to check a signed link you placed in a Shopify notification. Printday doesn't send email. We don't use the data for marketing.

Shopify permissions

• read_orders, read_draft_orders, and read_products: to fill the document from the order and its products at the moment you print.
• read_customers, read_locations, read_payment_terms, read_locales, and read_markets: to print the details the template asks for.
• read_merchant_managed_fulfillment_orders, read_third_party_fulfillment_orders, and read_assigned_fulfillment_orders: to print fulfillment details when a template includes them.

Printday doesn't ask to change orders or customers.

Providers

Shopify Inc. (platform and sign-in), Render Services, Inc. (hosting and database, United States, Virginia), and GitHub, Inc. (source code and testing, no merchant data). There is no email provider, because Printday doesn't send mail.

Retention and deletion

Name, address, email, and phone exist only in the document that was just rendered, and are gone when that response is sent. The IP hash on a link outcome is cleared after 30 days, and that row is deleted after 93 days. A bulk-print job (the order ids and counts) is deleted after 93 days, and so is the staff access log. Invoice numbers stay while Printday is installed. customers/data_request reports order ids, invoice numbers, link outcomes, and bulk-job ids. It does not include the document or an email address. customers/redact deletes the invoice number, the link row, and a bulk-print job that mentions those orders. Uninstalling ends the session. When Shopify sends shop/redact 48 hours later, we delete templates, invoice numbers, branding, staff flags, link rows, bulk-print jobs, and the session. The privacy-request record described in Part 1 stays. Its report and order ids are cleared after 93 days, and the rest of the record (store, request type, dates, and outcome) is deleted after 365 days. Database backups at Render then age out on their own schedule.

Ruleday: Checkout Rules

Ruleday stores the checkout rules you write (conditions and actions). Those rows are not customer records. A Shopify session can include the signed-in staff member's name and email, and the shop's access token.

We use the rules only to hide, rename, sort, or block payment and delivery methods at checkout, as you set them.

Shopify permissions

• read_products: to match a rule to the products in the cart.
• write_payment_customizations, write_delivery_customizations, and write_validations: to apply the payment, delivery, and validation rules you turn on.

Providers

Shopify Inc. (platform, sign-in, and billing) and Render Services, Inc. (hosting and database, United States, Virginia). GitHub, Inc. holds the source code and runs tests, and doesn't receive merchant data.

Retention and deletion

We keep the rules and the session while Ruleday is installed. Uninstalling ends the session. When Shopify sends shop/redact 48 hours later, we delete the rules and the session. The privacy-request record described in Part 1 has no names, emails, or addresses, and we delete it after 365 days. Database backups at Render then age out on their own schedule.

Bundleday (coming soon)

Bundleday hasn't launched yet and doesn't collect any data. We'll add its section here, listing exactly what it uses, before it goes live.

How we process personal data on your instructions is in our Data Processing Agreement.

Contact

Email: hello@tekraid.com
Company: TEKRAID LLC
Mail: TEKRAID LLC, 1561 West Hamlin Road, Rochester Hills, MI 48309