GGeneaProofGenealogy, grounded in evidence.
Sign inRegister
Menu
Help

Instructions

Step-by-step guidance for accounts, workspaces, family maps, people, evidence, import, research, collaboration, privacy, plans and export.

Choose a topic for a complete workflow. Open only the detail you need, or search across the whole handbook.

WorkspaceYour research data stays the same. Only guidance, density and advanced controls change.

How to use it

  1. Import existing research or create an empty private workspace. You can change direction later without losing data.
  2. The workspace controls members, roles and storage.
  3. You can add more trees later without creating another account.
  4. Keep these four actions visible and continue at your own pace.
  5. Progress is calculated from private records you can access. No separate completion profile is stored.
  6. The person and preferred name are saved atomically with an audit record.
  7. Link an exact citation to the person, a name or an individual event.
  8. A person, source and evidence link are stored in the private workspace. Continue researching or invite a collaborator.
  9. 3–30 letters, numbers or underscores. Your username is visible to other signed-in researchers.
  10. You can import Visio, GEDCOM, GEDZIP, Gramps XML/package or GeneaProof JSON directly.
Open feature
PeopleFind every person and work directly on the family map while keeping research facts, visual presentation and layout changes clearly separate.

How to use it

  1. Open People to search preferred names across the trees you can access. Filter by one tree, clear filters when needed, move through the result pages and choose Open in map on the correct person.
  2. Pan and zoom the map with the active navigation mode. Card detail adapts to zoom; controls and the mini-map can reframe the visible area. Guided, trackpad and precision behavior can be changed in Settings.
  3. Use the map search to find names, alternative names, dates, places or occupations. Press / to focus search, Enter to open the first result, Escape to clear it and Tab to move through accessible controls.
  4. Toggle parent–child and union lines independently. Selecting a person emphasizes that person and direct relatives; on very large trees GeneaProof renders the selected area first so search remains the reliable way to reach anyone.
  5. Open Filters on the family map to narrow the view by a selected person's direct family, ancestors or descendants, living status, research status, linked evidence, disputed research or a displayed flag. Branch filters need a selected reference person. The reference card stays visible for context, and filtering changes only the current view—not research records, relationships or saved layout positions.
  6. With editing access and inline editing enabled, select a card and activate its name or research status to edit the display name, global name components, name type, sex, living status, privacy, research status and biography. Save atomically, or press Escape to cancel.
  7. The complete name shown on the family map and in lists. Keep the structured name parts below as well so the name remains searchable and portable.
  8. A name component derived from a parent’s given name in naming traditions that use patronymics or matronymics. Leave it empty when it is not part of the person’s name.
  9. Choose the context in which this version of the name was used, such as a birth name, married name, nickname or religious name.
  10. A title or other element written before the person’s name. Enter only what belongs to the recorded name and leave the field empty when none is known.
  11. An element written after the person’s name, often distinguishing generations, qualifications or an inherited naming form.
  12. Preserve the complete name in its cultural order above. Add structured components and transliterations only when they are documented; they never replace the displayed name.
  13. Use a BCP 47 language tag for the language of the displayed name. Include a script subtag when it matters.
  14. Use the four-letter ISO 15924 code for the script used by the displayed name.
  15. Add only components supported by the source and keep them in the person's own name order.
  16. Record the same name in another script or transliteration system. Every representation requires its own language tag.
  17. Controls who may see this person when the research is shared. It does not change the evidence or grant anyone access to the workspace.
  18. Your current assessment of the research. This status helps organise review work and never replaces sources, citations or a proof conclusion.
  19. Activate the lifespan or place on an editable card to change birth and death. Preserve the source wording in Original date; use qualifier, confidence and separate normalized start and end dates for searching and chronology.
  20. Use the flag tool for separate dated nationality or citizenship claims. Enter the source-near territory text, optional jurisdiction code, confidence and an explicit modern flag or no flag. Several periods may coexist; the card shows up to four chosen flags and a remaining count.
  21. On an editable standard or detailed card, activate a work, residence, migration, education or military marker to open that exact saved event in the full inspector. A grouped +N opens the earliest displayed event; use the selector to reach the others. Opening does not save a change.
  22. Open a person to use the inspector for complete relationships, other events, evidence, conclusions and media. Advanced evidence and conflict work stays here even when quick fields are edited directly on the card.
  23. Hover over a name, date, place, flag, symbol, status or image in a person card to see what it represents. Keyboard-focusable controls show the same help when focused.
  24. Link witnesses, godparents, officiants, informants and other people exactly as the source records their involvement.
  25. Save the event before adding its participants.
  26. Preserve wording such as “about 42”, “infant” or an uncertain age without converting it into a conclusion.
  27. Record only what the source says about this person's participation. Interpretations belong in the evidence discussion.
  28. Contributors can update source-near details. Only owners, administrators and editors can replace the person or role or remove a participant.
  29. Participant changes update the event version and are preserved in the workspace audit history.
  30. Choose the calendar used by the source wording. GeneaProof preserves it and never guesses a conversion.
  31. Keep a second representation from the source, such as an old-style/new-style date or a split year. Leave it empty when the source gives only one date.
  32. Choose the calendar for the parallel wording. Unknown is valid when the source is ambiguous.
  33. Normalized start and end dates are separate search and sorting aids. Enter them only when supported by your research; GeneaProof does not convert calendars automatically.
  34. In the person's Media section, choose an allowed file within the displayed size limit, assign its role and add descriptive and rights metadata. A manager may mark a browser-safe portrait as primary and adjust its human-chosen focus and zoom without changing the original file.
  35. Upload heraldry, an occupation image, a frame texture or a card background with that exact visual role, then choose Use on card. Each choice is private presentation media; remove it from the card without deleting the underlying file when you only want a different appearance.
  36. Open Settings to choose a complete visual style or customize card detail, shape, accent, frame and background. Available library styles follow the effective plan; a selected card's frame tool can override the account frame for that person or return to inherited style.
  37. See card, frame, canvas and connector changes before saving. This preview uses fictional labels and never loads research or private media.
  38. In Settings choose curved, straight or stepped relationship lines, automatic, vertical, horizontal or closest-side attachment, arrowheads, line weight and palette. These account-level choices change presentation only; relationships are edited in the inspector, not by drawing a line.
  39. When card dragging is enabled, move cards to the desired positions and choose Save position or Save positions. A saved coordinate changes only the private layout, never a person or relationship; retry if the save control reports an error.
