Privacy Policy

1. Who We Are and Scope of This Policy

This Privacy Policy explains how NET1Plus LLC, a New Hampshire limited liability company ("Company," "we," "us," "our"), collects, uses, stores, shares, and protects information in connection with the MyFuelSavings website, application, and related services (the "Service").

This Policy is incorporated into, and should be read together with, our Terms of Service. Capitalized terms not defined here have the meaning given in the Terms of Service.

We built this Policy to be a straightforward, accurate account of our actual practices — not generic boilerplate. Where our practices are more protective than industry-typical, we say so specifically, because we think you should be able to trust exactly what happens to your data, not just that it is "kept secure."

2. Information We Collect

2.1 Account Information

When you register, we collect your email address and authentication credentials (managed through Amazon Cognito). We do not store your password in a form we can read; Cognito handles credential storage and authentication using industry-standard hashing.

A first name, last name, and nickname are optional and are provided on your profile page rather than at registration. A nickname is a unique handle intended to identify you to other people in features that share information you choose to share, so that your name need not be shown.

2.2 Uploaded Documents

You upload fuel-discount settlement documents from supported fuel discount program providers so the Service can extract transaction and savings data. These documents are referred to in this Policy as "Uploaded Documents."

2.3 Extracted Transaction Data

From your Uploaded Documents, our system extracts fuel-purchase transaction details relevant to calculating discounts and savings — for example, transaction dates, fuel types/gallons, unit prices, discount amounts, and site/location identifiers tied to the transaction. This becomes the data shown on your dashboard.

2.4 Payment Information

If you subscribe to a paid plan, payment is processed by our third-party payment processor (Stripe). We do not receive or store your full card number; we receive limited billing metadata (such as subscription status and a payment method reference token) needed to manage your account.

2.5 Usage and Device Data

We may automatically collect standard technical data when you use the Service, such as IP address, browser type, device identifiers, access times, and pages viewed, through server logs and infrastructure logging (e.g., AWS CloudFront and application logs). Server logs may include the page addresses requested from the Service, including information contained in URL parameters. These logs are automatically deleted after 90 days.

We also record how you interact with the Service — for example, which features, controls, and views you use, and when. These interaction records are associated with your account and are used to understand which parts of the Service are useful, to diagnose problems, and to guide product improvements. We do not use them for advertising, and we do not sell them or share them with third parties for their own purposes. Interaction records are automatically deleted after 180 days, and are deleted together with the rest of your data if you delete your account.

2.6 Browser Storage and Similar Technologies

We use first-party browser storage to maintain authentication and sessions, remember user preferences, temporarily cache account information, and record referral information. We do not use browser storage for advertising or third-party tracking.

2.7 Referral Information

If you visit the Service through a referral link, we store the referral code and the time of the referral in your browser before you create or sign in to an account. The referral code also appears in our server access logs (Section 2.5). If you later create an account, this information is associated with your account so we can attribute the referral. If you do not create an account, the referral code is not added to an account record, and the copy stored in your browser can be removed by clearing the Service's site data. We also keep the referral code and its time on our servers under a random identifier, with no IP address or other information about you. If no account uses it within 90 days, it is deleted.

2.8 Messages You Send Us

If you email us or use the contact form on our website, we receive your email address, any name you give, and your message, and we use them to respond to you.

3. Personal Information Contained On Your Statements — What We Do and Do Not Do With It

This section addresses something we think deserves explicit, plain-language treatment rather than a footnote.

3.1 What's on a typical settlement statement

The fuel-discount settlement documents you upload commonly contain personal information that is not related to your fuel transactions themselves — for example, your name, mailing address, and your discount-program account number, as printed by the issuing fuel discount program provider.

3.2 We do not extract, collect, store, or use that information as data

Our extraction process is scoped specifically to fuel-transaction data (Section 2.3). The AI extraction step described in Section 5 processes the whole page, so information printed alongside your transactions passes through it. What that step is built to return is fuel-transaction data and nothing else: we do not extract into our database, index, analyze, or otherwise use your name, address, or discount-program account number. It is not copied into our transaction records, it is not associated with your account as a separate data field beyond what you provided at registration, and it is not used for any purpose.

3.3 The only place that information exists in our systems is inside the original file itself, for the limited time it is retained

