I Can Get Grants.
PrivacyTermsContactBack to search

Funding listings on I Can Get Grants are informational. You must verify eligibility, deadlines, award amounts, and application rules with the provider.

Privacy policy

This policy describes what the I Can Get Grants public beta actually does with information. The product name in the interface is I Can Get Grants.

The operator is Tobias Fletcher, Brooklyn, New York. No street address is published. Questions, access requests, and deletion requests go to hello@icangetgrants.com (or use the contact form).

Effective date: October 25, 2026.

The law of the State of New York governs this policy. Disputes are heard in the state or federal courts located in New York.

Searching without an account

You can browse the shared funding catalog and run a match without creating an account. The guest form asks for applicant type, a U.S. state, interests, and, for students, a study level. That guest profile stays in the page for the current visit only. It is not written to the database. Reloading or leaving the page clears it. Guest searches are not monitored and are not included in scheduled discovery.

Opening the app still requests the shared catalog from the server. That request does not include the text you type into a guest search.

Accounts and sign-in

Saving a workspace uses Sign in with ChatGPT. The sign-in path is /signin-with-chatgpt, the callback path is /callback, and the sign-out path is /signout-with-chatgpt. This application does not collect a separate password.

After sign-in, each request can include these headers, which the app reads and does not store in its database:

  • oai-authenticated-user-id — account identifier
  • oai-authenticated-user-email — email address
  • oai-authenticated-user-full-name — full name, when the platform marks it as percent-encoded UTF-8

The app treats a visitor as signed in only when both an account id and an email are present. The name shown in the header is the full name when one is provided, otherwise a generic workspace label. The email and full name are not written into the database. The account id is the key for the saved workspace described below.

Signing out does not delete a saved workspace.

Sign in with ChatGPT is run by OpenAI, and sign-in is completed on OpenAI’s side. OpenAI’s privacy policy covers the account data, cookies, and logs OpenAI keeps for it. This app only reads the headers listed above.

On a local development server, a localhost-only HttpOnly cookie named __sites_local_auth stands in for those headers. That cookie is not the production sign-in.

Continue with Google

When Google sign-in is turned on, you can also continue with Google. The sign-in path is /auth/google/start, Google returns to /auth/google/callback, and the sign-out path is /auth/google/signout. The app asks Google only for the openid, email, and profile scopes. It exchanges the one-time code with Google on the server, checks Google’s signed ID token, and accepts only a Google account with a verified email address.

From that token the app keeps only Google’s account identifier (the sub value). It does not store or display the Google email address, name, or picture. A workspace created with Google alone is keyed by google: plus that identifier.

If you are signed in with ChatGPT, you can link one Google account in Preferences & data. A google_links row then stores the Google identifier, your ChatGPT account id, and the time of linking, and Continue with Google opens your ChatGPT workspace. Unlinking deletes that row. If that Google account already had its own workspace, linking moves its profiles and saved items into your ChatGPT workspace (your ChatGPT entries win where the two overlap) and then deletes the Google workspace, in one step. Unlinking later does not move anything back.

Catalog administration and the owner-only tools are available only through Sign in with ChatGPT, never through a Google sign-in, even a linked one.

Sign in with Google: Google’s signed ID token gives the app your Google account identifier, your email address and whether Google has verified it, and your name. The app uses the email only to check that it is verified, does not use the name, and keeps only the account identifier. Google data received through Sign in with Google is used only to sign you in and open your workspace. It is not sold, not used for advertising, and not shared with anyone. Google’s privacy policy covers what Google keeps about the sign-in.

Workspace stored for a signed-in account

Signed-in profiles, saved opportunities, and application notes are stored in a Cloudflare D1 database, in a workspaces row keyed by the account id. The row holds one JSON document. A save must come from the same site origin, and the document must be under 150,000 characters. The product allows up to 50 profiles and 500 saved items.

Each profile can include:

  • a profile id created in the browser
  • a profile name
  • applicant type: Student, Individual, Freelancer, Small business, or Nonprofit
  • country and state or region
  • interests and keywords
  • a funding goal in U.S. dollars
  • study level, when you set one
  • background and eligibility notes
  • whether monitoring is turned on for that profile