Open feature
Import dataImport through read-only analysis, a bound preflight and an explicit private write. The review queue keeps uncertain mappings, duplicates and corrections separate from trusted genealogy.

How to use it

  1. Create or select the destination workspace and tree before importing. Keep the original file unchanged and record which program, version and export settings produced it.
  2. Choose the file on Import. GeneaProof first validates size, filename, container and supported format; database candidates remain read-only until an exact versioned adapter has verified evidence.
  3. Read the detected format and next-step status. Direct adapters can continue; conversion bridges explain required conversion; DNA and ordinary evidence belong in their separate protected flows.
  4. GeneaProof identified the product family, but it will not guess an unverified private database schema. Convert a copy before continuing.
  5. For a named genealogy application, export GEDCOM 7 in UTF-8 when available; otherwise use GEDCOM 5.5.1 with Unicode or UTF-8. Include the intended people, sources, citations, notes and stable identifiers.
  6. For a generic database, archive or vendor export, ask the source system or data owner for a documented, non-executable export. Prefer GEDCOM; otherwise use UTF-8 CSV, XML or JSON with field and relationship documentation.
  7. Keep the exported file and its complete media folder together. Do not rename or move linked media until import and count comparison are complete.
  8. Keep the unchanged original, every backup and all related folders together until the portable export has been imported and verified.
  9. Review living people, private facts, notes and media before export. Never upload this file to an unreviewed online converter or share its password with a conversion service.
  10. For CSV, XLSX or ODS, select the worksheet and header row, map each column, choose the correct date order and inspect sample rows. Confirm only when names, identifiers, relationships and dates mean what you intend.
  11. Select Analyze file. Check people, events, places, unions, parent-child links, sources, citations, media and review-item totals before any data is written.
  12. Inspect the read-only preflight for creates, updates, earlier imports and duplicate candidates. Its fingerprint binds the approved preview to the later write and must be regenerated if the source or destination changed.
  13. Open the loss report and inspect every preserved, mapped and not-imported category. Continue only when you understand what remains native, what keeps its original record and what needs later review.
  14. Confirm the private-import boundary, then start the import. The write is atomic under workspace permissions; imported people stay private by default and a browser return never substitutes for the server result.
  15. Large imports become resumable jobs. Follow recorded progress, resume an interrupted job only from its current state and cancel it from the job control instead of uploading the same file again.
  16. After success, open Review whenever review items were created. Imported data remains available while uncertain records wait for an explicit decision.
  17. Use status, severity and code filters to work systematically. Start with critical and error items, then warnings and informational batches; reset filters when an expected case is not visible.
  18. Select one issue and compare the original record, importer note and normalized candidate. Treat source-provided text as evidence, not as a conclusion, and inspect the exact workspace, tree and source file.
  19. Approve only when the proposed mapping is faithful, correct through the typed workflow when a supported fact is wrong, or ignore only when the preserved issue needs no change. Add a concise reason that another researcher can audit.
  20. Use the typed name, birth or death correction form for supported facts and review informational batches through their batch control. Generic text decisions must not bypass field-specific preview, fingerprint or validation.
  21. For a possible duplicate, generate the read-only merge preview, choose the survivor and resolve every structural conflict. Submit a reason; another authorized researcher must review before mutation, and an owner or administrator can use the time-limited rollback when safe.