For the brief period your original Uploaded Document is on our systems (see Section 3.4 and Section 8 below), that document — in its original form and format, exactly as you uploaded it — is stored as a file, encrypted at rest. The personal information on that page exists only because it exists in the source document you gave us, in the same way it would exist if you saved a copy on your own computer. We do not treat it as a separately collected or usable data point.

3.4 How long we keep the original file

We do not retain your original Uploaded Document by default. Once your document has been successfully processed and the extracted transaction data (Section 2.3) has been saved to your dashboard, the original file is automatically deleted from our systems.

The only exception is if your statement requires manual review — for example, if our automated extraction cannot confidently process it. In that case, the original file is retained temporarily, only for as long as it takes our review process to resolve the item, after which it is deleted in the same way. See Section 3.5 for more on statements in this category.

3.5 Redaction for manually reviewed statements (planned)

We are evaluating an automated redaction step for statements that require manual review, so that personal information such as name, address, and discount-program account number would be removed from those temporarily retained files before storage or human review. This capability does not exist today. Statements requiring manual review are currently retained, unredacted, in their original form for the limited period described in Section 3.4, and are deleted once review is complete. We will update this Policy if and when a redaction step is implemented.

4. How We Use Information

We use the information described above to:

• create and maintain your account and authenticate your access (via Cognito);
• extract, calculate, and display your fuel-transaction and savings data on your dashboard;
• process payments and manage subscriptions (via Stripe);
• provide customer support and respond to your requests;
• maintain, secure, and improve the Service, including diagnosing technical issues;
• comply with legal obligations and enforce our Terms of Service; and
• communicate with you about your account, service updates, and other administrative matters, and, if you opt in, product news and marketing (see Section 9.5 for the distinction and your choices).

5. AI-Assisted Data Extraction (Third-Party Processing Disclosure)

To extract transaction data from your Uploaded Documents, the Service transmits document content to Anthropic's Claude models via Amazon Bedrock, a managed AI service operated within our AWS infrastructure.

• Your Uploaded Documents are sent to this AI processing step for the sole purpose of extracting the transaction data described in Section 2.3.
• This AI processing occurs within our AWS account infrastructure; it is not a general-purpose consumer chat product, and your documents are not exposed to other Bedrock customers.
• Your data is not used to train AI models. Per Amazon Bedrock's data protection terms, neither AWS nor third-party model providers (including Anthropic) use the content you submit through Bedrock, or the outputs it returns, to train or improve their underlying models, and your content is not shared with model providers.

6. How We Store and Protect Your Data

We think you should know specifically what protects your data, not just that "security is a priority." As implemented:

• Encryption at rest. Your data in our databases (Amazon DynamoDB) and stored files (Amazon S3) is encrypted using customer-managed AWS KMS encryption keys, not default provider-managed keys.
• Encryption in transit. All communication between your device and our Service is encrypted via TLS/HTTPS, served through Amazon CloudFront over our custom domains.
• Per-user data isolation. Your data is logically isolated from other users' data at the application layer, keyed to your unique authenticated identity (Cognito "sub" identifier). Application logic scopes every data query to your identity.
• Authentication. Account login and session management is handled by Amazon Cognito (Managed Login), which follows AWS's security and compliance practices for credential storage and session tokens.
• File integrity protections. Our storage buckets use versioning and deletion-protection safeguards to reduce the risk of accidental or unauthorized data loss.
• Upload validation. Files you upload pass through multiple layers of validation (client-side, transport-level, and server-side content verification) before processing, to reduce the risk of malicious or malformed files entering our systems.
• Infrastructure-as-code. Our infrastructure is defined and deployed through version-controlled infrastructure code (AWS CDK), which supports consistent, auditable configuration of the security controls above.

7. Who We Share Information With

• Service providers/subprocessors who process data on our behalf under contractual confidentiality and data-protection obligations, currently including:
  • Amazon Web Services (AWS) — hosting, storage, database, authentication, and content delivery infrastructure.
  • Amazon Simple Email Service (Amazon SES) — delivery of administrative and transactional email, and of any marketing email we send directly from the Service, if you opt in (see Section 9.5).
  • EmailOctopus (Three Hearts Digital Ltd, United Kingdom) — management of our marketing mailing list and delivery of our marketing campaigns, if you opt in. Mailing list data is stored in Ireland (see Sections 9.5 and 11).
  • Anthropic (via Amazon Bedrock) — AI-based document data extraction (Section 5).
  • Stripe: our payment processing service.
  • Cloudflare, Inc. (Turnstile): checks that a message sent through the contact form on our website comes from a person, using technical details from your browser such as your IP address. It runs only on the website’s contact pages.