Background notes are stored for you to read. They are not used to calculate a match score and they are not sent in searches to funding sources.

Each saved opportunity can include:

  • the profile id and the funding-record id
  • an application status: Considering, Preparing, Submitted, Awarded, or Not selected
  • notes you type in the application tracker

The workspace also stores a timestamp for in-app updates you have marked reviewed.

The interface says student names can be nicknames and that you should add only information you have permission to use.

Other records that can identify an account

A separate jobs table stores operational rows:

  • user-refresh- plus the account id, containing only the time of that account’s last source refresh. This enforces a 15-minute limit. Deleting a profile does not remove this row.
  • last-refresh, a shared scan summary. The copy stored in the database can include profile ids and match counts for the monitored profiles included in that scan. The response sent to the public workspace view removes those profile ids, the search cursor, and per-source errors. It keeps the scan time, counts, source name, status, record counts, request counts, notes, and a coverage sentence.
  • state- and research- rows about source checks. They describe sources and retrieval status. They do not store profile names, email addresses, or background notes. An owner-only research plan can include up to eight interest keywords gathered from monitored profiles in a state. That plan omits names, email addresses, and background notes.

The catalog table stores the shared funding listings (titles, funders, descriptions, amounts, deadlines, links, and similar public listing fields). It is not your account. A few starter listings are also included in the application itself.

The site operator can read workspace rows and job rows, because owner-only refresh and research tools load them in order to update the shared catalog. Those tools are not available to other signed-in accounts. A workspace response for a signed-in visitor returns that visitor’s own workspace, not someone else’s.

How workspace information is used

  • to show your profiles, shortlist, application tracker, and in-app updates
  • to rank listings using applicant type, country, state, study level, interests, and funding goal. A score is an alignment score, not the chance of receiving an award
  • when monitoring is on, to build funding searches from applicant type, country, state, and interests. Names, email addresses, and background notes are not included in those outbound searches
  • to show new in-app matches for monitored profiles. This version does not send email or browser push alerts

While you are signed in and the page is visible, the app reloads your workspace about once a minute and when you return to the tab. It pauses that reload while you are editing, saving, or refreshing.

The interface describes a daily catalog update at 9 a.m. Eastern for profiles with monitoring turned on. The application code exposes that update as an owner-only refresh. Guest searches and paused profiles are not monitored.

Tobias Fletcher runs that daily refresh himself, through a ChatGPT scheduled task that calls the owner-only refresh. It creates no extra logs about visitors.

Hosting and sign-in providers

  • The app runs on Cloudflare Workers through OpenAI Sites. Workspace, catalog, Google-link, and job rows are stored on Cloudflare, in a Cloudflare D1 database (the DB binding).
  • The site is hosted as an OpenAI Site. Sign-in is Sign in with ChatGPT (OpenAI), using the paths listed above.
  • When Google sign-in is turned on, Continue with Google is provided by Google, as described above.

This application does not include an advertising library, and it does not sell workspace records. It also does not write its own request log of IP addresses.

We count visits with Cloudflare Web Analytics, which uses no cookies and doesn’t track you across sites.

I Can Get Grants also keeps its own first-party daily totals in its database: how many home searches were run (the search words are not sent or stored), how many grant cards were opened, and how many links to an official source or application page were clicked. Each total is only a date, an event name and a number. No cookies, IP addresses, browser details or account ids are stored with them, no third-party script is involved, and only the site owner can see the totals.

Cloudflare and OpenAI may keep their own standard request logs, including IP addresses, under their own policies (Cloudflare’s privacy policy andOpenAI’s privacy policy).

Funding sources

