Privacy Policy

This Privacy Policy explains how Ethras (“we”, “us”, “our”) collects, uses and protects information when you visit ethras.org or use our services (the “Service”). By using the Service, you agree to this policy. If you do not agree, please do not use the Service.

We may update this policy at any time. Changes take effect when posted on this page, so please check it periodically.

Information we collect

We may collect the following information:

• Account information, such as your email address and the identifiers provided when you sign in with a third-party account.
• Blockchain information, such as wallet addresses you link and details of transactions related to payments you make to us.
• Usage information, such as your API keys, their settings, and how you use the Service.
• Device and log information, such as your IP address, browser type and access times.
• Referral information, such as the campaign or website that brought you to the Service when you create an account.
• Any other information you choose to provide, for example when you contact us.

Google sign-in

If you sign in with Google, we receive basic profile information from Google, including your email address. We use it to create and identify your account and to communicate with you about the Service.

How we use information

We use information to:

• provide, operate and maintain the Service, including signing you in and processing payments;
• manage your account and apply usage limits;
• monitor, secure and improve the Service, and detect and prevent abuse, fraud or illegal activity;
• understand how people find and use the Service, for example which channels bring new sign-ups;
• operate invite links: when you sign up through another user's invite link, we record that relationship so we can credit the person who invited you. Inviting users see counts and statuses of the developers they invited — never names, email addresses or other identifiers;
• communicate with you and respond to your requests;
• comply with applicable laws and requests from authorities.

Legal basis for processing

Where the law requires a legal basis, we rely on performing our agreement with you, our legitimate interests in operating and securing the Service, compliance with legal obligations, and your consent where required.

How we share information

We may share information with service providers that help us operate the Service, such as hosting, infrastructure and blockchain node providers; when required by law or legal process; to protect the rights, property or safety of Ethras, our users or others; or in connection with a merger, acquisition or sale of assets.

Some features may connect your browser directly to third-party services, such as content delivery networks and public blockchain infrastructure, and the Service may link to third-party websites. Those parties may receive your IP address and are governed by their own privacy policies; we are not responsible for their practices.

Emails

If your account has an email address, we may send you:

• product emails, such as a welcome message after you sign up, reminders to help you get started, and alerts about your usage; and
• billing notices about your plan, renewals and balance.

You can unsubscribe from product emails at any time: use the unsubscribe link in any product email, use your email app’s one-click unsubscribe, or turn them off in Settings in the console. Billing notices are about your account rather than marketing, and cannot be unsubscribed from while you have a paid plan.

Cookies

We use three kinds of cookies:

• Essential cookies keep you signed in and are needed to operate the Service. Parts of the Service may not work without them.
• An attribution cookie helps us learn which channel brought you to us when you create an account. It is only set when you arrive from a campaign link or another website, and it records the campaign parameters in that link, the domain of the referring site, the path of the page you first landed on and the time of that first visit. It is a first-party cookie that is not shared with third parties, and it expires after 90 days. When you create an account, we save these details with your account and delete the cookie.
• An invite cookie (ethras_inv) records that you arrived through another user's invite link, so that the person who invited you can be credited. It holds the invite code and the time of that first visit. It is a first-party cookie that is not shared with third parties, and it expires after 30 days. When you create an account, we save the invite relationship and delete the cookie.

You can view and delete cookies in your browser settings at any time. Deleting the attribution or invite cookie does not affect how the Service works — you simply will not be attributed to that channel or that invite.

Visitor analytics

We use self-hosted visitor analytics, served from our own domain, to understand how the site is used, such as which pages are visited. It does not use cookies or local storage. To count unique visitors, it uses a one-way hash combined with a salt that is replaced every day, and it does not store raw IP addresses. If your browser sends a Do Not Track signal, no analytics data is collected. Analytics data is not shared with third parties.

Retention and security

We keep information for as long as necessary for the purposes described in this policy, including to meet legal, accounting and dispute-resolution requirements. We take reasonable measures to protect information, but no method of transmission or storage is completely secure, and you use the Service at your own risk. You are responsible for keeping your API keys confidential.

Children

The Service is not intended for anyone under 18, and we do not knowingly collect information from them. If we learn that we have, we may delete it.

Contact

For questions or requests about your personal information, contact support@ethras.org. See also our Terms of Service.

Anonymous public RPC

When enabled, the public Ethereum endpoint does not require an account or API key. Its application does not store RPC bodies, addresses or signed transactions in request logs. Short-lived in-memory counters use the source IP (IPv6 grouped by /64) to limit abuse; source entries can expire after 15 idle minutes. Operational infrastructure can process connection metadata. Selected third-party providers receive the RPC payload and our gateway IP and apply their own retention policies. Do not send confidential data in RPC payloads. Anonymous calls do not create accounts or qualify for referral rewards.