Translations of this document are provided for convenience. If a translation differs from this English version, the English version governs.
Privacy Policy
What Hephaestus collects, why, who processes it, how long it is kept, and how to see, change or delete it.
Last updated 13 NOV 2026
Who we are
Hephaestus LLC, a South Carolina company, runs this website and makes the Hephaestus desktop app, and is responsible for (the "controller" of) the personal data this policy describes. This policy covers both. For any question or request about your data, email legal@hephaestus.design. If you have an account, you can also ask for a copy of your data in Settings → Privacy & data.
The desktop app
When the desktop app crashes, or hits an error while it keeps running, it sends a crash or error report to our servers at hephaestus.design, which pass it on to Sentry, our error-monitoring service, so we can fix it. A crash that closes the app is reported the next time you open it. Reports are on unless you turn them off: the first time the app opens, it tells you they are on and lets you turn them off, and a switch in Settings turns them off or back on at any time.
A report holds what went wrong and where it happened in the app's own code or in the engine the app is built on, the app's version and build and the versions of its internal components, the operating system and its version, the type of processor, the graphics card and its maker, the graphics interface and rendering mode the app is using and the interface's version, the amount of memory, the time, and a code worked out from the problem itself that groups reports of the same problem together. For a crash it also holds the names of the program files involved in the crash: usually the app itself or a part of the operating system, but it can be another program's add-on if one had loaded itself into the app. A report never holds your projects or anything in them, file or folder names, your user name on the computer, your computer's name, email addresses, your account details or your IP address. Because a report reaches Sentry through our website, our host keeps the same standard server log of it as of any other request to the site, described under This website. To slow down floods of reports, our server counts reports from each network each day by a keyed hash of the day and the network's IP address, and remembers each report it has passed on by a keyed hash of the report's random ID so that a resent copy is not passed on twice; each is kept for up to two days.
The app also signs you in to your Hephaestus account. The first time it opens you sign in, either by allowing the computer in your browser or with a code we email you, and after that it stays signed in. To sign in it sends your email address and the code, or your browser's approval, together with your computer's name, its operating system and the app's version, to hephaestus.design, which passes the sign-in to Supabase, the service that runs our accounts and database. If your account uses an authenticator app, the app also sends the six-digit code from it. To slow down guessing, our server counts desktop sign-in attempts by hashes of your IP address, your email address, your account ID and the app's sign-in token; each is kept for up to two days. While it is signed in, the app checks with hephaestus.design from time to time that it still is. We keep a record of each computer signed in to your account: its name, operating system and app version, how and when it signed in, and when it was last used. You can see these, and sign any of them out, under Settings → Sign-in & security; a record is deleted 400 days after that computer signs out, or with your account.
Apart from these reports, bug reports and suggestions you choose to send from the app, and signing in, the app sends us nothing. You need an internet connection the first time you sign in; after that the app works offline. Your projects are saved as files on your computer, and we receive one only if you choose to send it to us, for example by email with a bug report.
Links in the app open pages of hephaestus.design in your browser; some of those addresses include the app's version.
Your account
Your account holds your email address and whether you have confirmed it; your username, your display name and, if you add them, a bio and a profile picture; your plan, whether you sell on the Marketplace, how the account was created and whether you have finished setting up your profile; when the account was created, when your profile last changed and when you last signed in; the referral code of any creator's link you followed before creating the account on the sign-up page; and your notification settings, your notifications and any "notify me" requests you make; what you do in the forums is set out under The forums.
Asking for a sign-in code for a new address creates an account holding that address before the code is entered. If the address is never confirmed, we delete that account after 3 days, unless records we keep are linked to it or to its address. An open support conversation keeps it until a day after the conversation closes. We send one reminder before we delete it.
Your username, display name and bio are public, together with your account ID, when your account was created and your profile last changed, your plan, whether you sell on the Marketplace, whether you have finished setting up your profile, and how the account was created. Anyone can see them, including people who are not signed in.
If you add a profile picture, it is public, like your username: anyone who has its link can open it, including people who are not signed in, and it can appear wherever your profile does. Deleting your account deletes it.
Members can report a profile picture, and we may remove one that breaks our rules. When we remove one, we keep a record of it and of our reason.
We use this information to sign you in, to show your profile where you take part on the site, to send you the email described below, and to record which creator's referral link, if any, brought you to sign up.
Signing in
You sign in with a code we email to you or with Google. Each time you sign in, we record the time, the method you used, and your browser's description of itself (its user agent), and we add one to a running count of your sign-ins, which is kept with your account.
Our sign-in provider, Supabase, also records the IP address and browser of each signed-in session, and keeps security logs of sign-in activity, to protect accounts from misuse.
Signing in stores your session in cookies in your browser. These cookies are needed to keep you signed in. The site sets no advertising or tracking cookies.
You can create five recovery codes, each of which signs you in once when you cannot reach your email. We store them only as one-way hashes, which can check a recovery code but cannot reveal it, and we record when they were created, when each one is used and which sign-in session a used one opened.
If you add an authenticator app for two-step sign-in, Supabase stores, for each one, the name you give it, the secret it shares with your app, and when it was added and last used.
To protect staff accounts, our server records each staff sign-in attempt: when it happened, whether it worked, a keyed hash of the email address or username typed, and the IP address and browser details our host reports. We keep that record for 30 days. To slow down guessing, we keep short-lived counts of sign-in and recovery-code attempts, made from keyed hashes of the IP address, of what was typed, and of your account ID and email address; each is kept for up to two days.
Signing in with Google
If you choose Continue with Google, Google gives us your name, email address, profile picture and Google account ID, and tells us whether Google has verified the email address. Supabase stores these with your account.
We use the email address to sign you in. Signing in with Google and signing in with an emailed code to the same address open the same account. We offer your Google name as your display name, which you can change. We do not use your Google profile picture.
We ask Google only for your basic profile and email address. We do not use Google data for advertising, and we do not sell it or share it with anyone other than the processors listed below, except that a display name you keep from Google is public like any other display name. You can remove Hephaestus's access in your Google Account's security settings at any time. Doing so does not delete your Hephaestus account or sign you out, and if you choose Continue with Google again, Google asks for your permission again.
We email you sign-in codes; a reminder before we delete your account if you never confirm your email address; a welcome email once you finish setting up your account; a link to confirm a change of email address and, once the change is made, a notice to the address it replaced, which names the new address; a notice whenever an authenticator app is added to your account or removed from it; a copy of your recovery codes when you create them, a warning when one of them is used, and a notice when you have one or none left; if you have a paid plan, a confirmation when a new plan you asked to start at once begins, a notice when you cancel it, when you resume it and when it ends, a reminder 30 days before a yearly plan renews, with the plan, the amount, the renewal date and how to cancel, and a notice if a renewal payment fails; if you buy on the Marketplace, a confirmation when you agree that downloading an item ends your right to withdraw from that purchase, a confirmation when you ask us for a refund, our decision on it, and, for most kinds of payment dispute your bank opens on a purchase, a notice that it was opened; if you sell there, a notice when a refund our team approved on one of your sales is made, and about some payment disputes on your sales; our replies when you send us a message through the website or the app; if you make a data request in Settings → Privacy & data, a confirmation that we received it, with the date we will answer by, and a notice when we have answered or refused it; and, if you ask to delete your account, a confirmation of the request, a notice when the account closes, and a last email once it has been deleted. The notices about a changed email address and about authenticator apps are security notices, so no setting turns them off. The record of a notice sent to a replaced address, which includes that address, is kept with your account until the account is deleted. We do not send marketing email.
If you apply to the creator program, we email you when your application moves to screening, and send your press kit if it is approved. If you apply for a job, we email the address on your account when we receive the application, when it moves to screening, when an offer is ready, when you accept or decline an offer, and when we decide not to go ahead with it, unless one of its screening checks was flagged or failed; your application page shows the outcome either way. These emails name the role and what has changed. The terms of an offer are shown only on your application page.
Our email provider, Resend, receives each message's recipient address and content in order to deliver it.
This website
The website loads no advertising scripts, and its fonts are served from our own domain. Apart from Google's sign-in page when you choose it, Cloudflare's Turnstile check when you ask for a sign-in code, and YouTube's image server when the Creator Hub shows the thumbnail of a video you linked, the only outside service your browser contacts is Supabase, for sign-in, account data, the forums and pictures.
Our host, Vercel, keeps standard server logs of requests to the site. These include IP addresses, the pages requested and browser details.
On public pages, Vercel Web Analytics counts page views and Vercel Speed Insights measures how fast each page loads and responds. Your browser sends both to our own domain, where Vercel receives them. Each records the page, without the values after a question mark or anything after #, the time, your browser and operating system with their versions, and your type of device. A page view also records the address of the page that sent you here, if it is on another website, and your approximate location (country, region and city); a speed measurement records the page's timings, the part of the page each one is about, your connection speed and your country. Neither sets cookies or is linked to your account. To count visitors, Web Analytics uses a hash made from the request instead of a cookie, and Vercel discards each visitor session after 24 hours.
They never run on the sign-in and sign-up pages, invitations, checkout and the cart, member profiles and sellers' store pages, the job application form, or any page under /app, which includes your account and settings. Nothing is sent when your browser asks sites not to track you, with Do Not Track or Global Privacy Control. Vercel describes what it collects at vercel.com/docs/analytics/privacy-policy and vercel.com/docs/speed-insights/privacy-policy.
When something on the website goes wrong, a report of the error goes to Sentry, our error-monitoring service, so we can fix it. Your browser sends the report to our own domain, which passes it on to Sentry. A report holds the error and where in our code it happened, the address of the page without anything after a question mark, the names and versions of your browser and operating system, the pages and buttons used just before it, and the time. A report never holds your account details, your cookies or anything you typed. Errors on our own servers are reported the same way, and our servers also send Sentry timing data for a sample of requests.
Settings you choose, such as the color theme and color-vision mode, are saved in your browser's local storage. While you are signed in, some of what you save also follows your account to our servers, so it is there when you sign in on another browser: for example your units and region, carts, recently viewed items, drafts and applications you have started, your creator links, and the app downloads you started. The rest of what the site keeps in your browser's storage stays there, including what you do while signed out and a short history of your visits to your account home page; when you sign out, or someone else signs in on that browser, it is set aside for you rather than shown to them. We receive none of that. Settings → Privacy & data exports and deletes both.
If you follow a creator's referral link, your browser keeps its code, the page you landed on and the time. We also count the visit toward that link's total for the day, with no record of who visited; to stop one visitor being counted many times, your IP address is used briefly, scrambled rather than kept as typed, for that alone.
When you ask us to email you a sign-in code, your browser may first run Cloudflare Turnstile, a check that tells people apart from automated abuse, usually without a puzzle. It loads from Cloudflare and sends Cloudflare your IP address and details about your browser and device; our server then sends Cloudflare the check's answer and your IP address to confirm it. Cloudflare handles this under its own privacy policy.
Payments
We do not collect or store payment card details.
Paid plans and Marketplace purchases are not on sale yet. When they open, Stripe processes payments, as Who processes your data describes, and we keep the records of your plan, payments, refunds and taxes for 7 years, as tax and accounting law requires.
Applying for a job
Applying for a job at Hephaestus needs an account. An application holds your name, the email address on your account and what you give us on the form: your phone number, where you are based, your years of experience, any links, a note, the role, your resume and, if you add one, an audio introduction. It also holds the record of what happens next: the stage it has reached, our notes, the time, place and outcome of each interview, the terms of any offer and your answer, any days you tell us you are away before a start date, and, if you decline an offer without giving a reason, that you are not to be contacted about future roles.
If your application reaches screening, a further form asks for the addresses you have lived at with each landlord's name and contact details, the places you have worked with a contact at each and whether we may contact them, people who can give you a reference, and anything else you choose to tell us, and for your consent to a drug screening, a background check, a credit check and a conversation with your landlord. We use these details to check the application, which includes contacting the landlords, employers and references you list; we do not contact an employer you have told us not to. We record the result of each check with the application. The Data Sharing Policy describes the kinds of company that run checks for us.
Staff see applications only with hiring or personnel-file permissions. Screening details and check results need a separate screening permission, and each time a member of staff opens an applicant's screening details, their name and the time are recorded. The pay in an offer is shown only to staff who also hold finance permissions. Your application page shows where your application stands, and your notifications tell you when it moves to a new stage or an offer is made.
The forums
Posting in the forums needs an account. Your threads and posts are public, including to people who are not signed in: their text, titles, tags and channels, when each was posted, edited or withdrawn, the reply you mark as the answer, and your username, display name, profile picture (if you have added one) and account ID as their author. Votes are public only as totals on each post. Because all of this is public, search engines and others can copy it, and we cannot remove copies kept elsewhere.
When you edit a post, we keep the text it had before each edit, and only you and staff with forum permissions can read it. Withdrawing a post empties its text for good: it keeps its place in the thread, the public can still see that you wrote it and when you withdrew it, and the earlier text kept from your edits stays.
Which way you voted on each post can be read only by you and staff with forum permissions. When you report a post, the report holds the post, your reason and the thread's title as you saw it; you and staff with forum permissions can read it, and the member you reported cannot. Only you can read your drafts, which are saved as you type a reply, and your starred threads with how many of their replies you have seen. Writing in a thread stars it for you. When someone else replies in a thread you have starred, a notice can appear in your notifications; it says only that a followed thread has a reply, it is not emailed, and Forum replies in your notification settings turns these notices off.
When you open a thread while signed in, we record that your account opened it that day (UTC), so your views count once a day in its view total. Nobody can read that record through the site, staff included, and it is used for nothing else.
Writing in the forums, voting, reporting, and writing a review or question on a Marketplace listing need your agreement to the community pledge. We record which version you agreed to and when; agreeing again does not change the date. You and staff with security permissions can read it.
We use this information to show the forums, count views and votes, send the notices above, moderate, and limit how often one account can post or report.
Bug reports and support messages
When you write to us through the contact form or report a bug from the website, we keep what you send with the conversation: your name and email address, a phone number if you give one, the topic, your message and your answers, and any screenshots you attach, up to 3 on a bug report. We also keep how long the form was open and whether it was filled in by hand, which we use to set automated spam aside. A bug report also holds the page you sent it from, the website's version and, if the website hit an error in the last 30 minutes, the error's code. If you paste a diagnostic code from the desktop app, the report also holds what the code carries: the app's version, system and hardware details, the view and tool you were using, counts of what is in the open project, and recent error messages with the places in the app's own code where they happened. A diagnostic code never holds your projects, file or folder names, your user name on the computer, your computer's name, email addresses or sign-in tokens. A bug report sent from inside the desktop app holds the same answers, with your account, up to 3 pictures you add (screenshots of the app or images you pick), the app's version, and a diagnostic code the app attaches unless you leave it out.
Our staff who handle that kind of message read it, and it is kept and deleted as How long we keep it says. We also keep an anonymous count of bug reports (the error, the page, the version and the category, with no sender and no words) for one year. If you ask for a copy of your data, it includes what you sent, diagnostic codes included, in readable form.
The Project Portal
The Project Portal holds what the members of a project put in it: the project's name, address and details; who is on it and their role; messages, comments and tasks; schedules and calendar events; daily logs and inspections; plans, documents, photos and their markups; quotes, change orders, invoices and other records; and a record of who did what and when. Each member sees what the project's owner and their own role allow. The project's owner decides what is shared about other people in the project and is responsible for having the right to share it.
To invite someone, a project's owner gives us the person's email address and role, and can add their name and a message; we email the invitation. Someone who joins only through an invitation gets an account limited to the Project Portal. Anyone with a private calendar link to a project's schedule can read that schedule, which is how calendar apps subscribe to it.
Photos and files are stored as you upload them, so details saved inside a file, such as where a photo was taken, stay in it and can be read by members who download it; we read only the date a photo was taken, to sort it. Remove those details before you upload if you do not want them shared.
What a project holds is kept for as long as the project keeps it. A deleted item stays in the project's trash for 30 days and is then deleted. What you add to a project stays with the project for its members after you leave it or delete your account. When a project's owner deletes their account, their projects are deleted with it, apart from Doc-Sig's records, which Signing documents describes. Files count toward the storage of the project's owner.
Signing documents
When a document is sent for signing with Doc-Sig, we record each step: when it was sent, opened, signed, declined or cancelled, and when the signed copy was downloaded. Each step records the signer's name and email address, how they confirmed it was them (their sign-in, or a code we email to a signer without an account), and the IP address and browser details used. The sender and the project's owner can read this record. We can too, to answer a question about a signature, and each time we look it up is logged.
When a professional seals a copy with their own digital certificate, we also record their name and email address, the name on the certificate, a fingerprint of the certificate and the time stamped on their signature.
Once everyone has signed, the signed copy is saved as a file of the project, which everyone on the project can see, and it counts toward the storage of the person who invited them. Hephaestus keeps no copy of its own. A signer without an account gets a download link by email. The signed copy ends with certificate pages showing each signer's name, email address, how they confirmed it was them, IP address and when they signed, and the history of each step, so everyone who gets the copy can read them.
Anyone can check a copy at hephaestus.design/sign/check. The browser works out the file's fingerprint and sends us only that, never the file. To limit how often one network can check, our server counts checks by a keyed hash of its IP address.
Who processes your data
Supabase, Vercel, Resend, Hostinger and Sentry process data for us, each only for its part of running Hephaestus. Supabase stores account data and job applications with their files, holds the forums, and runs sign-in, on servers in the United States (Oregon). Vercel hosts the website, runs its page-view counts and speed measurements, and keeps cached copies of its public pages, which can show a forum post's earlier text, or the name of an account since deleted, until the page is next rebuilt. Resend delivers the email we send. Hostinger hosts our email inbox, so it stores any email you send us. Sentry receives the website's error reports and the desktop app's crash and error reports. Google runs Google sign-in, when you choose it, under its own privacy policy.
Those are the companies that host and run the service. We also use outside tools to help diagnose and verify bugs. When we copy a report into one, we leave out your name, email address and account, although a screenshot you attached can still show what was on your screen. Other kinds of recipient, such as our professional advisers and, when the law requires it, the authorities, are described in the Data Sharing Policy.
We do not sell, rent or trade personal data, and we do not share it for advertising. If the law requires us to disclose data, we disclose only what is required and tell you, unless the law forbids it.
Files you upload, such as Project Portal documents and photos, are stored by Supabase or by Cloudflare, on its R2 storage service. When paid plans and Marketplace purchases open, Stripe will process payments, refunds and disputes and, for sellers, payouts and the identity checks they need. Stripe receives card and bank details directly, under its own privacy policy, and we do not receive a full card number.
Cloudflare also runs Turnstile, the check on asking for a sign-in code that This website describes.
How long we keep it
Account data is kept for as long as the account exists, and sign-in records of customer accounts for 400 days. Sign-in records of staff accounts are kept for as long as the staff account exists. Sentry keeps the website's error reports and the desktop app's crash and error reports for 30 days. Vercel and Supabase keep their logs, and Vercel its page-view counts and speed measurements, for limited periods set by their own services, and Supabase keeps each signed-in session's IP address and browser details until you sign out of that session or the account is deleted.
Forum threads and posts, including withdrawn posts and the earlier text of edited posts, are kept with no end date, including after the account that wrote them is deleted. When someone reports a forum post, we keep a private copy of its words with the report, for our moderators only, and delete it with the report. Reports you file are kept after your account is deleted, without your name. Your drafts are kept until you send or clear them, or until 90 days after you last saved them, and your votes and stars until you take them back; these, the record of the threads you opened and your pledge acceptance are deleted with your account.
Job applications are kept while they are open. Once an application closes without a hire, because we decided not to go ahead or you declined an offer, its screening details, check results and files are deleted 12 months later and the rest of it 24 months later. An application that leads to a hire is kept with that person's employment records, and an application under a legal hold is kept until the hold ends.
Support conversations are deleted 90 days after we resolve them. If you write again before then with anything more than a thank-you, the conversation reopens, and the 90 days start again when it is next resolved; a message that only says thanks keeps it resolved. Screenshots and diagnostic codes you send with a message are deleted with its conversation. Conversations we mark as spam are deleted two years after they are marked.
Doc-Sig's record of each signing step, and a fingerprint of each signed copy with its certificate (the document's title, each signer's name and email address and, for a professional's seal, their certificate's details), are kept for 7 years, even after the account or the project is deleted. The signed copy itself is kept as long as the project keeps it.
Warnings, suspensions, bans, flags and staff notes about an account are kept for as long as the account exists and are deleted with it. Flags and staff notes are for our staff only and are not shown in your account.
When you download the desktop app, we record your account, which file and version you downloaded, and when. We keep that record for 30 days and use it to limit how many downloads one account can start in a day, to stop automated abuse of the downloads. The file comes from Supabase Storage, which logs the request, with your IP address and browser details, for a limited period set by its service.
When we deal with a legal claim, a data request or a regulator, we keep the records that matter to it, including details of people who are not our users, such as a lawyer or a claimant, for as long as the matter needs, and then delete them.
When we delete data, copies of it can remain in our encrypted backups for up to 30 days, and are then deleted. GitHub runs the backup job and Cloudflare stores the backups, which are encrypted before they leave.
Deleting your account
You can delete your account from Settings → Privacy & data → Close your account. For 30 days the account keeps working, and you can cancel the deletion there. The account then closes, and for the next 30 days you can ask us to restore it. At the end of those 60 days we permanently delete the account and the personal data connected to it, except what the next three paragraphs list, unless we must keep it for a legal claim, and the email address can be used to create a new account. If a paid plan still runs past those 60 days, the deletion waits until the plan has ended. Once the account is deleted, copies of its data can remain in our encrypted backups for up to 30 days after that, and are then deleted. A staff sign-in, the account someone who works for Hephaestus uses for staff work, can't be deleted this way: when they leave, the company switches it off and keeps it.
We keep a record that the deletion was requested and when it was carried out, the billing records of any paid plan you had, the records of any Marketplace purchases and sales you made, the files of items people bought from you, which they keep, and Doc-Sig's records of documents you sent or signed, for the 7 years under How long we keep it.
We also keep any job applications you made, without your email address or a link to the account, for the periods under How long we keep it. To remove one, delete it from Settings → Privacy & data before your account closes, or email us.
Your forum threads and posts stay, as How long we keep it says, and so do reports other members filed about them, with the reasons they gave. Until the account is deleted, including while it is closed, they show your name and your profile picture, if you have added one; after that the public sees their author as "Previous Account", with no picture. With each of them we keep your username and display name as they were when the account was deleted, and your account ID, for as long as the thread or post exists; only staff with forum or user-account permissions can see them. Your username is freed for someone else to take, but your posts never become theirs. To empty a post, withdraw it before your account closes.
Seeing and changing your data
While your account is open and not suspended, you can change your display name, username, bio and email address in Settings. In Settings → Privacy & data you can download what you gave us in your job applications, and delete an application unless it led to a hire or is under a legal hold. Delete my data, also there, removes the settings, carts and drafts kept with your account, your watch list, the notification switches you turned on (ones you turned off stay off), your job applications, except one that led to a hire or is under a legal hold, and your creator program applications, except an approved one, which stays while you are in the program. To leave the program, contact support. To get a copy of the personal data we hold about you, ask in Settings → Privacy & data or email legal@hephaestus.design from the address on your account. To correct anything you cannot change yourself, email that address.
When you download or delete your data in Settings → Privacy & data, we note it on our register of data requests: which you did, the day, and your name and email address. When your account is deleted, the note keeps only which you did and the day.
While your account is open and not suspended or banned as a whole, you can withdraw your forum posts and unstar threads, even while you are barred from writing in the forums; you can edit a post only while you are allowed to write there. A report cannot be withdrawn.
Why we may use your data
Where the law asks us to name a reason (a "legal basis"), we use your data: to provide the service you asked for under our terms, such as your account, sign-in, the Project Portal, Doc-Sig, the forums, emails about your account and, once they open, paid plans; for our legitimate interests in keeping the service secure, preventing abuse, fixing errors and crashes, counting page views and improving the service, weighed against your rights; to meet legal duties, such as keeping tax records and answering lawful requests; and with your consent where we ask for it, such as for the checks a job applicant agrees to, which you can withdraw at any time.
Where your data is stored
Hephaestus is run from the United States, and our processors store and handle data mainly in the United States. If you use the service from elsewhere, including the European Union or the United Kingdom, your data is transferred to the United States. Where the law requires a safeguard for that transfer, we rely on the Standard Contractual Clauses, or another safeguard the law recognizes, in our processors' data-processing terms.
Your rights
Depending on where you live, you may have the right to know what personal data we hold about you and to get a copy of it, to have it corrected or deleted, to receive it in a portable format, to object to or restrict some uses of it, and to withdraw a consent you gave. Seeing and changing your data, above, explains the controls in your account; for anything else, email legal@hephaestus.design. We answer within one month, or tell you within that month if we need longer, as the law allows, and we may need to confirm that a request comes from you.
We do not sell your personal data or share it for targeted advertising. If you live in a U.S. state with a privacy law, such as California, you have these rights too, you can let someone you authorize make a request for you, and we will not treat you differently for using them.
If you are in the European Economic Area or the United Kingdom, you can also complain to your local data protection authority, though we would welcome the chance to answer your concern first.
Children
Hephaestus is not directed at children under 13, and we do not knowingly collect personal data from children under 13, or under the higher minimum age the law of their country sets. If you believe such a child has created an account, email legal@hephaestus.design and we will delete it.
Security
Everything between your browser or the app and our servers travels over HTTPS. Our database lets each person reach only their own private data; on the site, staff reach account data only with permissions granted to them, and the company's owner can also reach the database directly to administer it.
Changes to this policy
When this policy changes, the date at the top changes with it, and the change is listed in the development log in the release that makes it. If a change affects how we use data you have already given us, we tell you by email or in the service before it takes effect.