• Legal and safety disclosures — if required by law, subpoena, or legal process, or if necessary to protect the rights, property, or safety of the Company, our users, or others.
• Business transfers — if we are involved in a merger, acquisition, or sale of assets, information may be transferred as part of that transaction, subject to this Policy or a policy at least as protective.
• With your direction — if you affirmatively direct us to share specific information with a third party (e.g., a tax preparer).

We do not share your data with data brokers, advertisers, or ad-tech networks.

7.1 Links You Create and Share

The Service lets you create a share link to a read-only view of your own savings summary. This is something you choose to do; we never create one for you.

Anyone who has the link can view it, without signing in. A share link is not password-protected and is not restricted to a particular person. If you post it publicly, forward it, or send it to someone who forwards it, everyone who receives it can see the shared view. You are responsible for who you give the link to and for what they do with it.

A shared view contains your fuel transaction totals and savings figures. It does not contain your name, email address, account identifiers, or the original statement files. Station locations are included only if you turn that on when you create the link; they are off by default.

You may set a link to expire on a date you choose, and you may revoke any link at any time from your account. Revoking stops the link working from that point forward. It cannot retrieve information from anyone who already viewed it, and it cannot remove copies, screenshots, or forwarded content that already exist.

We log the fact that a shared link was viewed — the time of the view — so that we can show you whether your link is being used. We do not build profiles of viewers.

Deleting your account revokes every share link you created.

8. Data Retention

• Account data is retained for as long as your account is active.
• Uploaded Documents: not retained by default. Original files are automatically deleted once transaction data has been successfully extracted (Section 3.4). The only exception is statements flagged for manual review, which are retained temporarily until review is resolved, then deleted.
• Extracted transaction data is retained for as long as your account is active, so your dashboard history remains available to you.
• Upon a deletion request, you choose when deletion takes effect. The Service offers two options:
  • Delete immediately. We begin erasing your personal information and Uploaded Documents as soon as you confirm, and will complete deletion or de-identification within 7 days of your verified request. This option cannot be undone.
  • Delete after a 30-day hold. Your data is hidden from the Service immediately and is permanently deleted on the date shown to you, 30 days after your request. You may cancel and restore your data at any point before that date by logging in and choosing Restore. Once permanent deletion begins it can no longer be canceled.
  In either case, deletion is subject to retention required to comply with legal obligations, resolve disputes, or enforce our agreements, and to encrypted backups that are purged on our standard backup-rotation schedule (typically within 35 days of deletion from primary storage).
• We may retain minimal records (e.g., that an account existed and was deleted) as necessary for legal, accounting, or fraud-prevention purposes.
• Interaction records (the record of which features and controls you use, Section 2.5) are retained for 180 days and then automatically deleted, and are also deleted if you delete your account.
• Marketing list data. If you opt in to marketing email, your name and email address are stored by EmailOctopus (Sections 7 and 11). Opting out does not remove them: the contact is kept in an unsubscribed state so that we do not contact you again, including if the list is later re-imported. It is deleted when your account is closed or deleted (Section 9.5).
• Operational processing records. We keep a technical record of each document processed — the time of processing, an internal reference to the document, and the computing resources it consumed. These records contain no personal information beyond an internal account identifier, and no content from your statements. Because they exist to detect and prevent abuse of the Service and to account for our own operating costs, they are retained after account deletion for those purposes.

Accounts that never subscribe are deleted after 13 months. If you create an account and do not subscribe, we will email you periodic reminders that the account exists, if you have opted in to receive marketing email from us (Section 9.5). At 12 months we send a final notice stating that the account will be deleted, and 30 days after that notice, approximately 13 months after you signed up, the account and all data in it are permanently deleted. Subscribing at any point before that date stops this process entirely.

We send the final notice whether or not you have opted in to our reminder emails, because it is a notice about the deletion of your data rather than a promotional message. If your email address stops accepting mail, we cannot deliver the notice, and deletion still proceeds on the schedule above.