Open feature
Review centerTriage imports, duplicate hypotheses, disputed conclusions and professional evidence or chronology signals without weakening their specialized workflows.

How to use it

  1. Compare original import data with normalized candidates and document every research decision.
  2. Persistent hypotheses stay with the workspace, including the exact evidence snapshot and independent review decision.
  3. People marked disputed need their facts, sources or preferred conclusions checked in the family map.
  4. Prioritized, explainable next steps from the evidence and review work already in your workspace.
Open feature
SourcesKeep conflicting dates and conclusions without overwriting the original material. Every claim can carry its own evidence.

How to use it

  1. Link an exact citation to the person, a name or an individual event.
  2. The evidence link is saved to the selected database record, not only to the person card.
  3. Explain why the citation supports or contradicts this particular fact.
  4. The title, call number and other shared source details are not changed here.
  5. For example: volume A I:4, image 18, record 7
  6. Preserved verbatim, including line breaks.
  7. A readable transcription of handwriting or an image.
  8. For example: reading uncertainty, image quality or variant spelling.
  9. The source, citation and evidence link were saved atomically in the audit history.
  10. Save the citation first. Then open it through Manage to link private source images or documents.
  11. The link is removed from this fact. The source and citation remain available for provenance and reuse.
Open feature
Research tasksTurn research questions into assigned tasks, versioned notes and reproducible search logs without confusing working material with facts or evidence.

How to use it

  1. Choose an accessible workspace separately in the task and note areas. The role badge shows whether you can edit; readers can inspect but never receive write controls.
  2. Use task metrics, search, status and assignee filters to find active, overdue, blocked, mine or unassigned work. Select a task to keep its workspace and task ID in the URL.
  3. Choose New task and enter a focused title. Add a description, optional tree, assignee, due date and priority; when the status is Blocked, record the blocker. Saving is version-checked and audited.
  4. Move work deliberately through Open, In progress, Blocked, Completed or Cancelled. Keep the deadline, assignee and blocker current; Realtime refreshes other viewers when you have no unsaved draft.
  5. Use the selected task's discussion to ask questions and record progress. Authorized authors can edit or delete permitted comments; Realtime refreshes comments without changing the task.
  6. To suggest a task change, start from its current values, edit the proposed fields and give a reason. The pending proposal stays separate and can be withdrawn by an allowed proposer.
  7. An authorized second researcher reviews the before-and-after fields, may add a review note and approves or rejects. Approval is disabled after the task changes; reload instead of applying a stale proposal.
  8. Open Version history to compare the eight editable task fields with an audited version. Enter a restore reason to create a normal pending proposal; history never overwrites the task directly.
  9. Create General, Research log, Hypothesis, Analysis, Question or Method notes. Choose a privacy classification and write a title and body; the classification guides future sharing and export but never bypasses workspace access.
  10. For a structured Research log, record search date, method, repository, collection, scope or query, outcome, analysis, observed result and next steps. Negative means only that this documented scope returned no result.
  11. Optionally link a note to a tree, person, name, event, union, parent–child relation, place, repository, source, citation, media item or research task. The link adds context, never a fact or evidence assertion.
  12. Search citations in the same allowed scope and add each as Context, Supports or Challenges. That role applies only within the note and does not change the citation or any conclusion.
  13. Archive finished working material instead of deleting its context. Archived notes keep history and citation links, are read-only until restored, and imported provenance notes stay read-only until their source import is rerun or replaced.
