Data

What we read from each platform

Last updated 15 August 2026

To tell you what you kept, Akedra has to see what came in and what went out. That means reading data from the platforms you already use. This page says exactly which data, from which platform, and why each piece is needed. It is written in plain language on purpose — you should be able to decide whether you are comfortable without asking a developer.

None of this is happening yet. Akedra is still being built, no integration is live, and no store is connected. This page describes what the product will read when it exists, so that it is written down before anyone is asked to connect anything.

Three rules that apply everywhere

  • Read-only, always. Every connection uses read-only permissions. Akedra cannot edit an order, refund a customer, change a price, publish a product, create or pause a campaign, or spend a single dollar of your ad budget. Even if our own code had a bug, the permissions we hold do not allow a write.
  • Only what the arithmetic needs. We request the narrowest permission scope that produces the number, and nothing beyond it. Where a platform offers a broad scope and a narrow one, we take the narrow one even when it is more work.
  • Yours, not ours. We do not sell your data, share it with other merchants, or use one store’s figures to advise another. Your numbers exist in your account to produce your reports.

The platforms

Shopify — read only

Orders, fulfilments, refunds, products

This is the core connection and the only mandatory one. We read:

  • Orders — value, currency, line items, discounts, taxes, payment method, and the tags or notes your team uses to record a confirmation call. This is how we separate an order that was placed from an order that was confirmed.
  • Fulfilments and shipping status — including courier status where Shopify has it, so we can tell a delivered parcel from one refused at the door.
  • Refunds and returns — so an order that came back a week after delivery stops counting as revenue.
  • Products and variants — including cost per item where you have entered it, so we can subtract what the goods actually cost you.

We do not read your customers’ payment credentials (Shopify never exposes them), your staff accounts, your theme code, or your apps. Customer names, phone numbers and addresses arrive attached to orders; we use them only to identify repeat customers and to group results by city or region, and never to contact anyone.

To disconnect: Shopify admin → Settings → Apps and sales channels → Akedra → Uninstall. Uninstalling revokes our access immediately and triggers our deletion process below.

Meta — read only

Ad spend and campaign results

Optional. Connect it only if you advertise on Facebook or Instagram. Through the Meta Marketing API we read the ads_read scope only:

  • Spend by day, campaign, ad set and ad — the single figure that has to come out of your revenue.
  • Campaign, ad set and ad names and IDs — so the spend can be attributed to the products it was promoting.
  • Impressions, clicks and reported conversions — used to compare what Meta reported against what your store actually kept.

We do not read your personal profile, your friends, your messages, your page content, or any audience or customer list. We hold no permission to create, edit, pause or fund a campaign.

To disconnect: Meta Business Integrations → Akedra → Remove. You can also remove it from inside Akedra, which revokes the token from our side as well.

Google — read only

Google Ads cost and performance

Optional. Connect it only if you run Google or YouTube ads. Through the Google Ads API we hold read-only access and request the narrowest scope that returns cost data. We read:

  • Cost by day, campaign and ad group.
  • Campaign and ad group names and IDs, to attribute that cost to products.
  • Impressions, clicks and conversions, to compare reported performance against kept profit.

We do not read your Gmail, Drive, Calendar, Contacts or any other Google product. Akedra requests no Google scope outside Google Ads. We cannot create, edit, pause or fund a campaign, and we cannot change a budget or a bid.

To disconnect: Google Account → Third-party apps with account access → Akedra → Remove access. Or remove it from inside Akedra.

What we never ask any platform for

  • Card numbers, bank details or payout credentials. No integration we use exposes them and we do not want them.
  • Permission to write, spend, publish or delete anything, on any platform.
  • Your customers’ data for marketing. We never build an audience, upload a customer list, or contact anyone who bought from you.
  • Access to any Google or Meta product beyond the advertising cost data described above.

How it is stored

Access tokens are encrypted at rest and are only ever decrypted by the background job that fetches your figures. Store data is held in an isolated database per environment, encrypted at rest and in transit. Access is limited to the people who need it to run the service, and is logged.

Deleting it

Disconnecting a platform stops all further reading immediately. Everything we already pulled from that platform is deleted within 30 days, and the access token is destroyed at once. If you close your Akedra account entirely, everything goes within 30 days. You can ask us to do it sooner by writing to privacy@akedra.com, and we will confirm in writing when it is done.

If this changes

If we ever need a permission that is not listed on this page, we will update the page, email everyone affected, and ask you to approve the new scope. A connection you have already granted will never quietly widen.

Related: our privacy policy and our terms of service.