If your subscription ends — because it expires, is canceled, or is not renewed — your account becomes read-only at the end of the period you have paid for. You can still sign in and view your history, but you cannot add new statements. Your data is permanently deleted 60 days after that date unless you subscribe again before then. We tell you the deletion date, and you can export your transaction data to CSV at any time during that period.

These schedules are separate. An account that has never subscribed follows the 13-month schedule; an account whose subscription has ended follows the 60-day schedule. No account is subject to both.

Accounts we do not charge — including accounts we have granted free access to — are not deleted on either schedule for as long as that access is in effect.

9. Your Choices and Rights

9.1 Access and Correction

You can access and review your account information and dashboard data at any time by logging into the Service. Contact us at help@myfuelsavings.com to request corrections we cannot facilitate directly through the app.

9.2 Deletion

You may request deletion of your account and associated data at any time via account settings or help@myfuelsavings.com. See Section 8 for timing.

9.3 State Privacy Law Rights

Depending on your state of residence, you may have additional rights under state privacy laws (such as the California Consumer Privacy Act, as amended) to know, access, delete, or correct your personal information, and to not be discriminated against for exercising these rights. We do not sell or "share" personal information as those terms are defined under applicable state law.

9.4 How to Exercise Rights

Submit requests to help@myfuelsavings.com. We may need to verify your identity before completing certain requests.

9.5 Email and Communication Preferences

We send two categories of email communications:

• Administrative and transactional communications, which relate to your account and your use of the Service. Examples include confirmations that a document has been uploaded or processed, notices that a statement or its underlying data has been deleted or purged, account status or closure confirmations, security alerts, and notices of material changes to this Policy or our Terms of Service. These communications are necessary to operate the Service; you cannot opt out of them while you maintain an active account.
• Marketing communications, such as newsletters, product announcements, and promotional offers unrelated to your specific account activity. We send these only if you affirmatively opt in, such as during account creation or in your account settings. You may opt out at any time using the unsubscribe link in any marketing email or through your account settings. Opting out of marketing communications does not affect your receipt of administrative and transactional communications, and does not affect your ability to use the Service. Opting out does not delete your address from our marketing list. We mark the contact unsubscribed and keep it, which is what suppresses you across every campaign and any later re-import of the list, including if your address reaches us again from another source. Your name and email address therefore remain with EmailOctopus, in Ireland, in that unsubscribed state (Sections 7 and 11). The contact is deleted outright when your account is closed or deleted. Deleting your Service data while keeping your account does not change it, so a standing choice about email keeps standing.

10. Children's Privacy

The Service is not directed to, and we do not knowingly collect personal information from, children under 18. If we learn we have collected personal information from a child in violation of this Policy, we will delete it.

11. International Users

The Service is designed for and hosted in the United States, and is intended for use by U.S.-based users. If you access the Service from outside the U.S. (for example, while traveling), your information will be transferred to and processed in the United States.

Marketing email, only if you opt in. Our marketing mailing list is operated by EmailOctopus (Three Hearts Digital Ltd), a United Kingdom company that stores mailing list data on servers in Ireland. If you opt in, the name and email address on your account are held there for that purpose, and are processed outside the United States. If you later opt out, they remain there in an unsubscribed state so that we do not contact you again, and are deleted when your account is closed or deleted (Section 9.5). Your Uploaded Documents and your extracted transaction data are never sent to that list. If you do not opt in, no information about you reaches it at all.

The contact form’s security check. The contact pages on our website use Cloudflare Turnstile to check that a message comes from a person. Cloudflare runs that check on its global network, so the technical details it uses, such as your IP address, may be processed outside the United States.

12. Data Breach Notification

In the event of a security incident involving unauthorized access to your personal information, we will notify affected users without unreasonable delay, and in any event no later than 30 days after we discover the incident, except where a shorter or longer period is required by applicable law, in which case we will follow the legally required timeline. We will also notify applicable regulators as required by applicable law, including applicable state breach-notification statutes.

13. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will provide notice (such as by email or in-app notification) before the changes take effect. The "Last Updated" date at the top reflects the most recent revision.

14. Contact Us

Questions about this Privacy Policy or our data practices can be directed to:

NET1Plus LLC

Suite 4388, 221 Main St, Nashua, NH 03060

help@myfuelsavings.com