Open feature
Research resourcesOpen verified archive searches, record collections and research guides for every country. GeneaProof links out now; direct provider integrations remain a later, separately reviewed phase.

How to use it

  1. Country or territory
  2. Use the worldwide resources while this versioned directory is expanded. Absence here does not mean that the country has no archives or records.
  3. GeneaProof does not send names, dates or research data to these services. Each provider controls its own availability, terms, accounts, fees and privacy practices.
  4. Official archive or authority
  5. Mixed access
  6. Use a lawful, proportionate purpose. Respect opt-outs, provider terms and local privacy law. Do not harass, bulk-search, copy sensitive details or add private contact data to shared research without authority or consent.
  7. For a structured Research log, record search date, method, repository, collection, scope or query, outcome, analysis, observed result and next steps. Negative means only that this documented scope returned no result.
  8. Search citations in the same allowed scope and add each as Context, Supports or Challenges. That role applies only within the note and does not change the citation or any conclusion.
  9. Opens an external provider in a new tab
  10. Suggest a missing or better resource
Open feature
Research assistantPrioritized, explainable next steps from the evidence and review work already in your workspace.

How to use it

  1. Start with the highest-priority evidence, conflict and workflow review.
  2. Versioned GeneaProof rules explain every suggestion. No external language model receives your research.
  3. Guided view shows the three highest-priority next steps.
  4. Advice never changes, merges, publishes or shares research. Every research change still uses its normal reviewed workflow.
Open feature
Possible duplicatesCompare names, life events, places and family connections across an entire tree. Every result is a research hypothesis for a person to review.

How to use it

  1. Start with the highest score. Compare original sources and relationships before deciding whether two records describe the same person.
  2. Persistent hypotheses stay with the workspace, including the exact evidence snapshot and independent review decision.
  3. Explain why this pair should be reviewed. Saving the case does not merge or edit either person.
  4. Check the original evidence before recording whether these records describe the same person.
Open feature
TimelineExplore one tree through chronology, verified places, privacy-aware reports and immutable change history without changing the underlying research.