When a signed-in refresh or the owner-only catalog refresh runs, the server requests public funding pages and APIs. Those requests identify the app with the user-agent ICanGetGrants/1.2 (funding source discovery; +https://icangetgrants.com). They can include search keywords, applicant category, country, or state derived from monitored profiles. They do not include your name, email, or background notes.

Sources requested by the current discovery code include:

  • Grants.gov (api.grants.gov)
  • CareerOneStop scholarship listings (cloudfront.careeronestop.org)
  • business-funding and student-aid pages configured for all 50 states, plus the California Grants Portal CSV on data.ca.gov
  • the U.S. Chamber CO— small-business grant guide
  • Poets & Writers grant listings
  • Federal Student Aid pages on studentaid.gov and named state student-aid pages
  • WomensNet Amber Grant and Awesome Foundation program pages
  • official city economic-development and small-business grant pages, and community foundation grant pages

A curated NASE Growth Grants listing is included even when its page cannot be fetched automatically. Choosing “Visit source” leaves this site. The provider’s own terms and privacy practices then apply. This app does not submit an application to a funder for you.

Cookies and on-device storage

The application does not save the workspace in browser local storage. Sign in with ChatGPT is carried by the headers listed above. When Google sign-in is turned on, the app sets two cookies of its own. Both are HttpOnly, Secure, SameSite=Lax, and signed by the server:

  • __Host-icgg_google_oauth holds one-time values for a Google sign-in or link in progress. It lasts up to 10 minutes and is cleared when Google returns.
  • __Host-icgg_session holds the Google account identifier and an expiry time. It lasts up to 30 days, or until you sign out.

Neither cookie is used for advertising or analytics.

For Sign in with ChatGPT, the only sign-in cookies are the ones OpenAI sets, covered by OpenAI’s privacy policy. I Can Get Grants sets no cookies of its own for that sign-in. The two Google sign-in cookies above are the only cookies the app sets itself.

Export, retention, and deletion

During the beta there is no automatic retention period and no automatic deletion.

  • You can delete a profile from the profile editor. The next successful save removes that profile and its saved opportunities from the stored workspace.
  • You can remove a saved opportunity from the application tracker.
  • You can download the workspace currently loaded in the browser as icangetgrants-workspace.json from the application tracker and from Preferences & data.
  • Signing out does not delete the workspace row or the refresh-time row. A ChatGPT account can unlink Google in Preferences & data, which deletes the google_links row.
  • The app has no button that deletes the account, the workspace row, or the refresh-time row.

You can ask for access to your workspace data, or for deletion of it, by emailing hello@icangetgrants.com (or use the contact form). Requests are handled manually. A completed deletion removes that account’s workspace and the refresh and scan records tied to that account or to its profile ids, plus any Google link for that account.

Age and information about other people

I Can Get Grants is for people 13 and older. If you are under 18, use it with a parent or guardian’s involvement. The operator does not knowingly collect personal information from children under 13. The app does not ask for age, and it has no age gate or parental-consent step.

You can create a profile for a student or another person. Study levels include high school. The interface says student names can be nicknames. Add information about someone else only when you have permission to do that. If you believe information about a child under 13 has been saved, email hello@icangetgrants.com (or use the contact form) so it can be deleted.

Safeguards in this version

  • Workspace responses use Cache-Control: private, no-store.
  • Saves and signed-in discovery require the account headers and a same-origin request.
  • Each saved workspace is keyed by that account id, or, for a Google sign-in, by the linked ChatGPT account id or the Google identifier.
  • Catalog administration is limited to the site operator. A local development identity is accepted only when the app is running in development.
  • Traffic to the site is encrypted in transit (HTTPS), and stored data is encrypted at rest by Cloudflare. The application does not add its own encryption layer on top of that.

If we learn of a breach that affects your information, we’ll notify affected users promptly.

Changes to this policy

Updated versions of this policy are posted at this same address, /privacy, with a new effective date. The product does not currently record that a visitor accepted this policy.

Contact

Tobias Fletcher, Brooklyn, New York. Email hello@icangetgrants.com or use the contact form.

The contact form sends only the name, email address, and message you type, when you press Send. It goes through a small form handler on tobiasfletcher.com, hosted by Cloudflare, which emails it to the operator through Google (Gmail) and sends you one short confirmation with a copy of your message. A one-way hash of your IP address and email address is used to count messages per day and limit abuse. Messages are used only to reply.

Public funding sources. Confirm eligibility and deadlines with the provider.
PrivacyTermsContact
I Can Get Grants · Beta