Terms and privacy

Privacy Policy

The rules we work by, in plain words. We write and publish for your business, so you should know exactly what we do with your website, your content and your accounts. Five documents cover it: the Terms of Service, the Privacy Policy, the Acceptable Use Policy, the list of companies that help us run the service, and how to have your data deleted.

Last revised November 6, 2026Effective October 11, 2026

This policy explains what Gild & Grid, operated by Amanah Fund, LLC, collects, why, who receives it and how long we keep it. It covers gildandgrid.com and the service at gildgrid.app. It is separate from the Amanah Budget app's privacy policy.

We do not sell your data, and we do not use your content to train AI models.

Our two roles

  • Controller for your account and billing data: we decide how it is used to run the service.
  • Processor for your content: we use it only to do what you ask. A data processing agreement is available on request.

What we collect

DataWhere it comes fromWhyNotes
Name, email, sign-in methodYou, or Google sign-inYour account, sign-in codes, noticesCodes are sent through our email provider
Workspace, members, roles, invitesYouRunning the service
Website content we scanPublic pages of the site you submitYour brand profile and draftsRaw pages kept 30 days; the profile stays until deletion
Brand assets you uploadYouTemplates and posts
Drafts, posts, articles, mediaCreated for youThe serviceKept until you delete them or retention ends
Channel credentialsYou, when you connectPublishing and reading analytics as you directSealed; never in logs or exports
Google Analytics 4 and Search Console dataYou, when you connectPlanning and refreshing articlesRead only; see Google user data
Usage, job records, audit trailCreated as you use the serviceAllowance meters, security, support
Billing detailsStripePayments, invoices, taxIdentifiers and status only
Support messagesYouHelping you
Technical data: IP address, browser, logsYour deviceSecurity, abuse prevention, reliabilityBot protection on sign-in, signup, scan, invite acceptance and the forms on gildandgrid.com
Homepage and sign-in visitsGoogle Analytics on gildandgrid.com and on the sign-in screen at gildgrid.appUnderstanding which pages and links people useSee Cookies
Managed inquiriesThe contact formReplying to youNetwork address and browser details stored only as salted hashes, for rate limiting
Launch listThe join forms on gildandgrid.comOne email when we open; see Launch listNetwork address stored only as a salted hash, for abuse limits

Launch list

Gild & Grid is not open yet. When you join the launch list on gildandgrid.com, we collect:

  • Your email address.
  • Your website address, if you give one. It is optional.
  • Which form you used: the one at the top of the page or the one at the end.
  • Your network address, stored only as a salted hash, so we can limit abuse.

We use your email address to send you one email when Gild & Grid opens. If you gave us your website, we use its public pages to prepare your brand profile, so it is ready on day one. We send no other mail to the list, and we never sell it.

To be taken off the list, email [email protected] and we will remove you. Otherwise we keep your entry until we send the launch email, then for up to 90 days after it.

Google user data

If you connect Google Analytics 4 or Search Console, we ask for one read-only scope at a time:

ProductScopeWhat we read
Google Analytics 4analytics.readonlyAccounts, properties and reports, such as sessions by landing page
Search Consolewebmasters.readonlySites, queries, pages, clicks and impressions

How we use it

  • To show you your properties, and to plan and refresh your articles. Suggestions drawn from it are treated as data, never as instructions.
  • Never for advertising.

Who sees it

  • Only our hosting provider receives it, to run the connection, plus anyone the law requires us to disclose it to. We do not send it to AI model providers. If that ever changes, we will update this policy first.
  • Our staff read it only for support you ask for, to investigate abuse, or when the law requires.
  • It is never used to train generalized AI models.

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

Data protection for Google user data

These are the measures that protect information we receive from Google APIs:

  • Encryption in transit. Your browser reaches Gild & Grid over HTTPS, and our app tells browsers to connect to it only that way. Our requests to Google go over HTTPS to Google's own API addresses and nowhere else.
  • Encryption at rest. The token that lets us read your Google data is sealed with AES-256-GCM encryption before it is stored, under a key held apart from the database and never written to logs. Our hosting provider also encrypts the data it stores for us.
  • Only what is needed. We ask for read-only scopes, one product at a time. We do not store the reports and tables we read from Google, and we keep only the sealed token and the name and ID of the property or site you chose. We do not keep a short-lived access token: each time we read, we get a new one from Google for that request.
  • Access controls. Only an owner or admin of your workspace can connect a Google account, view its reports or disconnect it, and the server enforces that, not just the screen. Workspaces are isolated from one another, and an automated test checks that one workspace cannot reach another's. Staff open a workspace only through an admin console behind its own sign-in, and each time they do, we record who opened it and when.
  • Quiet logs. When a request to Google fails, our log keeps a short code and a status number. It never holds a token, a report row or the content Google returned.
  • Removal. You can disconnect at any time, as described under Disconnecting below. We ask Google to end the grant, then erase the stored token at once.
  • Incidents. If your Google data is ever accessed or used without authorization, we will tell you without unreasonable delay and no later than 60 days after we discover it. Security says what the notice contains and what we do first.