How to use it

  1. Open Timeline and choose an accessible tree. This view is read-only; use the family map or person editor when a date, event, participant or place needs correction.
  2. Filter by event group, dated or undated records, year range and ascending or descending order. Apply the filters, move through the bounded pages and reset to return to the selected tree's complete chronology.
  3. Read the source-near original date first, then place, participants and evidence totals. Professional details expose normalized range, qualifier, confidence, privacy, preferred status and separate Supports, Contradicts, Mentions and Derived-from counts.
  4. Open Geography, choose a tree and optionally a person, event group and year range. Places mode groups verified locations; Journey mode requires one person and orders that person's dated mapped events.
  5. Choose world or fit-to-results scope and static or animated presentation. Markers show only complete verified WGS84 coordinate pairs; routes connect the visible chronological steps and do not infer missing travel paths.
  6. Check mapped, unmapped, evidence and conflict counts before interpreting the map. Coverage or limit warnings mean the display is incomplete; the local Natural Earth base map makes no external tile or geocoding request.
  7. Preserve the names and jurisdictions that applied at different times without replacing the stable place identity, coordinates or current hierarchy.
  8. Equal spellings and overlapping jurisdictions may coexist when sources disagree. A preferred flag controls presentation only; it never proves that an assertion is correct.
  9. Choose the stable place identity. Historical names and jurisdictions are added to it without changing its coordinates or current label.
  10. Enter the spelling exactly as it should be preserved, including diacritics and the source script.
  11. Keep the original source wording and calendar. Normalized ISO dates are search aids and must not overwrite the source expression.
  12. Choose another stable place identity that governed, contained or classified this place during the stated period.
  13. Record reasoning, unresolved questions or context. Notes are not evidence and do not replace a citation.
  14. Open Reports, select a tree, focus person, Pedigree, Descendants, Family group or Narrative type, and a depth from one to eight. Generate again after changing a control; truncation or cycle notices remain part of the report.
  15. Keep Protect living people for ordinary sharing and printing. Research detail is for an authorized private context; report masking changes presentation only and never changes stored person privacy or research data.
  16. Review the complete preview, then use Print and the browser's print dialog to save PDF or print. The report is generated from the current bounded graph and is not a full workspace backup or evidence archive.
  17. Open Audit, choose an accessible workspace, then filter by entity group, insert/update/delete action and actor. Entries are paginated and read-only, and dates and counts follow the active locale.
  18. Use the summary for who changed which entity and fields. Professional details show a bounded before/after diff with sensitive values redacted; an audit entry records a change but does not by itself prove the genealogical conclusion is correct.
Open feature
CommunityWork with other researchers without surrendering control: keep friendship, workspace membership, research matching and public sharing as separate permissions.

How to use it

  1. Open Community and complete your profile. The username is your stable public identifier; first and last names are optional. Set discoverability, friend requests, real-name visibility and accessibility, then save.
  2. Search for an exact username and send a friend request. The other researcher must accept it. Friendship enables contact but never grants access to a workspace, tree, source or file.
  3. Open Chat from an accepted friend. Use direct messages for coordination; record conclusions, source criticism and proposed changes on the exact research object so their context remains reviewable.
  4. For an existing researcher, choose a workspace and exact discoverable username. For someone new, send one separate secure email invitation per person when direct delivery is active, or use the prepared draft fallback. Each pending link reserves an included subscription seat and expires after seven days unless accepted or revoked.
  5. GeneaProof sends only the invitations you request. Recipient addresses are used for delivery, are not saved as an address book and are not added to marketing. A one-way delivery fingerprint may be retained for abuse prevention and then removed under the retention policy.
  6. Choose the least access needed: Viewer reads; Contributor can add and update with limited destructive access; Editor has full genealogical editing; Administrator also manages the workspace. Only an owner may invite another administrator.
  7. The recipient checks the workspace, inviter, proposed role and message before accepting or declining. Acceptance creates only that workspace membership; rejection changes no research.
  8. Share GeneaProof with someone who may benefit from evidence-based, collaborative genealogy.
  9. GeneaProof sends only the personal recommendations you request. Addresses are used for delivery, are not stored as an address book and are never added to a marketing subscription. A keyed one-way recipient fingerprint blocks repeat sends for 90 days and is deleted within 180 days under the retention policy.
  10. Use object discussions for a person, event, source, citation, evidence link or relation. Comments do not alter evidence, and proposed changes still require the normal independent review and audit workflow.
  11. A workspace owner or administrator may enable research matching separately for each tree. Only deceased people with a normalized name and year are compared; the first match reveals aggregate counts, not names or person identifiers.
  12. To prepare a public view, first classify each deceased person that may appear as Shared or Public. Living people, uncertain life status and Private or Restricted records are masked; sources, media, notes and internal identifiers are excluded.
  13. An owner or administrator creates a draft and inspects the exact read-only graph, visible and masked counts and title. The snapshot is frozen, so later research changes cannot silently enter that link.
  14. Publish only the inspected draft. The complete bearer link is shown once; store or send it carefully. Revoke an active share immediately if it was sent incorrectly, and create a new preview when updated research should be shared.
Open feature
Backup and exportKeep research portable, verify complete backups before relying on them, restore through an explicit preview and close an account only after every owned workspace has a deliberate destination.

How to use it

  1. Open Backup and export as an active owner or administrator, choose the exact workspace and tree, then use GEDCOM 7, GEDZIP 7, GEDCOM 5.5.1 or Gramps XML for exchange. Match the receiving program's encoding; private media bytes are excluded.
  2. Read the export report before leaving the page. Notes, unsupported application details and omissions are counted explicitly; an exchange file is never a full-fidelity GeneaProof backup.
  3. Create a complete workspace ZIP for recovery or migration, download it to storage you control and use Inspect file locally before restoration. It contains supported tables, audit and active private media with a versioned SHA-256 manifest, but excludes credentials, passwords and global profiles.
  4. Choose Restore as copy to create a new private workspace from a valid backup. GeneaProof remaps internal identifiers and leaves the source workspace unchanged, so use this for a safe trial or independent branch.
  5. Restoring into an existing workspace is owner-only and requires a backup of that exact workspace. Upload locally, review checksum, schema, manifest, media and row-count preflight, and stop if any mismatch appears.
  6. Confirm the exact workspace name, required phrase and irreversible acknowledgement. Writes freeze, a restore point is created and the replacement applies atomically; never refresh or submit twice while it runs.
  7. Inspect the restored research immediately. Roll back from the protected restore point if the result is wrong, or explicitly discard the point after acceptance; do not replace a failed preflight with a blind retry.
  8. Open Account and review owned workspaces, memberships and private files. Transfer each shared workspace to an active member, or explicitly choose permanent deletion for every workspace you still own.
  9. Account closure requires recent password confirmation when available, the exact closure phrase and an irreversible acknowledgement. It freezes writes, drains private storage, erases account data and ends sessions; support cannot undo it.
  10. A statutory withdrawal request is separate from subscription cancellation and account closure. Submit it from Withdrawal only when applicable and retain its immutable receipt and status while the reviewed payment process completes.
Open feature
DNA evidence vaultKeep a bounded raw genetic file private while GeneaProof verifies its format and exact checksum. The file never becomes a family tree or an automatic conclusion.

How to use it

  1. Only uncompressed consumer SNP text/CSV and plain-text VCF up to 32 MiB are accepted here. ZIP, gzip, BCF, PLINK, FASTA, FASTQ and whole-genome files remain blocked until their separate security and processing boundary is verified.
  2. Choose a finite retention period. Only your account can access the raw object, and you can erase it immediately.
  3. These files are outside workspaces and are not available to collaborators, support staff or platform administrators.
  4. There is no indefinite option. Automatic erasure runs daily, so removal can occur after the displayed deadline but the expired file cannot be downloaded.
Open feature
Professional servicesUse professional services as a separate, deliberately scoped customer journey. A request, offer acceptance or payment never grants research access or starts work automatically.

How to use it

  1. Review the public catalog for data conversion, duplicate cleanup, a graphic family map or source and archive organization. These are request-based services, not self-running product features, and availability is confirmed only through the controlled service conversation.
  2. Sign in, choose the service code and describe the desired outcome, file format and approximate scale in 20–4,000 characters. Explicitly consent to contact through the account email; do not paste complete research, credentials or living-person records.
  3. Submitting the summary creates a bounded request only. It does not expose a workspace, tree, private media, imported file, billing data or another account, and it does not authorize GeneaProof to inspect research.
  4. Follow status and replies in Requests and replies. Keep scope decisions in that conversation, answer only what is necessary and cancel from the workspace while the request has not entered work; later cancellation requires support review.
  5. Attach a file only when the exact request asks for it. The handoff is private, request-bound, size-limited and checksum-verified; executable and DNA files are rejected, staff reads require a recorded purpose, and temporary or rejected objects are cleaned up. Accepted originals are not claimed malware-free because external antivirus and content-disarm processing are not active.
  6. Read the current versioned offer before deciding. It freezes seller, terms version, currency, tax treatment, validity, scope, deliverables and exact amount; an older, withdrawn or expired revision is not the offer you are accepting.
  7. Accept or decline only the current offer. Acceptance records agreement to that snapshot but does not charge a payment method, start work, grant access, create a subscription or unlock a product entitlement.
  8. A one-time service payment is separate from subscriptions. Continue only through hosted checkout when enabled, and trust the status shown after a signature-verified provider event; a browser return, pending payment, refund or dispute never starts work or changes research access.
  9. Support access is fail-closed and limited to owner-provisioned staff with the service-support capability. Queue, request, file, offer and status actions require a recorded reason and audit trail; that role has no general administrator, workspace, tree, media or unrelated-account access.
  10. Commercial offers, payments and delivery remain unavailable until named staffing, seller and legal terms, tax and accounting, support and incident procedures, service levels, accepted-file retention and external antivirus/content-disarm controls are approved. The site must not promise automated AI execution before an approved delivery system exists.