Disconnecting

Revoke access in Settings, under Connections, or from your Google account's permissions page. When you disconnect in Settings, we ask Google to end the grant first and then erase the stored token at once.

How long we keep it

We do not store the reports and tables we read from Google. They are fetched when you open a report, shown to you and not saved. We keep only the sealed token that lets us read on your behalf and the name and ID of the property or site you chose. The token is erased when you disconnect. The property or site name and ID stay with your workspace and follow the timeline in How long we keep it.

Facebook, Instagram, TikTok and LinkedIn

If you connect one of these accounts, this is what we receive from it and what we do with it. For each, we use the data only to show which account is connected and to publish posts that you or your team approved. We do not sell it, use it for advertising or use it to train AI models. An owner or admin of the workspace connects and disconnects accounts.

Facebook and Instagram

When you connect a Facebook Page or an Instagram professional account, you sign in to Meta and approve permissions to list your Pages, publish to them and read their basic details. Where a Page belongs to a business portfolio, we also ask for business management so the Page can be listed. We receive your Meta user ID, the name and ID of each Page you administer, the username and ID of any Instagram professional account linked to it, and an access token for each Page. We keep the token only for the Page you choose, and keep your Meta user ID so we can recognize a notice from Meta that you removed our access. For each post we publish, we also keep the ID and link Meta returns. We do not read your messages, comments, followers or performance numbers. Tokens are sealed with application-layer encryption under a key held apart from the database, and are never written to logs. To disconnect, choose Disconnect on the account's card under Settings, then Connections. That erases the stored token at once. Meta offers no way for us to end a single Page's access, so also remove Gild & Grid under Business integrations in Facebook, or under Apps and websites in Instagram. If you do, Meta tells us, we stop publishing and the connection shows as needing to reconnect. If you ask Meta to delete the data it shared with us, Meta tells us, we erase the token and the record of which Meta user granted it, and Meta shows you a confirmation code and a status page. The Page name and ID and the post records stay with your workspace until it is deleted, within 90 days after you cancel or ask us to delete your account. You can also write to [email protected].

Instagram, signed in directly

If you connect an Instagram professional account directly, you sign in to Instagram instead of Meta and approve two permissions: instagram_business_basic, to read the account's basic details, and instagram_business_content_publish, to publish to it. We receive the account's Instagram user ID, username and account type, and an access token that lasts 60 days, which we renew automatically while the account stays connected. We keep the Instagram user ID so we can recognize a notice from Instagram that you removed our access. We do not read your messages, comments, followers or performance numbers. The token is sealed with application-layer encryption under a key held apart from the database, and is never written to logs. To disconnect, choose Disconnect on the account's card under Settings, then Connections. That erases the stored token at once. You can also end the access in Instagram, under your settings, then Website permissions, then Apps and websites, by removing Gild & Grid. If you do, Instagram tells us, we stop publishing and the connection shows as needing to reconnect. If you ask Instagram to delete the data it shared with us, Instagram tells us, we erase the token and the record of which Instagram user granted it, and Instagram shows you a confirmation code and a status page. The account's username and ID and the post records stay with your workspace until it is deleted, within 90 days after you cancel or ask us to delete your account. You can also write to [email protected].

TikTok

When you connect a TikTok account, you approve two permissions: user.info.basic, to read your display name and avatar, and video.publish, to post on your behalf. We receive your TikTok account ID, display name and avatar, an access token and a refresh token. When we post, we also read the posting options TikTok offers your account, and we post with the privacy and interaction settings you chose. For each post, we keep the ID TikTok returns. We do not read your videos, followers or messages. Both tokens are sealed with application-layer encryption under a key held apart from the database, and are never written to logs. To disconnect, choose Disconnect on the account's card under Settings, then Connections. We ask TikTok to end the grant, then erase the stored tokens. If TikTok cannot be reached, nothing changes, so you can try again. If you remove Gild & Grid in TikTok instead, TikTok tells us, we stop posting and the connection shows as needing to reconnect; TikTok removes our access, but our stored tokens stay until you disconnect here. The account name and ID and the post records stay with your workspace until it is deleted, within 90 days after you cancel or ask us to delete your account. You can also write to [email protected].

LinkedIn

You can connect your own LinkedIn profile, a company Page, or both. For a profile you approve openid, profile and w_member_social. We receive your name, your LinkedIn member ID and an access token, plus a refresh token if LinkedIn issues one. For a company Page you approve w_organization_social and rw_organization_admin. We receive the ID and name of each Page you administer, and a token for the one you choose. We use w_member_social and w_organization_social to publish, and the rest to show which account is connected. rw_organization_admin is the Page administration permission LinkedIn grants us; we use it only to read which Pages you administer and their names, never to change a Page. We do not read your connections, feed or messages. Tokens are sealed with application-layer encryption under a key held apart from the database, and are never written to logs. To disconnect, choose Disconnect on the account's card under Settings, then Connections. We send LinkedIn a request to end the grant, then erase the stored tokens. You can also remove our access in your LinkedIn settings, after which our stored token stops working. The account name and ID and the post records stay with your workspace until it is deleted, within 90 days after you cancel or ask us to delete your account. You can also write to [email protected].