Open feature
Your GeneaProof planSee the access currently applied to your account and the commercial plans being prepared for launch.

How to use it

  1. A safe starting point for private, source-based family research.
  2. Prepared for dedicated individual researchers with larger and deeper projects.
  3. Prepared for families who research, preserve and collaborate together.
  4. Prepared for professional researchers, client work and advanced support.
  5. Upgrade with an automatic credit for unused paid time. Downgrades and yearly-to-monthly changes start at the end of the paid period. You can also switch billing cycle, update your payment method, review invoices or cancel. Stripe shows the exact adjustment before you confirm.
  6. Verified account events are shown newest first. Technical provider identifiers are never displayed.
  7. Open secure billing to update the payment method or complete the outstanding payment. Your research remains safe.
Open feature
Contact salesRequest a tailored GeneaProof platform for a museum, archive, library, university, public authority, historical society, professional firm or another institution. The request starts a human conversation only.

How to use it

  1. Sign in with your confirmed personal account and open Request an institution platform from the navigation or pricing page.
  2. Enter the organisation's name and type, main country, approximate seat requirement and a concise description of needs. These values are planning information, not an order.
  3. Confirm that GeneaProof may use your verified account email to contact you about this request. The email is read from Auth during an authorised review and is not copied into the inquiry record.
  4. Do not include passwords, raw DNA, living-person data or private research. Submitting the form does not expose any workspace, tree, source or media.
  5. Each account may have one active inquiry. Track its status on the same page; you may withdraw it, and a later inquiry can be submitted after withdrawal or closure.
  6. A qualified request is reviewed with you before any institution, agreement, custom price, billing arrangement, administrator account or access setting is created.
Open feature
Institutions & EnterpriseFor archives, museums, public authorities, universities and organisations that need tailored capacity, governance, onboarding or support.

How to use it

  1. Each registration creates a Supabase Auth identity and a separate GeneaProof profile. Soft-deleted Auth tombstones are excluded from active accounts.
  2. Institution administrator manages members and access; billing administrator handles commercial administration; member is the standard institutional role. These roles never grant workspace or research access by themselves.
  3. An email matching an existing GeneaProof account is linked immediately; otherwise it remains pending until that person registers. Pausing a member changes institution access only and never deletes the account or research.
  4. Review the plan, exact price, billing period, tax treatment, terms version and every entitlement before accepting. Acceptance freezes that revision; changes require a new revision.
  5. Use Active only for people who should manage the institution now. Role or status changes affect institution administration only; workspace membership and research permissions remain separate.
  6. Accepting confirms this scope and price snapshot. It does not charge a payment method, start work, grant access to research or activate a subscription.
Open feature
HelpFind product, company, trust, support and legal information in one place.

How to use it

  1. Describe the need, problem or workflow you want improved. Concrete examples help the webmaster understand the impact on your research.
  2. 20-4,000 characters. Do not include passwords or sensitive information about living people.
  3. GeneaProof does not claim a legal status, certificate, partnership, price or service level that has not been verified.
  4. This area is being prepared and verified. It does not yet represent final company, price, legal or operational information.
Open feature