Cookies

We set one session cookie to keep you signed in. Our bot protection may set a token of its own. We use no advertising trackers.

Our homepage at gildandgrid.com, and the sign-in and sign-up screen at gildgrid.app that you reach before you are signed in, use Google Analytics to count visits and see which pages and links people use, including whether a visit that starts on our homepage goes on to sign in. When you move between the two, a link parameter named _gl carries an anonymous visitor identifier so Google counts it as one visit. They set cookies named _ga that last up to two years. If you visit from the European Economic Area, the United Kingdom or Switzerland, it sets no analytics cookies and sends Google only a cookieless signal that a page was viewed. We do not use it for advertising, and it is not loaded on any page you see after you sign in, so it never sees your workspace, content or email address. You can block it in your browser settings or with Google's Analytics opt-out browser add-on.

How we use data

To run and secure the service, to bill you, to answer you, and to tell you about changes. We make no automated decisions that have legal effects on you.

Who receives data

  • The companies on the Subprocessors page, to run the service. Text goes to model providers only to generate your output.
  • The channels you choose to publish to.
  • Authorities, when a valid legal request requires it.
  • A buyer or successor, if the business is sold or merged, under this policy.

Where data is processed

In the United States by default.

How long we keep it

DataHow long
Raw copies of scanned pages30 days
Workspace data while you subscribeFor as long as the subscription is active
After cancellation90 days, with warnings by email; export works throughout
After account deletionThe same 90 days
Billing recordsAs long as the law requires; Stripe holds the payment record
Launch list entriesUntil we send the launch email, then up to 90 days; sooner if you ask us to remove you
Homepage and sign-in analytics14 months in Google Analytics, then deleted by Google
Support recordsAs long as reasonably needed to help you
Security logsAs long as security and the law require
Google Analytics 4 and Search Console dataReports and tables are not stored. The sealed token is erased when you disconnect. The chosen property or site name and ID are kept with your workspace data
BackupsAge out on their normal schedule

Deletion covers database rows, stored files and credentials. How to ask for it is on the Data Deletion page.

Your choices and rights

Depending on where you live, including California, the European Economic Area and the United Kingdom, you can ask to see, correct, export or delete your personal data, or object to how we use it. If your customers ask you about data we process for you, we will help you answer. We verify identity before acting on a request. To delete your account, your workspace or a connected account, including Facebook and Instagram, follow the steps on the Data Deletion page.

Security

We protect your data with these measures:

  • Encrypted connections. Gild & Grid is served over HTTPS, and our app tells browsers to connect to it only that way. Our hosting provider encrypts the data it stores for us.
  • Sealed credentials. The tokens that let us act on your connected accounts are sealed with AES-256-GCM encryption under a key held apart from the database, and are never written to logs.
  • Isolated workspaces. Each workspace is kept apart from every other, and an automated test checks that one workspace cannot reach another's data.
  • Roles checked on the server. What a person can see or change depends on their role in the workspace, and the server enforces it, not just the screen.
  • Limited staff access. Staff open a workspace only through an admin console behind its own sign-in, and each time they do, we record who opened it and when. They read your data only for support you ask for, to investigate abuse, or when the law requires.
  • Private files. Files you upload are stored privately. They are served only to people signed in to your workspace, after a check, and never from a public link.
  • Bot protection. Our sign-in and sign-up screens and our launch list form use bot protection.
  • Fail closed. If a security setting the service depends on is missing, the service refuses to run rather than running without it.

If you think you have found a security problem, write to [email protected].

If something goes wrong

If we learn that someone has accessed, used or disclosed your data without authorization, we will:

  • Act at once to stop it and limit the harm, such as revoking affected tokens and replacing keys.
  • Find out what happened and whose data was involved, and keep a record of it.
  • Tell the owner of each affected workspace by email, without unreasonable delay and no later than 60 days after we discover the incident. If the law or an agreement with you requires sooner, we will notify sooner. We will wait longer only if a law enforcement agency lawfully asks us to, and only for as long as it asks. We will also tell regulators where the law requires.
  • Say in the notice what happened, which of your data was involved, what we have done, what you can do to protect yourself, and how to reach us. If the incident involved information we received from Google APIs, the notice will say so and name the connected account.
  • Review each incident afterward, so we can prevent a repeat.

Children

Gild & Grid is for businesses and is not directed to anyone under 18.

Changes

We will tell you about a material change before it takes effect.

Contact

Gild & Grid by Amanah Fund, LLC
215 W Michigan Ave, Ypsilanti, MI 48197
[email protected]